Atlassian Statuspage Outage History
10 incidents recorded over the last 365 days, 9 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Atlassian Statuspage Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Apr 9, 2026 | Unable to open manage portal and StatusPage intermittentlyStatusPage is operational and issue has been resolved. | 28 min | Resolved |
| Mar 19, 2026 | Latency in System MetricsThe latency fix is confirmed stable across all integrations, and we are closing this issue as resolved. | 176h 15m | Resolved |
| Mar 7, 2026 | Statuspage Database MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Feb 26, 2026 | Issues displaying system metricsThe issue has been resolved, and the service is operating normally for all affected customers. | 372h 8m | Resolved |
| Feb 10, 2026 | Disrupted Statuspage availabilityOn February 10, 2026, affected Statuspage users may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers. | 1h 14m | Resolved |
| Feb 2, 2026 | Issues displaying system metricsNew System metrics implementation has been successfully enabled for all customers. | 492h 38m | Resolved |
| Feb 2, 2026 | Statuspage API Access IssuesOn 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… | 5h 44m | Resolved |
| Oct 29, 2025 | Partial outage while accessing statuspageOn October 29th, between 9:50 UTC and 10:04 UTC, some Statuspage customers using custom domains may have experienced downtime. Once we identified the root cause of the issue, we took swift action to resolve it. We have… | -37 min | Resolved |
| Oct 24, 2025 | Intermittent errors while accessing public StatuspagesWe identified a configuration change to our edge networking that affected our ability to route traffic for Public Statuspages that use a custom domain. This occurred from 02:55 to 03:13 UTC, at which point the issue was… | 16 min | Resolved |
| Oct 21, 2025 | Atlassian Cloud Services impacted### Postmortem publish date: Nov 19th, 2025 Summary All dates and times below are in UTC unless stated otherwise. Customers utilizing Atlassian products experienced elevated error rates and degraded performance… | -1548 min | Resolved |
How to Read This Atlassian Statuspage Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Atlassian Statuspage acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Atlassian Statuspage outage in this window ran 20d 12h, against a mean recovery of 5d 11h. If you depend on Atlassian Statuspage in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.