Resolved incident

Statuspage API Access Issues

Atlassian Statuspage · Major · Started

Duration
5h 44m
Severity
Major
Status
Postmortem

Summary

Major · Postmortem

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.

View official incident ↗

Event timeline

How this incident unfolded, from the official status page.

  1. Identified

    Atlassian Statuspage

    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.

  2. Monitoring

    Atlassian Statuspage

    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.

  3. Resolved

    Atlassian Statuspage

    The incident has been resolved.

  4. Postmortem

    Atlassian Statuspage

    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.