Rewindex

CompaniesJiraIncidents

Jira: Delayed email ingestion and issue notifications

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatejira-software.status.atlassian.com (opens in new tab)
Part of an outage event

AWS us-east-1 outage, Dec 7, 2021 · 71 vendors, 77 incidents

Jira’s incident started in the same window without naming AWS (timing only, not evidence of a link). (hop 1, posted +1 h 52 min vs the first vendor naming AWS)

Swipe sideways to see the whole diagram.

same windowAWS us-east-1own incident not archivedWithin an hour11 vendors, 9 blamed AWSAptible, Firebolt, Honeycomb +81 to 4 hours later16 vendors, 12 blamed AWSMaven Central, Pusher, Confluent +13Later3 vendors, 2 blamed AWSSegment, Confluent, DopplerJira (this incident)posted +1 h 52 min
same windowAWS us-east-1own incident not archivedWithin an hour11 vendors, 9 blamed AWSAptible, Firebolt, Honeycomb +81 to 4 hours later16 vendors, 12 blamed AWSMaven Central, Pusher,Confluent +13Later3 vendors, 2 blamed AWSSegment, Confluent, DopplerJira (this incident)posted +1 h 52 min
Jira is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS us-east-1<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>11 vendors, 9 blamed AWS<br/>Aptible, Firebolt, Honeycomb +8"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>16 vendors, 12 blamed AWS<br/>Maven Central, Pusher, Confluent +13"]:::blames
  root --> h4
  later["Later<br/>3 vendors, 2 blamed AWS<br/>Segment, Confluent, Doppler"]:::blames
  root --> later
  me["Jira (this incident)<br/>posted +1 h 52 min"]:::me
  root -.->|"same window"| me

Full 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

  1. resolved

    Between 16:15 UTC to 17:13 UTC, we experienced Jira Work Management, Jira Service Management, and Jira Software outage impacting some customers in us-east1 region. The issue has been resolved and the service is operating normally.

From Jira’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 jira-software.status.atlassian.com (opens in new tab).

Jira profileRecent Jira incidentsMarkdownJSON