Tell customers what broke before they ask.

Hosted status pages and uptime checks for small engineering teams. Set up in an afternoon, priced per page.

What you get on day one

No setup calls and no add-ons. Every page comes with checks, notifications, an API and your own domain.

Checks from six regions

HTTP, TCP and keyword checks run every 30 seconds. A failure has to be confirmed from a second region before anything turns red.

  • FrankfurtEU Central
  • LondonEU West
  • VirginiaUS East
  • OregonUS West
  • SingaporeAsia Pacific
  • São PauloSouth America

One update, every channel

Write the incident once. Subscribers get it the way they asked for it.

  • Email and SMS
  • Slack and Teams
  • RSS and Atom
  • Signed webhooks

Everything is in the API

Read and write components, incidents and subscribers. Our own status page is built on the same endpoints.

$ curl https://api.servicestatusdashboard.com/v1/status
{
  "status": "operational",
  "page": "servicestatusdashboard"
}

On your own domain

Point a CNAME at us and the page is served on your domain, with a certificate we renew for you.

Host
status.example.com
Type
CNAME
Value
pages.servicestatusdashboard.com

From the first failed check to resolved

Automation does the watching. A person decides what customers read.

  1. Detect

    A check fails in one region. We retry from a second region within 30 seconds.

  2. Confirm

    If the second probe fails too, whoever is on call gets a draft incident to review.

  3. Publish

    One click posts the update to the page and to every subscriber.

  4. Resolve

    When checks pass again we ask before closing the incident. Nothing resolves itself silently.

One plan, billed per page

$19per page, per month

Your first page with up to five components is free.

  • Unlimited components and incidents
  • Email, Slack and webhook notifications
  • 500 SMS per month included
  • Custom domain and certificate
  • Full API access
Request access

Questions we get

Where is our data stored?

In the EU, in Frankfurt. Backups are encrypted and kept for 30 days.

Can we import from another provider?

Yes. We import components and past incidents from any page that publishes a JSON or RSS feed. Most imports take a few minutes.

What happens when you are down?

Status pages are served separately from the dashboard and the API, so they stay up when the rest of the product does not. Our own history is on the status page.

Do subscribers need an account?

No. They subscribe with an email address or phone number and can leave with one click from any message.