FireHydrant: Atlassian Status Page, Authentication Failures
Timeline of updates
- identified
Our upstream provider, Atlassian, is currently experiencing an issue which is affecting our Status Page Integration. Specifically, API Keys are experiencing authentication failures.
We are observing this issue effecting pre-existing and newly generated Atlassian API Keys.
See https://metastatuspage.com/ (opens in new tab) for more details.
We will resolve this incident once we have received confirmation the issue has been resolved from our upstream provider.
- resolved
Per Atlassian, they have started rolling out a fix and are currently monitoring its impact. Further updates will be shared as soon as the issue has been fully resolved.
See https://metastatuspage.com/ (opens in new tab) for more details.
We will resolve this incident once we have received confirmation the issue has been resolved from our upstream provider.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.firehydrant.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by FireHydrant, started 2026-02-02 15:19 UTC, resolved after 1.6 h, 2 update(s).
- Title
- Atlassian Status Page, Authentication Failures
- Vendor
- FireHydrant
- Date
- URL
- https://rewindex.com/company/firehydrant/incidents/7f33db87-218e-4ab7-bc13-31cadc405f4d
FireHydrant profileRecent FireHydrant incidentsAll outages on February 2, 2026FireHydrant in February 2026MarkdownJSON