Time: Feb. 20, 2024, 1:14 p.m.

Status: Resolved

Update: Between 04:33 UTC to 13:10 UTC, we experienced intermittent 503 errors for Jira Software, Jira service management and Jira work management. The issue has been resolved and the service is operating normally.

Time: Feb. 20, 2024, 12:49 p.m.

Status: Investigating

Update: We are investigating reports of intermittent 503 errors for Jira Work Management, Jira Software and Jira Service Management Cloud customers. We will provide more details once we identify the root cause.

Time: Feb. 27, 2024, 5:45 a.m.

Status: Postmortem

Update: ### **Summary** On February 14, 2024, between 20:05 UTC and 23:03 UTC, Atlassian customers on the following cloud products encountered a service disruption: Access, Atlas, Atlassian Analytics, Bitbucket, Compass, Confluence, Ecosystem apps, Jira Service Management, Jira Software, Jira Work Management, Jira Product Discovery, Opsgenie, StatusPage, and Trello. As part of a security and compliance uplift, we had scheduled the deletion of unused and legacy domain names used for internal service-to-service connections. Active domain names were incorrectly deleted during this event. This impacted all cloud customers across all regions. The issue was identified and resolved through the rollback of the faulty deployment to restore the domain names and Atlassian systems to a stable state. The time to resolution was two hours and 58 minutes. ### **IMPACT** External customers started reporting issues with Atlassian cloud products at 20:52 UTC. The impact of the failed change led to performance degradation or in some cases, complete service disruption. Symptoms experienced by end-users were unsuccessful page loads and/or failed interactions with our cloud products. ### **ROOT CAUSE** As part of a security and compliance uplift, we had scheduled the deletion of unused and legacy domain names that were being used for internal service-to-service connections. Active domain names were incorrectly deleted during this operation. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. The detection was delayed because existing testing & monitoring focused on service health rather than the entire system’s availability. To prevent a recurrence of this type of incident, we are implementing the following improvement measures: * Canary checks to monitor the entire system availability. * Faster rollback procedures for this type of service impact. * Stricter change control procedures for infrastructure modifications. * Migration of all DNS records to centralised management and stricter access controls on modification to DNS records. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. ‌ Thanks, Atlassian Customer Support

Time: Feb. 27, 2024, 5:45 a.m.

Status: Postmortem

Update: ### **Summary** On February 14, 2024, between 20:05 UTC and 23:03 UTC, Atlassian customers on the following cloud products encountered a service disruption: Access, Atlas, Atlassian Analytics, Bitbucket, Compass, Confluence, Ecosystem apps, Jira Service Management, Jira Software, Jira Work Management, Jira Product Discovery, Opsgenie, StatusPage, and Trello. As part of a security and compliance uplift, we had scheduled the deletion of unused and legacy domain names used for internal service-to-service connections. Active domain names were incorrectly deleted during this event. This impacted all cloud customers across all regions. The issue was identified and resolved through the rollback of the faulty deployment to restore the domain names and Atlassian systems to a stable state. The time to resolution was two hours and 58 minutes. ### **IMPACT** External customers started reporting issues with Atlassian cloud products at 20:52 UTC. The impact of the failed change led to performance degradation or in some cases, complete service disruption. Symptoms experienced by end-users were unsuccessful page loads and/or failed interactions with our cloud products. ### **ROOT CAUSE** As part of a security and compliance uplift, we had scheduled the deletion of unused and legacy domain names that were being used for internal service-to-service connections. Active domain names were incorrectly deleted during this operation. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. The detection was delayed because existing testing & monitoring focused on service health rather than the entire system’s availability. To prevent a recurrence of this type of incident, we are implementing the following improvement measures: * Canary checks to monitor the entire system availability. * Faster rollback procedures for this type of service impact. * Stricter change control procedures for infrastructure modifications. * Migration of all DNS records to centralised management and stricter access controls on modification to DNS records. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. ‌ Thanks, Atlassian Customer Support

Time: Feb. 14, 2024, 11:32 p.m.

Status: Resolved

Update: We experienced increased errors on Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, Trello, Atlassian Bitbucket, Atlassian Access, Jira Align, Jira Product Discovery, Atlas, Compass, and Atlassian Analytics. The issue has been resolved and the services are operating normally.

Time: Feb. 14, 2024, 11:32 p.m.

Status: Resolved

Update: We experienced increased errors on Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, Trello, Atlassian Bitbucket, Atlassian Access, Jira Align, Jira Product Discovery, Atlas, Compass, and Atlassian Analytics. The issue has been resolved and the services are operating normally.

Time: Feb. 14, 2024, 10:55 p.m.

Status: Monitoring

Update: We have identified the root cause of the Service Disruptions affecting all Atlassian products and have mitigated the problem. We are now monitoring this closely.

Time: Feb. 14, 2024, 10:55 p.m.

Status: Monitoring

Update: We have identified the root cause of the Service Disruptions affecting all Atlassian products and have mitigated the problem. We are now monitoring this closely.

Time: Feb. 14, 2024, 10:31 p.m.

Status: Identified

Update: We have identified the root cause of the increased errors and have mitigated the problem. We continue to work on resolving the issue and monitoring this closely.

Time: Feb. 14, 2024, 10:31 p.m.

Status: Identified

Update: We have identified the root cause of the increased errors and have mitigated the problem. We continue to work on resolving the issue and monitoring this closely.

Time: Feb. 14, 2024, 9:57 p.m.

Status: Investigating

Update: We are investigating reports of intermittent errors for all Cloud Customers across all Atlassian products. We will provide more details once we identify the root cause.

Time: Feb. 14, 2024, 9:57 p.m.

Status: Investigating

Update: We are investigating reports of intermittent errors for all Cloud Customers across all Atlassian products. We will provide more details once we identify the root cause.

Time: Feb. 13, 2024, 6:27 a.m.

Status: Resolved

Update: Between 2024-02-12 21:00 UTC to 2024-02-13 05:52 UTC, we experienced mentioned user name showing as @User that impacted some Jira Cloud customers. The issue has been resolved and the service is operating normally.

Time: Feb. 13, 2024, 3:56 a.m.

Status: Identified

Update: We continue to work on resolving the mention issue for Jira. We have identified the root cause and expect recovery shortly.

Time: Feb. 13, 2024, 3:26 a.m.

Status: Investigating

Update: We are continuing to investigate this issue.

Time: Feb. 13, 2024, 2:12 a.m.

Status: Investigating

Update: We are investigating an issue with user name showing as @User for mention that is impacting some Jira Cloud customers. We will provide more details within the next hour.

Time: Feb. 13, 2024, 6:27 a.m.

Status: Resolved

Update: Between 2024-02-12 21:00 UTC to 2024-02-13 05:52 UTC, we experienced mentioned user name showing as @User that impacted some Jira Cloud customers. The issue has been resolved and the service is operating normally.

Time: Feb. 13, 2024, 3:56 a.m.

Status: Identified

Update: We continue to work on resolving the mention issue for Jira. We have identified the root cause and expect recovery shortly.

Time: Feb. 13, 2024, 3:26 a.m.

Status: Investigating

Update: We are continuing to investigate this issue.

Time: Feb. 13, 2024, 2:12 a.m.

Status: Investigating

Update: We are investigating an issue with user name showing as @User for mention that is impacting some Jira Cloud customers. We will provide more details within the next hour.

Time: Feb. 12, 2024, 8 p.m.

Status: Resolved

Update: Between February 9, 4 PM UTC to February 12, 5:49 PM UTC, we experienced degraded performance related to Invitations on Confluence and Jira Software Cloud. The issue has been resolved and the service is operating normally.

Time: Feb. 12, 2024, 5:11 p.m.

Status: Identified

Update: We are experiencing intermittent issues with the Invite flow for new accounts on Jira and Confluence Cloud. The team identified the issue and we are in the process of pushing the fix to all affected customers.

Time: Feb. 12, 2024, 3:27 p.m.

Status: Investigating

Update: We are continuing to investigate this issue.

Time: Feb. 12, 2024, 3:03 p.m.

Status: Investigating

Update: We are investigating cases of degraded performance/accessibility for some Jira Cloud customers. We will provide more details within the next 2 hours.