← Back to Atlassian Statuspage History
major✓ Resolved

Statuspage API Access Issues

Atlassian Statuspage•
Status
resolved
Duration
5h 44m
Updates
4
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
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.
resolved
The incident has been resolved.
monitoring
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.
identified
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.

📊 TECHNICAL DETAILS

Internal ID
ca6aae25-65b9-4740-88d8-c8ab2435d02c
External ID
ctw5xv6t643h
🕐 Started
🔄 Last Updated
✓ Resolved
MAJOR
Impact Level
5h 44m
Total Duration
4
Status Updates
Affected Components
Authenticated API
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed