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, and keep it in openping.yml beside your monitors.
Your own domain
On Pro and up, a page can live at your own address, like status.example.com, with HTTPS. Until you prove the domain is yours, the page stays at your-name.openping.dev.
- Type the domain in the page’s settings. It shows a TXT record: add it at your DNS provider and press Check the record.
- Once it is proven, the settings say Waiting for your DNS: add a CNAME from status.example.com to edge.openping.dev. Add that CNAME.
- We set up the certificate. The settings move to Getting a certificate, then Live. It usually takes a few minutes; Check again asks at once.
- Change or clear the domain and we stop serving the page there. Nobody else can serve a page on your domain: only the page that proved it can.
- Move to Free and the domain keeps working until you next change the page’s settings. Then the page moves back to
your-name.openping.dev.
Without our name
Every page says “Status by OpenPing” at the foot. On Pro and up, turn off Show “Status by OpenPing” in the page’s settings and it goes.
Behind a password
On Pro and up, a page can have a password: for a page only your team or your customers should see.
- Visitors see a short form in the page’s own look: “This status page is private. Enter its password.”
- After the right password they stay in on that browser for 30 days. A new password signs everyone out. One address gets ten tries in 15 minutes.
- Search engines and agents get nothing: no JSON, no
llms.txt, no feeds without the password, and the page is never indexed. People in your workspace open it from the app without the password. - We keep only a salted hash of the password, never the password.
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
- times in your organisation’s time zone, each with its zone named (“14:05 IST”), because visitors read the page from everywhere; the day bars are your days
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. A page holds up to 1,000 email subscribers on Free, 10,000 on Pro and 50,000 on Team. A full page tells new people so, and tells you once. Nobody already subscribed is ever removed.
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.jsonBuilt 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
Pages behind sign-in (SSO or an IP allowlist), email to subscribers from your own domain, pages per audience, and SMS and Slack subscriptions are planned and not built yet.