FAQ: Status page uptime is set manually

Status page uptime is not measured automatically. Quackback does not ping or monitor your endpoints. The uptime bars are calculated from each service's status history, which changes when your team sets a status, when an incident affects a service, or when a script or monitoring tool updates it through the Status API.

How uptime is calculated

Each service's uptime bar covers the last 90 days, one segment per day (UTC). For each day, Quackback takes the share of time the service spent operational or under maintenance. Time spent in degraded performance, partial outage, or major outage counts against uptime, and the day shows the worst status it reached.

So the bar is only as accurate as the status updates you post. If a service went down and nobody changed its status, the bar still shows it as up.

Keep status current automatically

To reflect real outages without manual updates, connect your existing uptime monitor to the Status API:

1. As a workspace admin, create an API key in Settings > Developers and give it read and write access to Feedback. Status page updates are covered by Feedback access.
2. Find the service's id with GET /api/v1/status/services.
3. When your monitor detects a problem, have it send the new status:

curl -X PATCH https://your-domain/api/v1/status/services/SERVICE_ID \
  -H "Authorization: Bearer qb_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{ "status": "major_outage" }'

4. When the monitor recovers, send { "status": "operational" }.

Valid statuses are operational, degraded_performance, partial_outage, major_outage, and under_maintenance. Most monitoring tools can call a webhook URL on alert and recovery, or you can run the call from a small script.

You can also open an incident from a script with POST /api/v1/status/incidents. Your workspace's API reference at /api/v1/docs lists every field.

Related articles

• Set up a status page
• Status API
• API overview
• Follow service status