Last checked: 4 minutes ago
Get notified about any outages, downtime or incidents for Jira Service Management and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Jira Service Management.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Assist | Active |
| Authentication and User Management | Active |
| Automation for Jira | Active |
| Jira Service Management Email Requests | Active |
| Jira Service Management Web | Active |
| Opsgenie Alert Flow | Active |
| Opsgenie Alert Flow | Active |
| Opsgenie Incident Flow | Active |
| Opsgenie Incident Flow | Active |
| Purchasing & Licensing | Active |
| Service Portal | Active |
| Signup | Active |
View the latest incidents for Jira Service Management and check for official updates:
Description: We have observed cases of delayed notifications for a small no. of Jira Service Management and Jira Cloud customers. We believe the problem is resolved now. Delayed messages should arrive in the coming hours.
Status: Resolved
Impact: None | Started At: Sept. 10, 2024, 1:26 p.m.
Description: ### SUMMARY On August 29, 2024, between 8:32 AM and 11:35 AM UTC, Atlassian customers experienced an unexpected disruption in service affecting Jira and Confluence cloud products. This was primarily due to connectivity issues with an external service provider, which impacted our ability to perform certain operations integral to our services. The incident was promptly identified through our monitoring systems, and our teams initiated response protocols to address the issue. The disruption resulted in increased error rates across Jira and Confluence products, temporarily affecting the experience for some of our users. ### **IMPACT** On August 29, 2024, between 8:32 AM and 11:35 AM UTC, there was an impact on Confluence and Jira cloud affecting customers in multiple regions. The total time to resolution was three hours and three minutes. ### **ROOT CAUSE** The issue was caused by an outage on our external security token provider. Services which requested security tokens experienced timeouts leading to outages for our cloud products. Our automated monitoring system detected the incident within one minute and we confirmed the external service outage with the external provider. The provider resolved the outage at 10:02 AM UTC, and full system recovery for Atlassian was completed by 11:35 AM UTC. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We are committed to reducing the risk of similar incidents in the future. To achieve this, we will enhance our system's ability to handle external service disruptions and improve our incident response strategies. Specifically, we will reduce our reliance on single points of failure by setting up fallback region support for the critical security service provider. Additionally, we will implement measures to minimize the recovery time of the Atlassian services once the external security provider has recovered. Thanks, Atlassian Customer Support
Status: Postmortem
Impact: Major | Started At: Aug. 29, 2024, 9:43 a.m.
Description: Between 15:00 UTC to 15:48 UTC, we experienced partial unavailability for Jira in the AMER region. The issue has been resolved, and the service is operating normally.
Status: Resolved
Impact: None | Started At: Aug. 28, 2024, 4:43 p.m.
Description: Between 12:29 UTC Aug 27 to 3:38 UTC Aug 28, we experienced an issue where topics were not visible for portal-only customers when using custom domains. The issue has been resolved and the service is operating normally.
Status: Resolved
Impact: Minor | Started At: Aug. 28, 2024, 3:32 a.m.
Description: Between 01:00 UTC and 02:00 UTC, some customers experienced issues with site loading for Jira Service Management and Jira. The root cause was related to an RDS saturation. We have deployed a fix to mitigate the issue and verified that the services have recovered. The conditions that caused the bug have been addressed. The issue has been resolved, and the service is operating normally.
Status: Resolved
Impact: None | Started At: Aug. 27, 2024, 3:57 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
