Jira: Degraded performance with Microsoft incoming emails
Affected components: Create and edit
Timeline of updates
- investigating
Jira and JSM incoming emails are experiencing elevated failures when processing mail, resulting in a reduction in the number of emails handled and a noticeable drop in incoming email processing.
The issue is attributed to the ongoing global service degradation with Microsoft 365 services. More details can be referred on their status page - https://status.cloud.microsoft/ (opens in new tab) - investigating
Incoming email processing is still experiencing failures, and teams continue to monitor recovery from Microsoft. We will share the next update if there is any significant change.
For more details on the service degradation reported by Microsoft, please refer - https://status.cloud.microsoft/ (opens in new tab) - identified
Incoming email processing is showing signs of improvement, but some failures continue. Teams continue to monitor recovery from Microsoft. We will share the next update if there is any significant change.
For more details on the service degradation reported by Microsoft, please refer to -https://status.cloud.microsoft/ (opens in new tab) - monitoring
We continue to see signs of improvement for incoming email processing with lower failure rates. Teams continue to monitor recovery from Microsoft, and we will share the next update when there is a significant change.
For more details on the service degradation reported by Microsoft, please refer to https://status.cloud.microsoft/ (opens in new tab)
Changes Rewindex caught on this incident
- Incident updated: Degraded performance with Microsoft incoming emails
- Incident updated: Degraded performance with Microsoft incoming emails
- Incident updated: Degraded performance with Microsoft incoming emails
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-13 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
7c81187ef6dc1b64…Version 2 captured
In the 2026-11-13 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
8d469b92b264cda4…Version 3 captured
In the 2026-11-13 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
fda969dcb8f624ef…Version 4 captured
In the 2026-11-13 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
f265684807bb3e53…
Impact, status and times are the vendor’s own, as last archived. View on jira-software.status.atlassian.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Jira, started 2026-11-13 06:01 UTC, not resolved, 4 update(s); edited after publishing.
- Title
- Degraded performance with Microsoft incoming emails
- Vendor
- Jira
- Date
- URL
- https://rewindex.com/company/jira/incidents/d5393cmcng14
Jira profileRecent Jira incidentsAll outages on November 13, 2026Jira in November 2026MarkdownJSON