Confluence: Atlassian Cloud Partial Outage
AWS outage, Nov 12, 2019 · 11 vendors, 12 incidents
Confluence’s incident started in the same window without naming AWS (timing only, not evidence of a link). (hop 1, posted +53 min vs the first vendor naming AWS)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>5 vendors, 4 blamed AWS<br/>Opsgenie, Elastic Cloud, Wise, JFrog +1"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor, 1 blamed AWS<br/>Confluent"]:::blames
root --> h4
later["Later<br/>1 vendor<br/>JFrog"]:::names
root --> later
me["Confluence (this incident)<br/>posted +53 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
Between 7:27 UTC to 12:45 UTC on 11/12/2019, we experienced an outage followed by a performance degradation for Confluence Cloud, Jira Core, Jira Service Desk, Jira Software and Opsgenie. The issue has been resolved and the services are operating normally.
From Confluence’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on confluence.status.atlassian.com (opens in new tab).