Atlassian Compass status history
Current state: operational — “All Systems Operational” per https://compass.status.atlassian.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Atlassian Compass incidents last?
From 6 incidents with a vendor-posted start and resolve time. Longest on record: Atlassian Cloud Services impacted — 21.5 h (2025-10-20 07:56 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (6)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-05-14 05:24 UTC | Users experiencing issues accessing multiple Atlassian products | postmortem | critical | 1 h 23 min |
| 2026-05-08 01:31 UTC | Multiple Atlassian services are experiencing issues | postmortem | minor | 18 h 13 min |
| 2025-10-20 07:56 UTC | Atlassian Cloud Services impacted | postmortem | major | 21 h 28 min |
| 2025-09-30 14:07 UTC | Delays in Opsgenie, JSM Ops and Compass Ops notifications | resolved | minor | 25 min |
| 2025-09-22 05:59 UTC | Degraded performance to multiple Atlassian experiences | postmortem | minor | 1 h 17 min |
| 2025-09-11 08:53 UTC | Delays observed at JSM, Opsgenie and Compass alert search functionality in US Region | resolved | minor | 9 h 51 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Atlassian Compass with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"atlassian-compass"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
