Jira outage on August 24, 2026: Degraded performance of Notifications
Jira reported an incident affecting Jira for 3 hours 53 minutes on 24 August 2026, from 19:22 to 23:15 UTC.
Resolved
Official incident reported by Jira
- Started
- 19:22
- 24 Aug 2026 UTC
- Resolved
- 23:15
- 24 Aug 2026 UTC
- Duration
- 3h 53m
- 3 hours 53 minutes
- Impact
- Minor
- as rated by Jira
- Updates
- 4
- posted by Jira
Timeline
All times UTC.
Official incident from Jira
Degraded performance of Notifications
-
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. We will share updates here as more information is available.
-
Official
Investigating
Our teams have identified three impacted regions, and continue to investigate the increased latency affecting email, mobile, and Slack notifications for JIRA, JSM, and Confluence.
-
Official
Identified
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience increased latency in email, mobile, and Slack notifications for JIRA, JSM, and Confluence. We will continue to share additional updates here as more information is available.
-
Official
Resolved
On August 24, 2026, some JIRA, JSM, and Confluence users may have experienced performance degradation resulting in increased latency in email, mobile, and Slack notifications. The issue has been resolved for newly created notifications, and service is operating normally. There may be older notifications that are being processed, and we expect them to be completed in next few hours.
"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.