- 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
- 41of 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 19h 41m it lasted.
Anything that failed between 2026-02-19 16:44 UTC and 2026-02-20 12:26 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 10
- investigating
We are actively investigating reports of performance degradation affecting the ability to select users and teams in specified fields on certain sites. We will share updates here as more information is available.
provider
- investigating
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience inability to select users and teams in specified fields on certain sites. We will continue to share additional updates here as more information is available.
provider
- identified
Mitigation is progressing, and user experience is returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites.
provider
- identified
We continue to make progress on full mitigation, and more users should see experience returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites. We will continue to share additional updates here as more information is available.
provider
- identified
Several regions have fully recovered, and the team continues to diligently work on full mitigation. Some affected users may experience inability to select users and teams in specified fields on certain sites. We anticipate next update to be posted in approximately 8 hours.
provider
- identified
Our team has identified components of Jira Service Management that are also impacted by this incident and we have updated our notifications here appropriately. We anticipate our next update to be posted within 8 hours, as our team continues working with urgency towards mitigation of this issue.
provider
- identified
Customers using Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours as we continue our investigation.
provider
- identified
We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours or sooner based on significant progress.
provider
- identified
We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours or sooner based on significant progress.
provider
- resolved
This issue has been resolved and all services are functional.
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-f2d86f7a5b
Is Jira still down?
No, this incident was resolved 2026-02-20 12:26 UTC. For Jira's live state, see https://down.guide/jira.
How long did it last?
19h 41m, from 2026-02-19 16:44 UTC to 2026-02-20 12:26 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.