Jira outage on August 31, 2026: Fetching mails from Microsoft accounts producing errors and preventing email based creation of Jira work items
Jira reported an incident affecting Jira for 10 hours 50 minutes on 31 August 2026, from 18:28 to 05:18 UTC.
Resolved
Official incident reported by Jira
- Started
- 18:28
- 31 Aug 2026 UTC
- Resolved
- 05:18
- 1 Sep 2026 UTC
- Duration
- 10h 50m
- 10 hours 50 minutes
- Impact
- Major
- as rated by Jira
- Updates
- 3
- posted by Jira
Timeline
All times UTC.
Official incident from Jira
Fetching mails from Microsoft accounts producing errors and preventing email based creation of Jira work items
-
Official
Identified
Impact
-
Official
Monitoring
Jira Incoming Emails are experiencing elevated failures when fetching mail from Microsoft accounts. This affects email-based creation and updates of Jira work items. Users may see 500 internal server errors when email fetch attempts occur. We are tracking updates from Microsoft and continuing to review the impact. These updates are available publicly via https://status.cloud.microsoft/
-
Official
Resolved
We're now seeing full recovery across Atlassian services that have been impacted, and this incident is now resolved. For those continuing to experience issues relating to this incident we encourage you to please check https://status.cloud.microsoft/ as they continue to provide further updates about additional services.
"Official" rows are quoted from Jira's public status page, jira-software.status.atlassian.com. Very long posts are shortened.
What our checkpoints saw
HostTracker's checkpoints, which test jira.atlassian.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live Jira status shows what our checks see right now.
Does your product depend on Jira?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with Jira. Official updates are quoted from Jira's public status page and remain Jira's own words.