# Jira: Atlassian Cloud Services impacted

- Impact (vendor’s label): none
- Status: resolved
- Started: 2025-10-20 07:56 UTC · Resolved: 2025-10-21 05:24 UTC · Duration: 21 h
- Updates: 1
- [Vendor status page: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l](https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l)
- [Company: Jira](https://rewindex.com/company/jira.md)

## Part of an outage event

- [AWS us-east-1 outage, Oct 20, 2025: 141 vendors, 181 incidents](https://rewindex.com/events/2025-10-20-aws-us-east-1)
- This incident started in the same window without naming AWS (timing only, not evidence of a link). (hop 1, posted +45 min vs AWS’s own post)

```mermaid
flowchart LR
  root["AWS us-east-1<br/>posted 07:11 UTC"]:::root
  before["Posted before AWS did<br/>5 vendors, 4 blamed AWS<br/>Salesforce, Descope, Ashby +2"]:::blames
  root --> before
  h1["Within an hour<br/>18 vendors, 17 blamed AWS<br/>Asana, Firebolt, Monday.com +15"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>30 vendors, 29 blamed AWS<br/>SingleStore, Loops, Buildkite +27"]:::blames
  root --> h4
  later["Later<br/>45 vendors, 44 blamed AWS<br/>RudderStack, Airbyte, Unbounce +42"]:::blames
  root --> later
  p0["Twilio<br/>posted +15 min"]:::blames
  root --> p0
  k0["BigCommerce<br/>+2 h 46 min"]:::hop2
  p0 -->|"blamed Twilio"| k0
  p1["Webflow<br/>posted +4 h 37 min, did not name AWS"]:::timing
  root -.-> p1
  k1["Rootly<br/>+10 h 23 min"]:::hop2
  p1 -->|"blamed Webflow"| k1
  p2["Baseten<br/>posted +4 min"]:::blames
  root --> p2
  k2["Zed<br/>+26 h 20 min"]:::hop2
  p2 -->|"blamed Baseten"| k2
  me["Jira (this incident)<br/>posted +45 min"]:::me
  root -.->|"same window"| me
```

_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._

## Timeline of updates

- **resolved** 2025-10-21 05:24 UTC: Our team is now able to see full recovery across the vast majority of Atlassian products. We are aware of some ongoing issues with specific components such as migrations and JSM virtual service agents, and our team is continuing to investigate with urgency. We apologise for the inconvenience that this incident has caused and we will provide further information when the Post Incident Investigation has been completed.

_From the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._


---
Canonical: https://rewindex.com/company/jira/incidents/wh0w6jjt6g5l · Markdown: https://rewindex.com/company/jira/incidents/wh0w6jjt6g5l.md · JSON: https://rewindex.com/api/v1/companies/jira/incidents/wh0w6jjt6g5l · Generated 2026-10-20T03:15:43.098Z