Skip to content

ProductStatus pages

A status page your customers can trust.

It changes when your metrics do, shows each customer their own commitments, and lives on your domain. Nobody has to remember to update it.

Ground
status.example.com
Skip to status
Acme
Active incidents
1 active incident.
Nov 2122:26 UTC

Latest updateInvestigating22:26 UTC ()

p95 latency on the public API is above 500 ms. Requests are completing, more slowly than usual.

  1. Identified22:52

    A slow query on the usage endpoint is holding connections. The fix is rolling out now.

View incident

At a glance

Uptime, 90 days

99.76%

Services operational

3of 4

Active incidents

1
Services
3 of 4 services operational
  • Operational
  • Degraded
  • Outage
  • No data
API
2 checks
Degraded90-day uptime99.8%
Oct 23Today
Metrics
  • Request latency p95
    Degraded90-day uptime100%
    Oct 23Today
  • Error rate
    Operational90-day uptime99.8%
    Oct 23Today
Dashboard
2 checks
Operational90-day uptime100%
Oct 23Today
Metrics
  • Availability
    Operational90-day uptime100%
    Oct 23Today
  • Page load p75
    Operational90-day uptime100%
    Oct 23Today
Webhooks
2 checks
Operational90-day uptime100%
Oct 23Today
Metrics
  • Delivery success
    Operational90-day uptime100%
    Oct 23Today
  • Queue depth
    Operational90-day uptime100%
    Oct 23Today
Database
2 checks
Operational90-day uptime99.9%
Oct 23Today
Metrics
  • Replication lag
    Operational90-day uptime99.9%
    Oct 23Today
  • Connections in use
    Operational90-day uptime100%
    Oct 23Today
Service levels
1 at risk.

API latency under 500 ms

API

18.6%budget leftAt riskTarget 99%
30 days

API availability

API

41.2%budget leftOn targetTarget 99.9%
30 days

Webhook delivery

Webhooks

72.1%budget leftOn targetTarget 99.5%
7 days

Dashboard availability

Dashboard

88.4%budget leftOn targetTarget 99.95%
30 days
Uptime calendar
Last 90 days
97.77%across the whole page
Aug 2026100%No downtime
Sep 202696.6%23 min down
Oct 202696.7%23 min down
Nov 2026100%No downtime
  • API98.8%
  • Dashboard100%
  • Webhooks100%
  • Database98.8%
Incidents
Last 24 hours
1 recent update, all resolved
Nov 2117:04 UTC1h
MinorResolvedWebhooks
  1. Investigating17:04

    Webhook deliveries are running up to ten minutes late.

  2. Monitoring17:34

    Workers are back to full capacity. Watching the queue drain.

  3. Resolved18:04

    The queue has drained and every delayed event was delivered.

The status page renderer itself, drawing sample data. Switch the layout, scroll inside it, hover a day.

Status

A status page that can't lie.

Each metric is measured against two thresholds, and a value exactly on one does not count. The page follows the measured status, not someone's memory of updating it.

The reading

API · Request latency p95

642ms

Try a reading

The rule

Healthy
under 500
Unhealthy
over 1000
Otherwise
degraded

Degraded

Neither rule matches: between the two thresholds is degraded.

One bad sample does not flip the page. By default a worse verdict has to hold for 3 minutes before the page follows, a better one for 5. Both are set per metric.

The page

status.example.com
Degraded performance · API

Services

  • 99.5%Degraded
    Request latency p95100%
    Error rate99.5%
23 OctNow

Incidents

An incident can raise the headline, never lower it.

A minor incident reads degraded even while every metric is healthy, and a real outage stays an outage whatever was posted.

Customers

One page, measured against each customer's contract.

Sign customers in through your app. The same page shows each one the targets in their contract and the incidents that affect them, and nothing about anyone else.

status.example.com
IdentifiedMinor impactOpened API
Exports delayed for your workspace

Your dedicated export worker is behind. Exports finish, up to 15 minutes late.

10:55 PM UTC

Service levels
All 3 targets healthy
  • APIAPI availability
    99.95% target, 30-day window (custom)
    54.2% of budget left
  • APIAPI latency under 500 ms
    99% target, 30-day window
    61.8% of budget left
  • DashboardDashboard availability
    99.95% target, 30-day window
    88.4% of budget left

Access

One mode per page. The badge and widget follow it, so a private page never leaks through an embed.

Public
Anyone with the address. Badge, widget and JSON are open too.
Every plan
Password
One shared password; a signed cookie keeps visitors in.
Starter and up
IP allowlist
Only your office or VPN ranges. Every other address is refused.
Starter and up
JWT
Signed in through your app, verified against your key or JWKS.
Pro and up
Customer scoped
The token's subject is the customer, granted this page.
Pro and up
Sign-in
Google or Microsoft accounts on your list, or your own identity provider on Enterprise.
Business and up

Reliability

Reliability they can verify.

Uptime is counted from recorded readings, day by day. Publish your SLO targets with the budget left, and give customers a Reliability Center with monthly attainment.

status.example.com

Uptime

Measured time, not whole days.

Uptime counts the time a check was actually unhealthy, out of the time it reported a status, so a three-minute outage costs three minutes. Degraded time was served, so it counts as up, and time without data is left out instead of counted as up. The bars mark an hour down once it has two unhealthy readings.

Service levels

Targets in public, with the budget left.

Pro and up

Choose which SLOs the page shows. Each row carries its target, its window and how much error budget remains.

Incidents

Incidents without the scramble.

When a metric breaks, Observer can draft the incident for you. Check it, publish it in one step, and the page and its subscribers hear about it together.

status.example.com

Draft

Written from the breach.

Pro and up

A metric that turns unhealthy can open a draft quoting the reading against its threshold. Drafts never reach the page until you publish.

Publish

One step to go public.

The incident lands under the headline, subscribers are emailed and your alert channels are notified.

Resolve

The all clear goes out too.

Every update and the resolution reach the same subscribers, so nobody has to check back.

Subscribers

Fewer tickets during an outage.

Customers who can see the status don't open a ticket to ask. They subscribe from the page, and your app and docs show it where they already are.

Subscribe, from the page

status.example.com

Confirmed by email. Each subscriber picks every change or a daily digest, and can leave from any message.

Status, in your docs

docs.example.com
Acme DocsStatus badge, blueprint style: degradedStatus badge, blueprint style: degraded

Webhooks

Degraded performance

Acme

  • APIDegraded
  • DashboardOperational
  • WebhooksOperational
  • DatabaseOperational

The badge and the widget are served from the page's own address and follow its access mode.

Email

Every change, or one digest a day.

Free 100 · Pro 50,000

Incidents scoped to a customer email only that customer's subscribers.

Slack, Teams, webhook

Or straight into a channel.

Visitors can send updates to a Slack or Microsoft Teams channel, or to a signed webhook, for every service or only the ones they pick. Each counts as a subscriber.

Feeds and JSON

Atom, RSS, a maintenance calendar and a JSON document per page.

For readers, calendar apps, chat integrations and your own dashboards.

Widget and badge

Two snippets.

Reference

The badge can show 30-day uptime instead. Its color still follows the current status, so a degraded page never hides behind a green number.

<iframe src="https://status.example.com/embed"
  width="360" height="240" style="border:0"></iframe>
[![status](https://status.example.com/badge.svg)](https://status.example.com)

Brand

Yours, on your domain.

Three layouts, eight theme presets with editable tokens, ten languages including Arabic and Chinese, your own address with the certificate handled, and custom CSS on Enterprise. Nothing reaches visitors until you save.

Minimal Dark

Minimal Light

Corporate Blue

Monochrome

Pastel

Serif Newspaper

Terminal Green

Vibrant Card

Console / Pages / Observer
Status page builder: layout section with a live preview of the page

The page builder: pick a layout and sections, preview against your real metrics at desktop and phone width.

The one record

Type
CNAME
Name
status
Value
cname.use.observer

What the console shows

  1. Waiting for DNS
  2. DNS verified
  3. Issuing certificate
  4. Live

Domains per plan

Starter
1
Pro
5
Business
10
Enterprise
Unlimited

Theme

A color that would fail WCAG AA is lifted until it passes, keeping its hue. Blueprint keeps its own ink palette and takes your logo and accent.

Proof

See ours. Then set up yours.

status.use.observer is an Observer page, reading Observer's own metrics. Yours can be public in about ten minutes.

status.use.observer
Public status page, Aurora layout
Public status page, Aurora layout on a phone

Agent

Run the agent.

2 min

One container next to your data. It only dials out; nothing connects in.

Metric

Define what working means.

5 min

A query and two thresholds per metric, compared with strict operators.

Page

Put it on a page.

Pick the metrics, a layout and a theme, then publish. The page follows the signal from then on.

Connect one metric. See its record in ten minutes.