Confluence: Degraded performance in Confluence Cloud
AWS outage, Sep 18, 2023 · 29 vendors, 29 incidents
Confluence’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +1 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/>3 vendors, 1 blamed AWS<br/>Dagster, Snowflake, Vanta"]:::blames
root --> h1
h4["1 to 4 hours later<br/>7 vendors, 5 blamed AWS<br/>Amplitude, Temporal Cloud, Coralogix, Confluent +3"]:::blames
root --> h4
me["Confluence (this incident)<br/>posted +1 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
The issues with Confluence have been mitigated and the incident is being marked resolved for Confluence.
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).