Organization administrators can now receive personalized incident information in Atlassian Administration. Subscribe to System Health (currently in Beta) to receive notifications if a reliability incident affects your organization.
Get webhook notifications whenever Jira Service Management creates an incident, updates an incident, resolves an incident or changes a component status.
On February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.
Posted Feb 07, 2026 - 05:38 UTC
Monitoring
The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.
Posted Feb 07, 2026 - 05:28 UTC
Update
Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.
Posted Feb 07, 2026 - 03:43 UTC
Update
Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.
Posted Feb 07, 2026 - 02:22 UTC
Update
Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.
Posted Feb 06, 2026 - 22:33 UTC
Update
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM.
We will continue to share additional updates here as more information is available.
Posted Feb 06, 2026 - 20:26 UTC
Update
Impact
The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption.
Current Status
Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible.
Next Steps
The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.
Posted Feb 06, 2026 - 20:24 UTC
Identified
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM.
We will continue to share additional updates here as more information is available.
Posted Feb 06, 2026 - 20:24 UTC
This incident affected: Jira Service Management Web, Service Portal, Opsgenie Incident Flow, Opsgenie Alert Flow, Opsgenie Incident Flow, Opsgenie Alert Flow, Jira Service Management Email Requests, Authentication and User Management, Purchasing & Licensing, Signup, Automation for Jira, and Assist.