# Jira: Atlassian Cloud Partial Outage

- Impact (vendor’s label): none
- Status: resolved
- Started: 2019-11-12 08:36 UTC · Resolved: 2019-11-12 13:42 UTC · Duration: 5.1 h
- Updates: 1
- [Vendor status page: https://jira-software.status.atlassian.com/incidents/93tb3n8mkr93](https://jira-software.status.atlassian.com/incidents/93tb3n8mkr93)
- [Company: Jira](https://rewindex.com/company/jira.md)

## Part of an outage event

- [AWS outage, Nov 12, 2019: 11 vendors, 12 incidents](https://rewindex.com/events/2019-11-12-aws)
- This incident started in the same window without naming AWS (timing only, not evidence of a link). (hop 1, posted +56 min vs the first vendor naming AWS)

```mermaid
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["Jira (this incident)<br/>posted +56 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** 2019-11-12 13:42 UTC: 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 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/93tb3n8mkr93 · Markdown: https://rewindex.com/company/jira/incidents/93tb3n8mkr93.md · JSON: https://rewindex.com/api/v1/companies/jira/incidents/93tb3n8mkr93 · Generated 2026-10-20T00:09:44.414Z