← Back to Jira History
critical✓ Resolved

Disrupted JIRA and JSM availability

Jira•
Status
resolved
Duration
9h 15m
Updates
7
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
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.
identified
Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.
identified
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.
identified
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.
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 might not be able to access Jira and JSM. We will continue to share additional updates here as more information is available.
identified
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.
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.

📊 TECHNICAL DETAILS

Internal ID
350e4c0a-25f1-4698-87a4-a7af4ff278f7
External ID
7yg61d3jfpdp
🕐 First reported
🔄 Last Updated
✓ Resolved
CRITICAL
Impact Level
9h 15m
Total Duration
7
Status Updates
Affected Components
Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed