Confluence: Intermittent Notification Delay/Failure
AWS outage, Sep 28, 2022 · 16 vendors, 16 incidents
Confluence’s incident blames AWS as the cause. (hop 1, posted +3 h 39 min vs the first vendor naming AWS)
“…are, Jira Work Management, Confluence, and Jira Service Management. The root cause was an AWS issue that caused our notification services to fail intermittently. This issue has been resolved.…”
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, 3 blamed AWS<br/>Daily, Unbounce, Gusto"]:::blames
root --> h1
h4["1 to 4 hours later<br/>3 vendors, 3 blamed AWS<br/>Lever, Jira, Confluence"]:::blames
root --> h4
me["Confluence (this incident)<br/>posted +3 h 39 min"]:::me
h4 --- 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 16:30 UTC to 19:30 UTC, some customers experienced notification delays/failures for Jira Software, Jira Work Management, Confluence, and Jira Service Management. The root cause was an AWS issue that caused our notification services to fail intermittently. This issue has been resolved.
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).