- Level
- confirmed
- Worst impact
- Degraded
- Components
- Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
- Down Index
- 36of 100
What to do
Check whether you use Jira Viewing content, Create and edit, Authentication and User Management, Search and 7 more. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 36m it lasted.
Anything that failed between 2026-06-10 04:55 UTC and 2026-06-10 06:31 UTC may need a replay.Subscribe to Jira's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=jira works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Jira 4
- investigating
We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps. Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.
provider
- identified
Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products. At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers. We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.
provider
- monitoring
Our team has now determined that performance has returned to expected levels for those impacted by this incident. Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.
provider
- resolved
We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-589549b5ba
Is Jira still down?
No, this incident was resolved 2026-06-10 06:31 UTC. For Jira's live state, see https://down.guide/jira.
How long did it last?
1h 36m, from 2026-06-10 04:55 UTC to 2026-06-10 06:31 UTC, by the times Jira posted.
What was affected?
Jira named Viewing content, Create and edit, Authentication and User Management, Search and 7 more.
What caused it?
Jira hasn't published a root cause. If it does, it shows here.
Where does this come from?
Jira's official status page, https://jira-software.status.atlassian.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.