Changes / Statuspage / Statuspage API Access Issues
Statuspage: Major incident: Statuspage API Access Issues
Summary
Statuspage reported a major API incident starting 2026-02-02 10:56 UTC, lasting 5 h 44 min until resolution at 2026-02-02 16:40 UTC. A planned old-key cleanup unintentionally disabled new keys, causing authorization errors in some customers’ API integrations; UI and core functions remained available. Customers could generate replacement keys; Statuspage restored affected keys from a point-in-time database backup.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Statuspage API Access Issues
Before: not present
After: major
Before: not present
After: postmortem
Before: not present
After: 2026-02-02 10:56 UTC
Before: not present
After: 2026-02-02 16:40 UTC
Before: not present
After: Authenticated API, Management - Authenticated API
Before: not present
After: Customers may be experiencing issues accessing Statuspage via the API due to the deprecation of existing keys. Our team is actively working on the fix and will provide an update soon. In the meantime, as a workaround, please generate new credentials with a Statuspage API key and update your integrations accordingly.
Before: not present
After: We have started rolling out a fix and are currently monitoring its impact. We’ll share an update as soon as the issue has been fully resolved.
Before: not present
After: The incident has been resolved.
Before: not present
After: On 2 February 2026 between 08:52 and 16:40 UTC, some Statuspage customers’ API-based integrations started failing with authorization errors when a planned cleanup of old API keys unintentionally disabled new keys as well. Statuspage UI and core product functions remained available. We provided a workaround by creating new API keys and then fully restored affected keys from a point‑in‑time database backup. We are implementing safeguards around bulk key operations, improved detection of abnormal API error rates, and stronger operational checks for similar maintenance activities to reduce the likelihood and duration of similar incidents in the future.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Statuspage API Access Issues (this change) Statuspage reported a major API incident starting 2026-02-02 10:56 UTC, lasting 5 h 44 min until resolution at 2026-02-02 16:40 UTC. A planned old-key cleanup unintentionally disabled new keys, causing authorization errors in some customers’ API integrations; UI and core functions remained available. Customers could generate replacement keys; Statuspage restored affected keys from a point-in-time database backup. | Major incident |
All Statuspage changes → · Statuspage profile · Markdown · JSON