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.
Update - Our teams identified two fix paths: a quick fix and a longer, time-consuming fix. We will test the quick fix over the weekend and, if no issues arise, implement it on Monday.
We will provide the next update on Monday, Feb 16, 2026.
Feb 13, 2026 - 07:41 UTC
Identified - We have identified the cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience increased error rates on APIs in Jira and Jira Service Management Ecosystem Apps.
Feb 12, 2026 - 22:29 UTC
Update - Our teams are in the final stages of mitigation. We will continue to share additional updates here as more information is available.
Feb 12, 2026 - 14:33 UTC
Investigating - We are investigating an issue with Increased error rates on APIs in Jira and Jira Service Management Ecosystem Apps.
We will continue to share additional updates here as more information is available.
Forge and Connect apps are not affected.
Feb 12, 2026 - 10:44 UTC
Here we will post updates about Jira's service availability. For status information about other Atlassian products or services, please visit the Atlassian status page.
Viewing content
Operational
Create and edit
Operational
Authentication and User Management
Operational
Search
Operational
Notifications
Operational
Administration
Operational
Marketplace
Partial Outage
Mobile
Operational
Purchasing & Licensing
Operational
Signup
Operational
Automation for Jira
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Feb 14, 2026
No incidents reported today.
Feb 13, 2026
Unresolved incident: Increased error rates on Jira and Jira Service Management Ecosystem Apps.
Resolved -
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.
Feb 7, 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.
Feb 7, 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.
Feb 7, 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.
Feb 7, 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.
Feb 6, 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.
Feb 6, 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.
Feb 6, 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.
Feb 6, 20:24 UTC
Resolved -
On February 5, 2026, JIRA and JIRA Service Management 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.
Feb 5, 21: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.
Feb 5, 21:09 UTC
Update -
Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.
We will continue to share additional updates here as more information is available.
Feb 5, 19:22 UTC
Update -
Our team is diligently working on a mitigation, with access being restored for some users in us-east-1 region.
We will continue to share additional updates here as more information is available.
Feb 5, 17:35 UTC
Update -
We have identified the 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.
Feb 5, 15:39 UTC
Identified -
Some users in the us-east-1 region cannot access Jira and JSM.
We have identified the cause and placed Jira and JSM in maintenance mode for the affected sites to expedite resolution.
We will provide update on the progress in next 60 minutes or sooner.
Feb 5, 14:40 UTC
Investigating -
Some users in us-east-1 region might not be able to access Jira and JSM. We are aware of this issue and are actively investigating the same.
We will provide update on the progress in next 60 minutes or sooner.
Feb 5, 14:13 UTC
Resolved -
Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.
Feb 3, 10:50 UTC
Update -
Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.
Feb 3, 10:24 UTC
Investigating -
Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.
Feb 3, 10:19 UTC