Confluence Outage History

Started Dec 15, 2025, 04:26 PM UTC· resolved Dec 15, 2025, 07:01 PM UTC

1. identified Dec 15, 2025, 04:26 PM UTC

   We are actively investigating reports of performance degradation affecting Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, Jira Work Management, and Rovo. We'll share updates here as more information is available.

2. identified Dec 15, 2025, 04:47 PM UTC

   We have identified the cause of the issue, and our teams are diligently working on mitigations. We're currently seeing signs of improvements. We'll continue to share additional updates here in 60 minutes or as more information becomes available.

3. identified Dec 15, 2025, 05:47 PM UTC

   Our teams are continuing to implement mitigations. Error rates have decreased across all products and we are seeing improvements. We will continue to provide updates here in 60 minutes or as more information becomes available.

4. resolved Dec 15, 2025, 07:01 PM UTC

   On December 15th, 2025, Admin Hub, Atlassian Analytics, Confluence Cloud, Ecosystem, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo users in the prod-us-east region may have experienced performance degradations and errors on the web page and mobile apps. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Dec 11, 2025, 01:08 AM UTC· resolved Dec 11, 2025, 04:37 AM UTC

1. investigating Dec 11, 2025, 01:08 AM UTC

   We are aware that customers are currently experiencing installation failures when attempting to install Connect on Forge apps into Confluence. Our team is investigating with urgency and we will provide an update within the hour.

2. identified Dec 11, 2025, 02:08 AM UTC

   Our team has identified a root cause for this issue, and have now commenced a rollback of the problematic change and verifying that this is resolved. There should not be any impact to currently installed apps as a result of this incident. However, we are aware that cloud migrations including Confluence Apps may also currently be blocked by this issue. We currently expect the rollback and validation of the fix to be completed within 3 hours. We will update further at that time with the latest status.

3. resolved Dec 11, 2025, 04:37 AM UTC

   The rollback required to resolve this issue is now completed, and we have verified across the impacted products that App installation behaviour is now working as expected. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Nov 21, 2025, 02:55 PM UTC· resolved Nov 21, 2025, 04:49 PM UTC

1. investigating Nov 21, 2025, 02:55 PM UTC

   Multiple Atlassian services are seeing outages and we are investigating the same. We shall keep you posted on the progress in 60 minutes, if not sooner

2. investigating Nov 21, 2025, 03:30 PM UTC

   Multiple Atlassian services are experiencing degraded performance. We are investigating and will provide an update within the hour.

3. monitoring Nov 21, 2025, 04:14 PM UTC

   The Trello performance degradation affecting some customers has been resolved. A subset of customers may have experienced intermittent errors on some of our other products, but these should also now be resolved too. We'll continue to monitor closely to confirm stability.

4. resolved Nov 21, 2025, 04:49 PM UTC

   The Trello performance degradation has been resolved. Also, some intermittent errors on some of our other products, has also now been resolved. The issue has now been resolved, and the service is operating normally for all affected customers.

5. postmortem Dec 08, 2025, 05:25 AM UTC

   ### Summary On November 21, 2025, between 13:44 and 15:16 UTC, Trello customers were intermittently unable to view and update data on their boards. Customers also may have experienced issues authenticating with Atlassian products, and creating new GitHub and Slack integrations. The event was triggered by a bug encountered in the software running our edge proxy fleet, which proxies customer traffic to Atlassian cloud services. The changes included the migration of our edge proxy fleet to hosts running an ARM CPU architecture, rather than the AMD64 CPU architecture they had previously been running, which impacted US East customers. The incident was detected within 1 minute by our automated monitoring systems, and mitigated by a scale up of of fleet size, which put Atlassian systems into a known good state. This was followed by a global migration of edge proxy fleet hosts back to AMD64 CPU architecture the following day. ### **IMPACT** During the impact window, US East customers intermittently could not view or update data in Trello. The same underlying issue also impacted our Identity services and integrations with GitHub and Slack, meaning some customers had trouble signing in to Atlassian products or creating new integrations. At the incident’s peak, the incident impacted up to: * 52% of new Trello network connections. * 9% of new GitHub and Slack integrations. * 8% of new Identity network connections. ### **ROOT CAUSE** The issue was caused by a change to CPU architecture from AMD64 to ARM on our edge proxy fleet. This led to a bug that caused these instances to stall under high load, and refuse up to 52% of new connections. As a result, some customers of the products above could not make new connections to Atlassian services, and customers received CloudFront 504 gateway timeout error responses. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. While we deploy our changes progressively by cloud region to avoid broad impact, on this occasion, our pre-change load testing had not accurately reflected production loads. As part of our response to this incident, and to help prevent recurrence, we rolled back all edge proxy fleets from ARM to AMD64 CPU architecture globally. To minimise the impact of breaking changes to our environments, we plan to implement additional preventative measures such as: * Adding improved load tests into edge proxy fleet deployment pipelines to catch load-related bugs before deployment to production. * Adding alerts to our edge proxy fleet to catch rises in TCP connect times before customer impact. We apologize to customers whose services were impacted during this incident; we are taking steps to help improve the platform’s performance and availability. Thanks, Atlassian Customer Support

Read the full incident report →

Started Nov 18, 2025, 01:32 PM UTC· resolved Nov 18, 2025, 04:57 PM UTC

1. investigating Nov 18, 2025, 01:32 PM UTC

   We are aware of a global Cloudflare issue affecting Confluence Whiteboards and are currently looking into the issue.

2. investigating Nov 18, 2025, 01:35 PM UTC

   We are aware of a global Cloudflare issue affecting Confluence Whiteboards and are currently looking into the issue.

3. investigating Nov 18, 2025, 01:37 PM UTC

   We are aware of a global Cloudflare issue affecting Confluence Whiteboards and are currently looking into the issue.

4. investigating Nov 18, 2025, 02:40 PM UTC

   We are aware of a global Cloudflare issue that is currently impacting Confluence. You may notice elevated server errors in Confluence Whiteboards and Databases. Cloudflare is actively working to restore its services, and we are closely monitoring its progress. We understand how disruptive this can be and truly appreciate your patience as we monitor the situation. We will continue to provide updates as we learn more.

5. identified Nov 18, 2025, 03:58 PM UTC

   We are aware of a global Cloudflare issue that is currently impacting Confluence. Cloudflare is reporting that a fix has been implemented and services are restoring. Our engineering teams continue to monitor the restoration of services. It is possible that you may still encounter some errors or issues. We will update you when services are fully restored. We will continue to provide updates as we learn more.

6. resolved Nov 18, 2025, 04:57 PM UTC

   Elevated Errors in Confluence Whiteboards and Databases Due to Cloudflare Outage Cloudflare successfully deployed a fix for the issue that was impacting Confluence. We are no longer seeing Confluence system performance degradation and Confluence systems have been fully restored. We will continue monitoring

Read the full incident report →

Started Nov 18, 2025, 02:55 AM UTC· resolved Nov 18, 2025, 03:35 AM UTC

1. investigating Nov 18, 2025, 02:55 AM UTC

   We are aware of some customers being impacted by an error in Confluence while attempting to edit content stating 'We've lost our connection to you. Your changes will be saved when we reconnect. Trying to reconnect...'. Our team is investigating with urgency and will provide another update within an hour.

2. monitoring Nov 18, 2025, 03:16 AM UTC

   Our team has reverted a recent change that is suspected to have caused these errors, and have seen instances of these error messages to decrease. We are continuing to monitor and will update when this issue is confirmed to be resolved.

3. resolved Nov 18, 2025, 03:35 AM UTC

   Our team has been able to confirm that customers should no longer be experiencing the error while attempting to edit using Confluence. We apologize for any inconvenience this may have caused. This issue is now resolved.

Read the full incident report →

Started Nov 03, 2025, 04:11 PM UTC· resolved Nov 03, 2025, 06:08 PM UTC

1. investigating Nov 03, 2025, 04:11 PM UTC

   We are investigating reports of degraded performance and intermittent errors for some Confluence, Jira Service Management, and Jira Cloud customers. We will provide more details in one hour, if not sooner.

2. investigating Nov 03, 2025, 05:15 PM UTC

   We are continuing to investigate the cause of degraded performance and intermittent errors impacting Automations and the Automation UI for some Confluence, Jira Service Management, and Jira Cloud customers. We will provide more details in one hour, if not sooner.

3. resolved Nov 03, 2025, 06:08 PM UTC

   On November 3, 2025, some Confluence, Jira Service Management, and Jira Cloud users may have experienced performance degradation and errors in the Global Automation UI page. Automation executions were not impacted by this incident. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Oct 29, 2025, 06:47 AM UTC· resolved Oct 30, 2025, 02:09 AM UTC

1. investigating Oct 29, 2025, 06:47 AM UTC

   We have reports of some users in Australia seeing degraded performance of Atlassian cloud. Our team is investigating this and we shall keep you informed in next 60 minutes or sooner.

2. investigating Oct 29, 2025, 06:57 AM UTC

   Considering the complexity and intermittent nature of this issue. Atlassian team believes that further investigation of this issue is required and we will reach out to some of the impacted customers for specific information. Based on the above, we shall be able to provide further update in next 24 hours, if not sooner

3. investigating Oct 29, 2025, 06:58 AM UTC

   Considering the complexity and intermittent nature of this issue. Atlassian team believes that further investigation of this issue is required and we will reach out to some of the impacted customers for specific information. Based on the above, we shall be able to provide further update in next 24 hours, if not sooner.

4. investigating Oct 30, 2025, 02:08 AM UTC

   Working with our infrastructure provider, our team has been able to identify specific CDN hardware changes that were rolling out this week, and are expected to be correlated to the performance issues some customers have seen loading pages in Jira and Confluence in specific countries, including Australia, Japan, Germany, Spain, Brazil and the USA. Our provider has indicated that this rollout has now been halted indefinitely and the rollout reverted, to restore expected levels of service across all impacted countries. Our network error logging from browser data shows that this mitigation was successful, and we've now received multiple confirmations from previously impacted customers following this change that services have restored. We sincerely apologize for any inconvenience this has caused. If you are continuing to experience any issues please reach out to Atlassian Support.

5. resolved Oct 30, 2025, 02:09 AM UTC

   Incident has been resolved.

Read the full incident report →

Started Oct 24, 2025, 06:31 AM UTC· resolved Oct 24, 2025, 09:18 AM UTC

1. investigating Oct 24, 2025, 06:31 AM UTC

   Multiple customers in APSE region are experience failure accessing Confluence application. We are currently investigating.

2. investigating Oct 24, 2025, 07:04 AM UTC

   We have an active line of investigation. Will update with results within 30 minutes.

3. investigating Oct 24, 2025, 07:42 AM UTC

   Addressed one potential cause of load in the affected region. Monitoring for results and continuing to pursue other leads.

4. investigating Oct 24, 2025, 08:26 AM UTC

   We are seeing reduced error volumes now which indicate improvement in Confluence availability. Continuing to monitor and investigate/validate root causes.

5. investigating Oct 24, 2025, 09:10 AM UTC

   We have addressed an issue causing increased database load and seeing recovery of user experience. Will continue to monitor before resolving issue.

6. investigating Oct 24, 2025, 09:18 AM UTC

   We see a full recovery in Confluence application experience in the affected AP SouthEast region now.

7. resolved Oct 24, 2025, 09:18 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 22, 2025, 06:20 AM UTC· resolved Oct 22, 2025, 06:47 AM UTC

1. investigating Oct 22, 2025, 06:20 AM UTC

   We understand that our customers are experiencing delay in execution of Automation rules. While our team is investigating further on this, it looks like a follow-on effect of the recent AWS outage. We continue to investigate further on this and we shall keep you informed of the progress every hour if not sooner.

2. identified Oct 22, 2025, 06:34 AM UTC

   Atlassian team has identified the cause of the issue that led to delay in execution of Automation rules. This is a follow-on effect of the recent AWS outage. We shall keep you informed of the progress every hour, if not sooner.

3. resolved Oct 22, 2025, 06:47 AM UTC

   Our teams have identified and fixed the root cause of the issue that caused delay in executing Automation rules. This was caused due to scaling issues following on from the recent AWS outage. This issue is marked as resolved.

Read the full incident report →

Started Oct 20, 2025, 07:56 AM UTC· resolved Oct 21, 2025, 05:24 AM UTC

1. investigating Oct 20, 2025, 07:56 AM UTC

   We have noticed that Atlassian Cloud services are impacted and our teams are actively investigating the same. We shall keep you informed of the progress every hour.

2. investigating Oct 20, 2025, 08:24 AM UTC

   Atlassian Cloud services are impacted and we are aware that our customers might not be able to create support tickets. Our teams are actively investigating the same. We shall keep you informed of the progress every hour.

3. investigating Oct 20, 2025, 09:23 AM UTC

   We are experiencing an outage due to some issue at the end of our public cloud provider. We are working closely with them to get this resolved or mitigated as quickly as possible. ETA of the same is not know at the moment. We shall continue to share updates every hour, if not sooner.

4. investigating Oct 20, 2025, 09:24 AM UTC

   We are experiencing an outage due to some issue at the end of our public cloud provider. We are working closely with them to get this resolved or mitigated as quickly as possible. ETA of the same is not know at the moment. We shall continue to share updates every hour, if not sooner.

5. identified Oct 20, 2025, 09:58 AM UTC

   We understand that our public cloud provider has identified the cause of the issue. We are starting to see some recovery and is working towards mitigation. We appreciate your patience. We shall continue to share updates every hour, if not sooner.

6. identified Oct 20, 2025, 11:07 AM UTC

   We continue to work with our public cloud provider towards mitigating the issue at the earliest. We appreciate your patience. We shall continue to share updates every hour, if not sooner.

7. identified Oct 20, 2025, 12:06 PM UTC

   Atlassian team is actively engaged and continues to work with our public cloud provider to mitigate this issue at the earliest. We are starting to see partial operations succeed. We appreciate your patience. We shall continue to share updates every hour, if not sooner.

8. identified Oct 20, 2025, 01:07 PM UTC

   Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.

9. identified Oct 20, 2025, 01:56 PM UTC

   Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.

10. identified Oct 20, 2025, 01:58 PM UTC

    Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.

11. identified Oct 20, 2025, 02:02 PM UTC

    We understand your pain and mitigating or fixing this issue is of utmost importance. Our public cloud provider is actively working to mitigate this issue on priority. We have been seeing partial operational success. We appreciate your patience and will continue to provide updates every hour or sooner.

12. identified Oct 20, 2025, 03:20 PM UTC

    Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available.

13. identified Oct 20, 2025, 03:22 PM UTC

    Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available.

14. identified Oct 20, 2025, 04:35 PM UTC

    Update - Thank you for your continued patience. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is still actively working to mitigate this issue with urgency and while we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will be providing hourly updates on this issue.

15. identified Oct 20, 2025, 05:27 PM UTC

    Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available.

16. identified Oct 20, 2025, 05:43 PM UTC

    We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority and we are closely monitoring the health of AWS services. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available.

17. monitoring Oct 20, 2025, 06:38 PM UTC

    There have been no changes since our last update. We will provide our next updated by 9:00PM UTC or sooner as new information becomes available. We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority and we are closely monitoring the health of AWS services. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation.

18. monitoring Oct 20, 2025, 09:26 PM UTC

    Monitoring - We've started seeing continued product experience improvement. While we still have a backlog of event processing, we are seeing improvements in systems operational capabilities across all products. We estimate a significant improvement with the next few hours and will continue to monitor the health of AWS services and the effects on Atlassian customers. We appreciate your continued patience and remain committed to full resolution as we work through this situation. We will post our next update in two hours.

19. monitoring Oct 20, 2025, 10:58 PM UTC

    Our teams are continuing to monitor the recovery of systems across Atlassian products. This update is to inform that the Atlassian Support portal is fully operational at this time for customers that wish to contact support.

20. monitoring Oct 21, 2025, 12:03 AM UTC

    Our team is now seeing recovery across all impacted Atlassian products. We are continuing to monitor for individual products that may still be processing backlogged items now that services are restored. The Atlassian Support portal is currently still displaying a message directing customers to our temporary support channel. Please note that our support portal is currently fully functional for those attempting to raise requests. We are continuing to look into this alert to remove this message. We will provide further update on our recovery status in one hour.

21. monitoring Oct 21, 2025, 01:07 AM UTC

    We continue to see recovery progressing across all impacted products as backlogged items continue to be processed. The Atlassian Support portal is currently displaying a message directing customers to our temporary support channel. Please note that our support portal is currently fully functional for those attempting to raise requests. We are continuing to look into this alert to remove this message. We will provide further update on our recovery status in two hours.

22. monitoring Oct 21, 2025, 03:24 AM UTC

    The issue relating to the Atlassian Support portal displaying a message to customers to use our temporary support channel has now been resolved. The Atlassian Support portal is fully functional for any ongoing support issues. With regards to other Atlassian products, we continue to see recovery continuing across all impacted products and our teams are continuing to monitor as the recovery continues. We will provide further update on our recovery status within two hours.

23. resolved Oct 21, 2025, 05:24 AM UTC

    Our team is now able to see full recovery across the vast majority of Atlassian products. We are aware of some ongoing issues with specific components such as migrations and JSM virtual service agents, and our team is continuing to investigate with urgency. We apologise for the inconvenience that this incident has caused and we will provide further information when the Post Incident Investigation has been completed.

24. postmortem Oct 24, 2025, 05:48 PM UTC

    ### 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 20, 2025 06:48 and was detected within six minutes by our automated monitoring systems. Our teams worked to restore all core services by Oct 21, 2025 04:05. Final cleanup of backlogged processes and minor issues was completed on Oct 22, 2025. We recognize the critical role our products play in your daily operations, and we offer our sincere apologies for any impact this incident had on your teams. We are taking immediate steps to enhance the reliability and performance of our services, so that you continue to receive the standard of service you have come to trust. ### IMPACT Before examining product-level impacts, it's helpful to understand Atlassian's service topology and internal dependencies. Products such as Jira and Confluence are deployed across multiple AWS regions. The data for each tenant is stored and processed exclusively within its designated host region. This design is intentional and represents the desired operational state, as it limits the impact of any regional outage strictly to tenants in-region, in this case us-east-1. While in-scope application data is pinned to the region selected by the customer, there are times when systems need to call other internal services that may be based in a different region. If a problem occurs in the main region where these services operate, systems are designed to automatically fail over to a backup region, usually within three minutes. However, if unexpected issues arise during this failover, it can take longer to restore services. In rare cases, this could affect customers in more than one region. It’s important to note that all in-scope application data for supported products is pinned according to a customer’s chosen region. **Jira** Between Oct 20, 2025 06:48 and Oct 20, 2025 20:00, customers with tenants hosted in the us-east-1 region experienced increased error rates when accessing core entities such as Issues, Boards, and Backlogs. This disruption was caused by AWS's inability to allocate AWS EC2 instances and elevated errors in AWS Network Load Balancer \(NLB\). During this window, users may also have observed intermittent timeouts, slow page loads, and failures when performing operations like creating or updating issues, loading board views, and executing workflow transitions. Between Oct 20, 2025 08:36 and Oct 20, 2025 09:23, customers across all regions experienced elevated failure rates when attempting to load Jira pages. This disruption was caused by the regional frontend service entering an unhealthy state during this specific time interval. Normally, the frontend service connects to the primary AWS DynamoDB instance located in the us-east-1 to retrieve the most recent configuration data necessary for proper operation. Additionally, the service is designed with a fallback mechanism that references static configuration data in the event that the primary database becomes inaccessible. Unfortunately, a latent bug existed in the local fallback path. When the frontend service nodes restarted, they were unable to load critical operational configuration data from primary or fallback sources, leading to the observed failures experienced by customers. Between Oct 20, 2025 06:48 and Oct 21, 2025 06:30, customers experienced significant delays and missing Jira in-app notifications across all regions. The notification ingestion service, which is hosted exclusively in us-east-1, exhibited an increased failure rate when processing notification messages due to AWS EC2 and NLB issues. This issue resulted in notifications being delayed - and in some cases, not delivered at all - to users worldwide. **Jira Service Management \(JSM\)** JSM was impacted similarly to Jira above, with the same timeframes and for the same reasons. Between Oct 20, 2025 08:36 and Oct 20, 2025 09:23, customers across all regions experienced significantly elevated failure rates when attempting to load JSM pages. This affected all JSM experiences including the Help Centre, Portal, Queues, Work Items, Operations, and Alerts. **Confluence** Between Oct 20, 2025 06:48 and Oct 21, 2025 02:45, customers using Confluence in the us-east-1 region experienced elevated failure rates when performing common operations such as editing pages or adding comments. The primary cause of this service degradation was the system's inability to auto-scale due to AWS EC2 issues to manage peak traffic load effectively. Though the AWS outage ended at Oct 20, 21:09, a subset of customers continued to experience failures as some Confluence web server nodes across multiple clusters remained in an unhealthy state. This was ultimately mitigated by recycling the affected nodes. To protect our systems while AWS recovered, we made a deliberate decision to enable node termination protection. This action successfully preserved our server capacity but, as a trade-off, it extended the time required for a full recovery once AWS services were restored. **Automation** Between Oct 20, 2025 06:55 and Oct 20, 2025 23:59, automation customers whose rules are processed in us-east-1 experienced delays of up to 23 hours in rule execution. During this window, some events triggering rule executions were processed out of order because they arrived later during backlog processing. This caused potential inconsistencies in workflow executions, as rules were run in the order events were received, not when the action causing the event occurred. Additionally, some rule actions failed because they depend on first-party and third-party systems, which were also affected by the AWS outage. Customers can see most of these failures in their audit logs; however, a few updates were not logged due to the nature of the outage. By Oct 21, 2025 5:30, the backlog of rule runs in us-east-1 was cleared. Although most of these delayed rules were successfully handled, there were some additional replays of events to ensure completeness. Our investigation confirmed that a few events may never have triggered their associated rules due to the outage. Between Oct 20, 2025 06:55 and Oct 20, 2025 11:20, all non-us-east-1 regional automation services experienced delays of up to 4 hours in rule execution. This was caused by an upstream service that was unable to deliver events as expected. The delivery service encountered a failure due to a cross-region dependency call to a service hosted in the us-east-1 region. Because of this dependency issue, the delivery service was unable to successfully deliver events throughout this time frame, resulting in customer-defined rules not being executed in a timely manner. **Bitbucket and Pipelines** Between Oct 20, 2025 06:48 and Oct 20, 2025 09:33, Bitbucket experienced intermittent unavailability across core services. During this period, users faced increased error rates and latency when signing in, navigating repositories, and performing essential actions such as creating, updating, or approving pull requests. The primary cause was an AWS DynamoDB outage that impacted downstream services. Between Oct 20, 2025 06:48 and Oct 20, 2025 22:46, numerous Bitbucket Pipeline steps failed to start, stalled mid-execution, or experienced significant queueing delays. Impact varied, with partial recoveries followed by degradation as downstream components re-synchronized. The primary cause was an AWS DynamoDB outage, compounded by instability in AWS EC2 instance availability and AWS Network Load Balancers. Furthermore, Bitbucket Pipelines continued to experience a low but persistent rate of step timeouts and scheduling errors due to AWS bare-metal capacity shortages in select availability zones. Atlassian coordinated with AWS to provision additional bare-metal hosts and addressed a significant backlog of pending pods, successfully restoring services by 01:30 on Oct 21, 2025. **Trello** Between Oct 20, 2025 06:48 and Oct 20, 2025 15:25, users of Trello experienced widespread service degradation and intermittent failures due to upstream AWS issues affecting multiple components, including AWS DynamoDB and subsequent AWS EC2 capacity constraints. During this period, customers reported elevated error rates when loading boards, opening cards, adding comments or attachments. **Login** Between Oct 20, 2025 06:48 and Oct 20, 2025 09:30, a small subset of users experienced failures when attempting to initiate new login sessions using SAML tokens. This resulted in an inability for those users to access Atlassian products during that time period. However, users who already had valid active sessions were not affected by this issue and continued to have uninterrupted access. The issue impacted all regions globally because regional identity services relied on a write replica located in the us-east-1 region to synchronize profile data. When the primary region became unavailable, the failover to a secondary database in another region failed, which delayed recovery. This failover defect has since been addressed. **Statuspage** Between Oct 20, 2025 06:48 and Oct 20, 2025 09:30, Statuspage customers who were not already logged in to the management portal were unable to log in to create or update incident statuses. This impact was restricted only to users who were not already logged in at the time. The root cause was the same as described in the Login section above, and it was resolved by the same remediation steps. ### REMEDIAL ACTION PLAN & NEXT STEPS We have completed the following critical actions designed to help prevent cross-region impact from similar issues: * Resolved the code defect in the fallback option to ensure that Jira Frontend Services in other regions remain unaffected during a region-wide outage. * Fixed the issue that prevented timely failover of the identity service which impacted new login sessions. * Resolved the code defect so that delivery services in unaffected regions remain operational during region-wide outages. Additionally, we are prioritizing the following improvement actions: * Implement mitigation strategies to strengthen resilience against region-wide outages in the notification ingestion service. Although disruptions to our cloud services are sometimes unavoidable during outages of the underlying cloud provider, we continuously evaluate and improve test coverage to strengthen resilience of our cloud services against these issues. We recognize the critical importance of our products to your daily operations and overall productivity, and we extend our sincere apologies for any disruptions this incident may have caused your teams. If you were impacted and require additional details for internal post-incident reviews, please reach out to your Atlassian support representative with affected timeframes and tenant identifiers so we can correlate logs and provide guidance. Thanks, Atlassian Customer Support

Read the full incident report →

Started Oct 15, 2025, 01:43 PM UTC· resolved Oct 15, 2025, 04:16 PM UTC

1. investigating Oct 15, 2025, 01:43 PM UTC

   UI based Customer interactions are currently degraded and our team is actively investigating the same. We shall keep you informed of the progress in next 2 hours.

2. investigating Oct 15, 2025, 02:34 PM UTC

   Atlassian team is actively investigating the issue with UI based Customer interactions. Existing automation rules continue to run without any issue. Accessing automation rules and creating new automation rules could lead to intermittent failures. We shall keep you informed of the progress in next 2 hours, if not sooner.

3. monitoring Oct 15, 2025, 03:26 PM UTC

   We have recovered from a issue which saw degraded Automation experience. Impact Some Customers using Jira, Confluence, and Jira Service Management were not able to create or update Automation rules, and some Automation rules which triggered webhooks might have been throttled and require re-running. Current Status The incident has been mitigated and we continue to investigate the cause of this incident Next Steps We are continuing to monitor the service, and will provide further updates in the next two hours

4. resolved Oct 15, 2025, 04:16 PM UTC

   Between 14:00 UTC to 16:00 UTC, we experienced automation rule functionality degradation for Confluence, Jira Work Management, Jira Service Management, and Jira. Impact Some customers using Jira, Confluence, and Jira Service Management were not able to create or update Automation rules, and some Automation rules which triggered webhooks might have been throttled and require re-running. Approximately 50 percent of Automation API calls were affected in the us-east-1 region with customers receiving 429 status codes. Current Status The incident has been mitigated by increasing the API Gateway rate limit service quota and disabling the internal service that was causing high traffic volume. Next Steps We are conducting a root cause analysis of the internal service. A post incident review will be conducted.

Read the full incident report →

Started Sep 30, 2025, 05:15 PM UTC· resolved Oct 01, 2025, 05:15 PM UTC

1. resolved Oct 08, 2025, 09:46 PM UTC

   On September 29-30 2025, for about 24 hours, Confluence Cloud experienced an incident due to the unintended deprecation of ACJS methods (https://developer.atlassian.com/cloud/confluence/about-the-connect-javascript-api/#connect-javascript-api) linked to retired V1 APIs (https://developer.atlassian.com/cloud/confluence/rest/v1/), resulting in 410 errors affecting partners reliant on these APIs. This issue is resolved, we will be working on a longer-term solution to prevent a similar incident from occurring again.

Read the full incident report →

Started Sep 22, 2025, 05:09 AM UTC· resolved Sep 22, 2025, 07:17 AM UTC

1. investigating Sep 22, 2025, 05:09 AM UTC

   Our team is aware that access to Jira and Confluence cloud products was degraded between 04:39 and 04:52 UTC due to an erroneous certificate. The certificate has now been corrected and functionality has been restored. We are continuing to monitor the situation and will provide further update when available.

2. identified Sep 22, 2025, 05:38 AM UTC

   Our team is continuing to monitor Jira and Confluence products following the earlier issues relating to an erroneous certificate change. We are assessing all impacted products to ensure that services are fully restored and we will provide further update within the hour.

3. identified Sep 22, 2025, 05:59 AM UTC

   Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

4. monitoring Sep 22, 2025, 06:55 AM UTC

   Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

5. resolved Sep 22, 2025, 07:17 AM UTC

   A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

6. postmortem Oct 01, 2025, 06:20 AM UTC

   ### **SUMMARY** On September 22, 2025, between 04:38 and 04:48 UTC, Atlassian customers experienced connection errors preventing access to their [atlassian.net](http://atlassian.net/) sites. Some customers observed intermittent errors as services gradually recovered until 06:17 UTC. The event was triggered by a faulty configuration change to our Content Delivery Network \(CDN\). The change included an invalid hostname which prevented customers from successfully connecting to [atlassian.net](http://atlassian.net/) domains. The incident was detected within 1 minute by our monitoring systems and mitigated by rolling back the change, which put Atlassian systems into a known good state. The acute impact was resolved in 10 minutes and all lingering errors resolved in 1 hour 38 minutes. ### **IMPACT** The acute impact occurred on September 22, 2025, between 04:38 UTC and 04:48 UTC to Confluence, Compass and Jira, including Jira Service Management. The incident caused service disruption to customers when they attempted to load those products in their browser or interact with APIs. Between 04:48 UTC and 06:17 UTC some customers continued to observe intermittent errors as services gradually recovered. ### **ROOT CAUSE** The issue was caused by a change to the hostname configuration of our Content Delivery Network \(CDN\). As a result, the products mentioned could not receive connections, and the users received TLS handshake errors, followed by HTTP 503 and 403 errors. More specifically a new CDN configuration contained a resource name which conflicted with the existing customer-serving CDN resource, and was able to be deployed, overwriting it. The root cause of the incident was the failure in the detection of the bug by our pre-deployment validations and tests. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that you rely on our products for your daily operations and productivity, and we sincerely apologize for any impact this disruption has had on you, your team or your organisation. We are prioritizing the following improvement actions to help avoid repeating this type of incident: * Improved pre-deployment change controls and testing. * Improved validation of target configurations before deployment to ensure customer-serving CDN resources cannot their hostnames changed. * Sharding of our CDN configuration to enable progressive changes. We sincerely appreciate your understanding and patience as we improve our processes to provide a better customer experience. Thank you, Atlassian Customer Support

Read the full incident report →

Started Sep 09, 2025, 10:23 AM UTC· resolved Sep 15, 2025, 06:40 AM UTC

1. investigating Sep 09, 2025, 10:23 AM UTC

   We are investigating cases of degraded performance for Confluence and Jira Cloud customers using Microsoft Edge. We will provide more details as they emerge.

2. identified Sep 09, 2025, 11:40 AM UTC

   Important Update on Attachment Issues with Edge 140 and Atlassian Products We've identified an issue affecting images, media, and Whiteboards in Confluence and Jira for users who have upgraded to Microsoft Edge version 140.0.3485.54 with Strict tracking prevention enabled. These settings can block media (images and videos) content from loading, uploading, or opening. The issue is triggered by Edge's Strict tracking prevention incorrectly classifying Atlassian as advertising, impacting functionality. Recommended Workarounds: - Switch your tracking prevention settings from 'Strict' to the 'Balanced (Recommended)' mode in Edge. - Alternatively, add an 'Exception' for the URL you use to access Atlassian products. - Use a different browser, such as Chrome, Firefox, or Safari. This issue only affects Microsoft Edge. Other browsers are not affected by this issue. Thank you for your patience as we work through this issue. We'll provide updates as they become available.

3. identified Sep 10, 2025, 12:55 AM UTC

   Our team is aware that the incorrect classification of Atlassian sites as advertising has been resolved, however these changes will take some time to propagate out to users since we are waiting for Edge from Microsoft to incorporate the changes. We are continuing to monitor the situation and will provide further update when we are able to confirm that the issue is resolved.

4. identified Sep 10, 2025, 06:35 PM UTC

   We continue to work on resolving the Microsoft Edge 140 tracking prevention issue for Confluence, Jira Work Management, Jira Service Management, Jira, Jira Align, and Jira Product Discovery. We have identified the root cause and are working on solutions for each product. We will provide the next update within three hours.

5. monitoring Sep 10, 2025, 08:34 PM UTC

   We have identified the root cause of the Microsoft Edge 140 tracking prevention issue and have mitigated the problem and we continue monitoring closely. The issue has been mitigated however it will not be considered resolved until Microsoft issues an updated version of the Edge browser scheduled for September 18th. This will be the last update until the issue is resolved.

6. resolved Sep 15, 2025, 06:40 AM UTC

   An update has been released by Microsoft to resolve this issue for users of the Edge browser. To verify that you are running the required version of Edge, you can navigate to edge://components/ in the address bar, click the 'Check for update' button for the 'Trust Protections List', ensuring that you are on version 1.0.0.31 or higher to ensure you are running the version that contains the fixed release. All Edge browsers should otherwise receive this update within 10 hours without user intervention.

Read the full incident report →

Started Aug 04, 2025, 11:44 PM UTC· resolved Aug 05, 2025, 04:19 AM UTC

1. investigating Aug 04, 2025, 11:44 PM UTC

   Our team is aware of issues with users not currently receiving product invitation emails as expected. We are investigating with urgency and will provide an update as soon as possible. Please note that invitations within the product are still successful, only the email notifications are currently impacted.

2. resolved Aug 05, 2025, 04:19 AM UTC

   Between 2025-08-03T21:34 and 2025-08-05T03:43 UTC some users would not have received the emails for product invitations. The change that caused these emails to stop being sent has been rolled back. New invitation emails should now be sent correctly for all products. For users that were impacted by this issue, re-submitting their invitation will also re-send the email to them if required.

Read the full incident report →

Started Jul 30, 2025, 07:10 AM UTC· resolved Jul 30, 2025, 07:31 AM UTC

1. investigating Jul 30, 2025, 07:10 AM UTC

   We are investigating an issue causing a degraded experience when adding attachments or accessing existing media content.

2. resolved Jul 30, 2025, 07:31 AM UTC

   We have resolved the issue impacting adding/accessing media attachments across products. We will continue to monitor the situation.

Read the full incident report →

Started Jul 10, 2025, 08:32 AM UTC· resolved Jul 10, 2025, 08:55 AM UTC

1. monitoring Jul 10, 2025, 08:32 AM UTC

   We are investigating reports of intermittent errors for some Confluence, Jira Work Management, Jira Service Management, Jira, and Compass Cloud customers failing invocation, mostly scheduled triggers and smart links from 5:44 am UTC to 7:44 am UTC. We have put mitigations in place, and the errors have receded. We are monitoring the incident resolution. Customers will sometimes see errors in app functionality during this time and scheduled triggers might not work. We have replayed the scheduled triggers.

2. resolved Jul 10, 2025, 08:55 AM UTC

   Between 10th July 5:44 am UTC to 7:44 am UTC, we experienced intermittent failure in some app funstionality(smart links, scheduled triggers) for Confluence, Jira Work Management, Jira Service Management, Jira, and Compass. The issue has been resolved and the service is operating normally. All scheduled triggers has been replayed.

Read the full incident report →

Started Jun 25, 2025, 09:38 AM UTC· resolved Jun 25, 2025, 10:57 AM UTC

1. investigating Jun 25, 2025, 09:38 AM UTC

   We are investigating reports of errors loading Users and Groups pages in Atlassian Administration, and errors affecting user IDP syncing. We will provide more details once we identify the root cause.

2. identified Jun 25, 2025, 10:21 AM UTC

   We continue to work on resolving the user syncing functionality for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, and Guard. We have identified the root cause and expect recovery shortly.

3. monitoring Jun 25, 2025, 10:41 AM UTC

   We have identified the root cause of the issue and have mitigated the problem. We are now monitoring closely.

4. resolved Jun 25, 2025, 10:57 AM UTC

   Between 07:40 UTC and 10:31 UTC, we experienced issues affecting user syncing in Atassian Administration. This affected Confluence, Jira Work Management, Jira Service Management, Jira, Trello, and Guard. The issue has been resolved and the service is operating normally.

Read the full incident report →

Started Jun 24, 2025, 10:35 AM UTC· resolved Jun 25, 2025, 08:49 AM UTC

1. resolved Jun 24, 2025, 10:35 AM UTC

   We have resolved an issue that affected attachment loading during C2C and Sandbox data copy migrations from 19-06-2025 18:00 UTC to 24-06-2025 08:49 UTC. If you encountered this issue, please delete the affected projects from the destination site and re-run the migration. For ongoing migrations, allow them to complete and then follow the same steps. For Sandbox FDC migrations, complete them as usual and re-run if needed. We appreciate your patience and cooperation.

Read the full incident report →

Started Jun 10, 2025, 09:41 PM UTC· resolved Jun 10, 2025, 10:34 PM UTC

1. investigating Jun 10, 2025, 09:41 PM UTC

   We are investigating an issue impacting a subset of market place apps for some Confluence, Jira Service Management, and Jira, and Atlassian Developer Cloud customers in the Singapore region. We will provide more details within the next hour.

2. resolved Jun 10, 2025, 10:34 PM UTC

   Between 21:39 UTC on June 09, 2025 and 21:35 UTC on June 10, 2025, we experienced a forge invocation errors impacting a subset of market place apps for some Confluence, Jira Service Management, and Jira, and Atlassian Developer Cloud customers in the Singapore region. The issue has now been resolved and the service is operating normally. We are actively monitoring this capability.

Read the full incident report →

Started Jun 05, 2025, 08:33 AM UTC· resolved Jun 05, 2025, 11:02 AM UTC

1. investigating Jun 05, 2025, 08:33 AM UTC

   We are investigating an issue affecting the search functionality in Confluence for some users in Europe. Our team is working diligently to resolve the degradation and restore services promptly. We will keep you updated with further information.

2. investigating Jun 05, 2025, 09:32 AM UTC

   We are continuing to address an issue affecting the search functionality in Confluence for some users in Europe. Our team is actively working to mitigate the impact and restore services promptly. We will keep you updated with further information.

3. monitoring Jun 05, 2025, 10:41 AM UTC

   The issues affecting the search functionality in Confluence have been resolved, and services now operate normally for all affected customers. We will monitor it closely for the next 30 minutes to ensure stability.

4. resolved Jun 05, 2025, 11:02 AM UTC

   The issues affecting the search functionality in Confluence have been resolved, and services now operate normally for all affected customers.

Read the full incident report →

Started Jun 04, 2025, 05:17 PM UTC· resolved Jun 04, 2025, 08:59 PM UTC

1. investigating Jun 04, 2025, 05:17 PM UTC

   We were experiencing cases of degraded performance for outgoing emails from Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas and Compass Cloud customers. The system is recovering and mail is being processed normally as of 16:45 UTC. We will continue to monitor system performance and will provide more details within the next hour.

2. resolved Jun 04, 2025, 05:59 PM UTC

   Between 2025-06-04 14:11 UTC to 20:18 UTC, we experienced delays in delivering emails for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Compass. The issue has been resolved and the service is operating normally.

Read the full incident report →

Started May 27, 2025, 06:53 AM UTC· resolved May 27, 2025, 07:56 AM UTC

1. investigating May 27, 2025, 06:53 AM UTC

   We are aware of an issue where users are receiving a 403 error when attempting to reach Administration. Our team is looking into this issue with urgency and will provide an update as soon as possible.

2. monitoring May 27, 2025, 07:33 AM UTC

   The issues causing access problems to Administration have been resolved, and services are now functioning normally for all affected customers. We will monitor it closely for the next 30 minutes to ensure stability.

3. resolved May 27, 2025, 07:56 AM UTC

   The issue with the Administration accessibility has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started May 26, 2025, 05:19 AM UTC· resolved May 26, 2025, 06:27 AM UTC

1. investigating May 26, 2025, 05:19 AM UTC

   We are aware of issues relating to authentication resulting in 503 gateway error messages. Our team is investigating with urgency and will provide an update when available.

2. monitoring May 26, 2025, 05:57 AM UTC

   A fix for the issue causing authentication errors across multiple apps has been rolled out. We will provide further update when can confirm the issue has been fully resolved.

3. resolved May 26, 2025, 06:27 AM UTC

   Monitoring has indicated that users are no longer receiving the error messages caused by this issue and it should now be fully resolved.

Read the full incident report →

Started May 06, 2025, 01:11 AM UTC· resolved May 06, 2025, 05:55 AM UTC

1. identified May 06, 2025, 01:11 AM UTC

   We are investigating reports of intermittent errors for Atlassian Intelligence Confluence Cloud customers. We have identified the root cause and are preparing a hotfix

2. monitoring May 06, 2025, 04:38 AM UTC

   We have identified the root cause of the intermittent errors for Smart Answers and AI definitions in Confluence Cloud Atlassian Intelligence customers are progressively rollout out a fix to customers, with a fix expected to reach all customers over the next 2 hours. We are monitoring closely to confirm all errors have resolved.

3. resolved May 06, 2025, 05:55 AM UTC

   Between 2025/05/03 21:38 UTC to 2025/05/06 05:26 UTC, we experienced an outage in Smart Answers in search and AI definitions for all Confluence Cloud Atlassian Intelligence customers. Rovo experiences were not impacted. The issue has been resolved and the service is operating normally.

Read the full incident report →