← Back to Jira History
minor✓ Resolved

Multiple Atlassian services are experiencing issues

JiraFri, May 8, 2026, 01:31 AM
Status
resolved
Duration
18h 18m
Updates
10
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedFri, May 8, 2026, 07:50 PM
This incident has been resolved.
monitoringFri, May 8, 2026, 11:12 AM
Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team. We apologise for the disruption and thank you for your patience.
monitoringFri, May 8, 2026, 08:03 AM
We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.
monitoringFri, May 8, 2026, 05:53 AM
The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.
identifiedFri, May 8, 2026, 04:10 AM
We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each product page.
identifiedFri, May 8, 2026, 04:10 AM
Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.
identifiedFri, May 8, 2026, 04:10 AM
We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.
identifiedFri, May 8, 2026, 03:00 AM
Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.
identifiedFri, May 8, 2026, 03:00 AM
We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.
identifiedFri, May 8, 2026, 02:15 AM
We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.
investigatingFri, May 8, 2026, 01:31 AM
We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

📊 TECHNICAL DETAILS

Internal ID
8747aa99-a131-474e-9cc8-1c7153ab5272
External ID
ryvrzdfwh57v
🕐 Started
Fri, May 8, 2026, 01:31 AM
🔄 Last Updated
Fri, May 8, 2026, 07:50 PM
✓ Resolved
Fri, May 8, 2026, 07:50 PM
MINOR
Impact Level
18h 18m
Total Duration
10
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 automatically generate one.
0 / 100 requests100 more needed