- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
- Down Index
- 51of 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 6d 6h it lasted.
Anything that failed between 2026-06-19 22:46 UTC and 2026-06-26 05:13 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 2
- monitoring
Jira and JSM customers using Microsoft OAuth for automatic creation of Jira tickets from email were unable to read email. This is now fixed and functional for all new incoming email processing. The impacted customers during the incident period need to re-authorise the Microsoft mail server to restore and below are the instructions. To re-authorise an incoming Microsoft mail server: Login in Jira as Admin Select > System Select Mail > Incoming Mail. Select Edit incoming mail server. Select re-authorise . Enter your Microsoft credentials to continue using your Microsoft mail server.
provider
- resolved
Our team has proactively reached out to all impacted organizations providing the below instructions to re-authorize their Microsoft mail server. If you are still experiencing this issue, please attempt to complete the re-authorization as advised below. If further issues still occur that you believe to be related to this incident, please reach out to Atlassian support for further assistance.
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-e5f818cec6
Is Jira still down?
No, this incident was resolved 2026-06-26 05:13 UTC. For Jira's live state, see https://down.guide/jira.
How long did it last?
6d 6h, from 2026-06-19 22:46 UTC to 2026-06-26 05:13 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.