Status pages

A public page at /status/<slug>that shows the current health of monitors you choose. Edge-cached for a minute so a viral incident doesn't melt your origin.

Creating a page

  1. Open Status pages in the dashboard.
  2. Pick a slug (3 – 64 lowercase letters, numbers, hyphens) and a title.
  3. Add monitors via the per-page picker. Each monitor can appear on more than one page.
  4. Mark public when you're ready. Private pages return 404 — the only difference between “not yet shared” and “doesn't exist”.

What visitors see

  • Overall banner — the worst current monitor status on the page (operational, degraded, or service disruption).
  • Component list — each monitor with a per-row pill showing its current state.
  • Recent incidents — the last 25 incidents across all monitors on the page, newest first.
  • Last updated — timestamp of the snapshot the visitor is looking at.

Embedding via JSON

Every status page is also a JSON document at /api/status/<slug>. The same Cache-Control: public, max-age=60 applies, plus permissive CORS — embed it anywhere.

{
  "slug": "acme-status",
  "title": "Acme Status",
  "overall_status": "up",
  "updated_at": "2026-05-10T08:21:59Z",
  "monitors": [
    { "id": "...", "name": "API", "type": "http", "status": "up" }
  ],
  "incidents": []
}

Custom domain

On Pro+ you can map a domain like status.acme.com at your DNS provider with a CNAME to cname.gochron.com; the page resolves there automatically. We provision TLS automatically.