Jira outage on August 25, 2026: Notifications are delayed
Jira reported an incident affecting Jira for 5 hours 51 minutes on 25 August 2026, from 08:42 to 14:33 UTC.
Resolved
Official incident reported by Jira
- Started
- 08:42
- 25 Aug 2026 UTC
- Resolved
- 14:33
- 25 Aug 2026 UTC
- Duration
- 5h 51m
- 5 hours 51 minutes
- Impact
- Major
- as rated by Jira
- Updates
- 5
- posted by Jira
Timeline
All times UTC.
Official incident from Jira
Notifications are delayed
-
Official
Investigating
We are actively investigating reports of performance degradation resulting in increased latency for email, mobile, and slack notifications for Jira, JSM and Confluence. Our teams are investigating the issue and more information will be shared within the next 1 hour.
-
Official
Investigating
Our teams have identified the impacted regions and are actively working to mitigate the issue. We will provide further updates within an hour, or sooner if we have significant progress to share.
-
Official
Investigating
Our teams have taken few corrective measures to mitigate the issue in one of the impacted regions and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered. We will provide further updates within next two hours, or sooner if we have significant progress to share.
-
Official
Monitoring
Our teams continue to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered. We will provide further updates within next two hours, or sooner if we have significant progress to share.
-
Official
Resolved
On 25th Aug 2026, some users may have experienced increased latency in email, mobile and slack notifications. The issue has now been resolved, and the service is operating normally for all customers.
"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.