# Jira: Delayed email ingestion and issue notifications
- Impact (vendor’s label): none
- Status: resolved
- Started: 2021-12-07 17:42 UTC · Resolved: 2021-12-07 17:42 UTC · Duration: 0 min
- Updates: 1
- [Vendor status page: https://jira-software.status.atlassian.com/incidents/k6ytmjs3kj2j](https://jira-software.status.atlassian.com/incidents/k6ytmjs3kj2j)
- [Company: Jira](https://rewindex.com/company/jira.md)
## Part of an outage event
- [AWS us-east-1 outage, Dec 7, 2021: 71 vendors, 77 incidents](https://rewindex.com/events/2021-12-07-aws-us-east-1)
- This 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)
```mermaid
flowchart LR
root["AWS us-east-1
own incident not archived"]:::inferred
h1["Within an hour
11 vendors, 9 blamed AWS
Aptible, Firebolt, Honeycomb +8"]:::blames
root --> h1
h4["1 to 4 hours later
16 vendors, 12 blamed AWS
Maven Central, Pusher, Confluent +13"]:::blames
root --> h4
later["Later
3 vendors, 2 blamed AWS
Segment, Confluent, Doppler"]:::blames
root --> later
me["Jira (this incident)
posted +1 h 52 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** 2021-12-07 17:42 UTC: 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 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/k6ytmjs3kj2j · Markdown: https://rewindex.com/company/jira/incidents/k6ytmjs3kj2j.md · JSON: https://rewindex.com/api/v1/companies/jira/incidents/k6ytmjs3kj2j · Generated 2026-10-20T00:51:39.213Z