https://approjects-vendor-status-watch.static.hf.space/v/atlassian-partners.htmlIncidents from Atlassian Partners's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/c4qcqpj1t4dratlassian-partners:2026-05-14T05:11:20.126ZThu, 14 May 2026 05:11:20 +0000### Summary On May 14, 2026, between 04:30 and 05:26 UTC, Atlassian customers experienced widespread service disruption across multiple Atlassian Cloud products. The issue was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products. The incident was detected within a minute by automated monitoring systems and mitigated in 56 minutes. ### **IMPACT** During the incident, customers attempting to access Atlassian Cloud products in the us-east region experienced authentication and permission failures and were unable to access serviceshttps://stspg.io/smlqssl6b4h4atlassian-partners:2026-05-07T02:27:15.303ZThu, 07 May 2026 02:27:15 +0000Users attempting to access the Atlassian shop will now be directed to our Homepage. This will prevent ongoing security related error messages from being presented in the meantime while the shop is able to be restored to its full functionality. Please reach out to Atlassian Support for additional assistance if required.https://stspg.io/f1lkjdfrv1cpatlassian-partners:2025-10-20T07:56:11.485ZMon, 20 Oct 2025 07:56:11 +0000### Postmortem publish date: Nov 19th, 2025 ### Summary All dates and times below are in UTC unless stated otherwise. Customers utilizing Atlassian products experienced elevated error rates and degraded performance between Oct 20, 2025 06:48 and Oct 21, 2025 04:05. The service disruptions were triggered due to an [AWS DynamoDB outage](https://aws.amazon.com/message/101925/#:~:text=1%3A50%20PM.-,DynamoDB,-Between%2011%3A48) and further affected by subsequent failures in [AWS EC2](https://aws.amazon.com/message/101925/#:~:text=service%20disruption%20event.-,Amazon%20EC2,-Between%2011%3A48) and [AWS Network Load Balancer](https://aws.amazon.com/message/101925/#:~:text=service%20disruption%20event.-,Amazon%20EC2,-Between%2011%3A48) within the us-east-1 region. The incident started at Oct 2