Jira Service Desk incident
Some users in us-east-1 region unable to access Jira and JSM.
Jira Service Desk experienced a major incident on February 5, 2026 affecting Jira Service Management Web and Service Portal and 1 more component, lasting 7h 25m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 05, 2026, 02:13 PM UTC
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.
- identified Feb 05, 2026, 02:40 PM UTC
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.
- identified Feb 05, 2026, 03:39 PM UTC
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.
- identified Feb 05, 2026, 05:35 PM UTC
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.
- identified Feb 05, 2026, 07:22 PM UTC
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.
- monitoring Feb 05, 2026, 09:09 PM UTC
The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.
- resolved Feb 05, 2026, 09:38 PM UTC
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.