Status pages that update themselves

How a status page works

A status page is a list of the services your customers care about, each backed by one or more monitors. You choose which monitors appear, give each a display name (so "api-prod-eu-2" can show as "Public API"), and arrange them in groups the way your customers think about your product.

When a monitor fails and the failure is confirmed, an incident opens and the page shows the affected service as having problems. When the next check passes, the incident resolves and the page goes back to normal. You can also open incidents yourself, set a severity, and post updates as you work through investigating, identified, monitoring and resolved. Each update is either public, shown on the page, or internal, kept for your team.

Planned maintenance appears on the page before it starts, and monitors in a maintenance window are silenced so they don't raise alerts or open incidents while you work.

What your visitors see

• Uptime bars for the last 30, 60 or 90 days, one bar per day per service, with that day's uptime.
• Response-time sparklines so people can see a service is slow before it is down.
• Current incidents and maintenance at the top, with every public update in order.
• A history page listing past incidents, and a page for each incident with its full public timeline.
• Your branding: logo, accent colour, light, dark or automatic theme, and an announcement banner for anything else you need to say.

Your own domain

Every page has a free address at /status/your-name. On paid plans you can serve it from your own domain, such as status.example.com, too.

1. Add the domain to the page in the app.
2. Create a CNAME record pointing the domain at Uptime Dog.
3. Create the TXT record the app shows you, at _uptimedog.status.example.com. It proves the domain is yours.
4. Click "Check DNS and verify". Once the TXT record matches, the page is served on your domain with HTTPS.

A domain is only served after it has been verified, so nobody can point their domain at your page, or yours at theirs, without the DNS records to back it up.

Subscribers

Visitors can subscribe by email. They confirm their address first (double opt-in), then hear about public incident updates, services going down and recovering, and maintenance when it's scheduled, when it starts and when it ends. Every email has an unsubscribe link.

Private pages

A page can be password protected, for an internal team or a single customer. Visitors enter the password once and the page remembers them with a signed cookie.

RSS and JSON feeds

Each page publishes an RSS feed of incidents and a JSON endpoint with every service's current status and uptime, active incidents with their public updates, and upcoming maintenance. Use the feed in a chat channel or a reader, and the JSON to show your status inside your own app or help centre.

Status page limits by plan

Subscriber limits count every subscriber across all of a team's pages. See pricing for everything else each plan includes.