OpenPingGet early access
When something breaks

Status pages

A status page is only worth having if people believe it. OpenPing builds yours from your monitors, keeps it up when your app (and ours) is down, and lets it say more than up or down.

Made for you

When you set up your first monitors, a status page is built from them at your-name.openping.dev. It stays private until you press Publish. You can point your own domain at it later.

What is on a page

  • the overall state, in words
  • components, in groups, each with 90 daily bars
  • current incidents and their updates, and planned maintenance
  • recent history
  • a line that says how the uptime number is worked out

States

Operational, Degraded performance, Degraded quality, Partial outage, Major outage and Under maintenance. Each is a word beside its colour.

Degraded quality is new: the product works, but agent tests show its answers are worse. A component backed by agent tests can show “Answers passing: 97% today”; a gateway, “Model routes: 5 of 6 working”; an MCP server, its tool count and protocol version.

From monitors to components

A component’s state comes from its monitors: the worst one decides, or most of them do, as you choose. During an incident you can set a component’s state by hand.

Updates during an incident

  • OpenPing can draft each update in plain words from the incident’s timeline. A person posts it.
  • If nobody has posted within a few minutes (5 unless you change it), a first “We’re looking into a problem with …” goes up by itself, once. Turn this off by setting the delay to 0.

Subscribing and feeds

Visitors can subscribe by email. Each page also has Atom and RSS feeds and a badge.

Statuspage-compatible API

Every page serves the Statuspage v2 files, so widgets, bots and aggregators written for Statuspage read an OpenPing page unchanged:

/api/v2/summary.json
/api/v2/status.json
/api/v2/components.json
/api/v2/incidents.json
/api/v2/scheduled-maintenances.json

Built to stay up

  • Every change renders the page to static files, served from Cloudflare’s edge.
  • If our app is down, the edge keeps serving the last version it has.
  • A page is small, makes no third-party requests, has no tracking, and works with JavaScript off.
  • Light and dark themes, or follow the visitor’s setting.

Planned

Private pages behind sign-in, pages per audience, SMS and Slack subscriptions, and hiding the OpenPing name are planned and not in the first release.