Atlassian Outage History

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

1. identified Dec 15, 2025, 04:16 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, and Rovo. We'll share updates here as more information is available.

2. 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.

3. identified Dec 15, 2025, 04:48 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.

4. 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.

5. 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 15, 2025, 04:16 PM UTC· resolved Dec 15, 2025, 07:01 PM UTC

1. identified Dec 15, 2025, 04:16 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, and Rovo. We'll share updates here as more information is available.

2. 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.

3. 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.

4. 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.

5. 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 15, 2025, 04:16 PM UTC· resolved Dec 15, 2025, 07:01 PM UTC

1. identified Dec 15, 2025, 04:16 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, and Rovo. We'll share updates here as more information is available.

2. 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.

3. identified Dec 15, 2025, 04:48 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.

4. 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.

5. 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 12, 2025, 06:40 AM UTC· resolved Dec 12, 2025, 07:41 AM UTC

1. investigating Dec 12, 2025, 06:40 AM UTC

   We are actively investigating reports of a service disruption affecting Trello users. We'll share updates here as they become available or within the hour.

2. monitoring Dec 12, 2025, 07:28 AM UTC

   Our engineering team has implemented a fix, and services have now recovered. We will continue to closely monitor the situation.

3. resolved Dec 12, 2025, 07:41 AM UTC

   On December 12, 2025, from 05:51 UTC to 08:09 UTC, Trello users may have experienced service disruptions on the web page and mobile apps. The issue has now been resolved, and the service is operating normally for all affected customers.

4. postmortem Jan 06, 2026, 05:06 PM UTC

   ### Summary On December 12, 2025, between 05:31 UTC and 07:11 UTC, Trello customers experienced errors or slow loading times due to a dependency library upgrade that caused high resource usage. The incident was detected within 1 minute by the automated monitoring system and mitigated by rolling back the version of the dependency library which put Atlassian systems into a known good state. The total time to resolution was 1 hour and 41 minutes. ### **IMPACT** The issue caused service disruption for all Trello customers on December 12, 2025 between 05:31 UTC and 07:11 UTC. Users experienced degraded service between 05:31 UTC and 06:32 UTC, and most users were unable to load Trello between 06:32 UTC to 07:07 UTC. ### **ROOT CAUSE** The issue was caused by an upgrade to a dependency library. As a result, there was an increase in system memory consumption causing startups to take longer than expected. When the startup time exceeded the allowed threshold, the worker process was flagged as unresponsive and restarted as an automated recovery action. Because every worker on the instance failed to startup within the expected time, the instance entered a startup loop that required intervention. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. While we have several testing and preventive processes in place, we didn’t anticipate that the upgrade would consume more memory, which ultimately caused the startup failure loop and service disruption. We are prioritizing the following improvement actions designed to avoid this issue in the future: * Review our automated detection of unresponsive workers and adjust the detection thresholds during initialization. * Improve monitoring during workers startup and restarts due to unresponsiveness. * Enhance the stricter standard process for confirming memory/other data processing resource requirements for planned updates. 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

Read the full incident report →

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

1. 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.

2. 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 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 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 Dec 09, 2025, 05:30 AM UTC· resolved Dec 10, 2025, 05:30 AM UTC

1. resolved Dec 09, 2025, 08:14 AM UTC

   Between Dec 8 05:30 UTC and Dec 9 05:30 UTC, new Forge app versions were not auto-published to Atlassian Marketplace. We’ve implemented a mitigation and auto-publish is operating normally. Action required: If you deployed during this window, please manually publish those versions in Marketplace (or re-deploy your app with forge deploy). We’re sorry for the inconvenience.

Read the full incident report →

Started Dec 05, 2025, 01:16 PM UTC· resolved Dec 05, 2025, 03:32 PM UTC

1. monitoring Dec 05, 2025, 01:16 PM UTC

   We are currently investigating an issue where users encounter a Something Went Wrong error when creating a Linked Work Item that includes an attachment. Our engineering team is in the process of deploying the fix to production, and the ETA is 9hours from now. We apologize for the inconvenience and will provide updates as soon as more information becomes available. Thank you for your patience. Next Steps: The team will continue to monitor the situation until the hotfix is fully rolled out. Follow-up communications will be sent once the hot fix is fully rolled out.

2. resolved Dec 05, 2025, 03:32 PM UTC

   On December 5th, 2025, Jira Service Management users may have experienced an error when creating linked work items that included an attachment. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Dec 05, 2025, 01:16 PM UTC· resolved Dec 05, 2025, 03:32 PM UTC

1. monitoring Dec 05, 2025, 01:16 PM UTC

   We are currently investigating an issue where users encounter a Something Went Wrong error when creating a Linked Work Item that includes an attachment. Our engineering team is in the process of deploying the fix to production, and the ETA is 9hours from now. We apologize for the inconvenience and will provide updates as soon as more information becomes available. Thank you for your patience. Next Steps: The team will continue to monitor the situation until the hotfix is fully rolled out. Follow-up communications will be sent once the hot fix is fully rolled out.

2. resolved Dec 05, 2025, 03:32 PM UTC

   On December 5th, 2025, Jira Service Management users may have experienced an error when creating linked work items that included an attachment. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Dec 05, 2025, 08:08 AM UTC· resolved Dec 05, 2025, 12:09 PM UTC

1. investigating Dec 05, 2025, 08:08 AM UTC

   We are aware that access to created Ecohelp support tickets is not available for some of our customers. Our team is investigating this issue. Repeat creation of tickets is not required as the created tickets are visible to the Atlassian teams. We will provide next update in 60 minutes.

2. investigating Dec 05, 2025, 09:23 AM UTC

   Customers encounter a permission error when accessing tickets: No Access - You do not have permission to view this request. Ticket creation works and created tickets are visible to the Atlassian teams. The Atlassian team continues investigating. The root cause remains unclear. We will provide next update in 60 minutes.

3. investigating Dec 05, 2025, 09:56 AM UTC

   Customers encounter a permission error when accessing tickets: No Access - You do not have permission to view this request. Ticket creation works and created tickets are visible to the Atlassian teams. The Atlassian team continues investigating. The root cause remains unclear. We will provide next update in 60 minutes.

4. investigating Dec 05, 2025, 11:06 AM UTC

   Customers continue to encounter a permission error when accessing tickets: No Access - You do not have permission to view this request. Ticket creation works and created tickets are visible to the Atlassian teams. The Atlassian team is engaged and continues investigation. However, the root cause remains unclear. We will provide next update in 3 hours or sooner.

5. resolved Dec 05, 2025, 12:09 PM UTC

   The feature flag causing the issue has been reverted, fixing the problem. With that this incident is resolved.

Read the full incident report →

Started Dec 05, 2025, 08:08 AM UTC· resolved Dec 05, 2025, 12:09 PM UTC

1. investigating Dec 05, 2025, 08:08 AM UTC

   We are aware that access to created Ecohelp support tickets is not available for some of our customers. Our team is investigating this issue. Repeat creation of tickets is not required as the created tickets are visible to the Atlassian teams. We will provide next update in 60 minutes.

2. investigating Dec 05, 2025, 09:23 AM UTC

   Customers encounter a permission error when accessing tickets: No Access - You do not have permission to view this request. Ticket creation works and created tickets are visible to the Atlassian teams. The Atlassian team continues investigating. The root cause remains unclear. We will provide next update in 60 minutes.

3. investigating Dec 05, 2025, 09:56 AM UTC

   Customers encounter a permission error when accessing tickets: No Access - You do not have permission to view this request. Ticket creation works and created tickets are visible to the Atlassian teams. The Atlassian team continues investigating. The root cause remains unclear. We will provide next update in 60 minutes.

4. investigating Dec 05, 2025, 11:06 AM UTC

   Customers continue to encounter a permission error when accessing tickets: No Access - You do not have permission to view this request. Ticket creation works and created tickets are visible to the Atlassian teams. The Atlassian team is engaged and continues investigation. However, the root cause remains unclear. We will provide next update in 3 hours or sooner.

5. resolved Dec 05, 2025, 12:09 PM UTC

   The feature flag causing the issue has been reverted, fixing the problem. With that this incident is resolved.

Read the full incident report →

Started Dec 01, 2025, 08:24 PM UTC· resolved Dec 05, 2025, 02:20 AM UTC

1. identified Dec 01, 2025, 08:24 PM UTC

   We are investigating reports of intermittent errors for ALL Talent Cloud customers. The Data Ingestion item is failing, causing sync issues. We will provide another update within the next 2 hours.

2. identified Dec 01, 2025, 10:16 PM UTC

   Impact Customers using Jira Service Management and Talent have encountered an issue where New Hire Employee data is unavailable in Talent. This situation blocks the creation of onboarding plans for new hires. At present, all Talent customers are affected by this synchronization issue, which has persisted for more than 18 hours. Current Status and Next Steps The engineering team continues to work on the fix. Once we have more details to share about their findings and fixes, a new Update will be posted in a least 2 hours from now.

3. identified Dec 02, 2025, 12:17 AM UTC

   Our team continues to actively investigate the cause of this issue. We are now deploying additional monitoring to help us understand the root cause of this issue in more detail and will provide further update within 4 hours or as soon as a resolution becomes available.

4. identified Dec 02, 2025, 01:59 AM UTC

   Our team has now identified a potential root cause for this incident and is actively working on a hot-fix release to resolve the issue. We will provide further update when the expected fix is available, or within 4 hours, whichever is sooner.

5. identified Dec 02, 2025, 06:09 AM UTC

   A fix has now been released for this issue, and our internal monitoring is showing that services are now processing events as expected. A historical backlog of events exists from the start of the incident, and we are now processing those events. We will provide further update within 4 hours, or when processing is completed, whichever is sooner.

6. identified Dec 02, 2025, 09:57 AM UTC

   We released a fix, and internal monitoring shows services now process current events as expected. Reprocessing the historical backlog of events from the incident start is ongoing. We estimate it will take about 7.5 hours for the APSE region and 10 hours for the EU Central region. For the PROD-EAST region, we do not yet have an ETA since reprocessing has not started, but the team estimates it will be brief due to fewer events. We will provide an update within 10 hours or when reprocessing completes, whichever is sooner.

7. identified Dec 02, 2025, 08:04 PM UTC

   Impact Customers using Jira Service Management and the Talent product experienced interruptions due to missing or delayed data updates. This issue impacted the availability of new hire employee data, preventing the creation of onboarding plans. The disruption persisted for more than 18 hours, affecting all Talent customers. Current Status Normal data processing remains restored, following initial hotfix implementation. Reprocessing the backlog of events continues at an accelerated pace. The Asia-Pacific Southeast (APSE) region has been reprocessed as of 1240 UTC and is complete. The EU Central region has also finished as of 1740 UTC, with no resync required. The last remaining affected region is US East, which is expected to reprocess within the next 3-4 hours. Next Steps No further action is required at this time for the APSE and EU Central regions. Atlassian Engineering is actively monitoring reprocessing job status on US East. The next update will occur at 2300 UTC.

8. monitoring Dec 03, 2025, 01:08 AM UTC

   Data syncing within the impacted features should now be fully operational. Some final historical tasks are still replaying, and we will update again once these tasks have been completed and the issue is fully resolved.

9. resolved Dec 05, 2025, 02:20 AM UTC

   All historical tasks have now been replayed and completed, so this incident will be closed. For any customers that are still experiencing issues they feel may be related to this incident, please reach out to Atlassian Support for additional assistance.

Read the full incident report →

Started Dec 01, 2025, 05:25 PM UTC· resolved Dec 01, 2025, 06:26 PM UTC

1. investigating Dec 01, 2025, 05:25 PM UTC

   We are investigating an incident affecting Jira Work Management, Jira, and Jira Service Management. We will provide updates via Statuspage shortly. The ability to view issues and boards is experiencing degraded performance for some users. Customers may notice a slowdown in accessing these functionalities.

2. investigating Dec 01, 2025, 05:26 PM UTC

   We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

3. investigating Dec 01, 2025, 05:30 PM UTC

   We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

4. investigating Dec 01, 2025, 06:26 PM UTC

   We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

5. resolved Dec 01, 2025, 06:26 PM UTC

   Impact Jira Software users experienced degraded performance affecting their ability to view issues and boards. Users may have encountered an error or slowdown during this time. Current Status The situation is currently mitigated due to actions taken on the affected systems, leading to a stabilization of services. Next Steps The team is actively monitoring the systems.

Read the full incident report →

Started Dec 01, 2025, 05:25 PM UTC· resolved Dec 01, 2025, 06:26 PM UTC

1. investigating Dec 01, 2025, 05:25 PM UTC

   We are investigating an incident affecting Jira Work Management, Jira, and Jira Service Management. We will provide updates via Statuspage shortly. The ability to view issues and boards is experiencing degraded performance for some users. Customers may notice a slowdown in accessing these functionalities.

2. investigating Dec 01, 2025, 05:26 PM UTC

   We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

3. investigating Dec 01, 2025, 05:30 PM UTC

   We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

4. investigating Dec 01, 2025, 06:26 PM UTC

   We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

5. resolved Dec 01, 2025, 06:26 PM UTC

   Impact Jira Software users experienced degraded performance affecting their ability to view issues and boards. Users may have encountered an error or slowdown during this time. Current Status The situation is currently mitigated due to actions taken on the affected systems, leading to a stabilization of services. Next Steps The team is actively monitoring the systems.

Read the full incident report →

Started Dec 01, 2025, 05:25 PM UTC· resolved Dec 01, 2025, 06:26 PM UTC

1. investigating Dec 01, 2025, 05:25 PM UTC

   We are investigating an incident affecting Jira Work Management, Jira, and Jira Service Management. We will provide updates via Statuspage shortly. The ability to view issues and boards is experiencing degraded performance for some users. Customers may notice a slowdown in accessing these functionalities.

2. investigating Dec 01, 2025, 05:26 PM UTC

   We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

3. investigating Dec 01, 2025, 05:30 PM UTC

   We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

4. investigating Dec 01, 2025, 06:26 PM UTC

   We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

5. resolved Dec 01, 2025, 06:26 PM UTC

   Impact Jira Software users experienced degraded performance affecting their ability to view issues and boards. Users may have encountered an error or slowdown during this time. Current Status The situation is currently mitigated due to actions taken on the affected systems, leading to a stabilization of services. Next Steps The team is actively monitoring the systems.

Read the full incident report →

Started Dec 01, 2025, 05:24 PM UTC· resolved Dec 01, 2025, 06:26 PM UTC

1. investigating Dec 01, 2025, 05:24 PM UTC

   We are investigating an incident affecting Jira Work Management, Jira, and Jira Service Management. We will provide updates via Statuspage shortly. The ability to view issues and boards is experiencing degraded performance for some users. Customers may notice a slowdown in accessing these functionalities.

2. investigating Dec 01, 2025, 05:26 PM UTC

   We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

3. investigating Dec 01, 2025, 05:30 PM UTC

   We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

4. investigating Dec 01, 2025, 06:26 PM UTC

   We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

5. resolved Dec 01, 2025, 06:26 PM UTC

   Impact Jira Software users experienced degraded performance affecting their ability to view issues and boards. Users may have encountered an error or slowdown during this time. Current Status The situation is currently mitigated due to actions taken on the affected systems, leading to a stabilization of services. Next Steps The team is actively monitoring the systems.

Read the full incident report →

Started Dec 01, 2025, 05:24 PM UTC· resolved Dec 01, 2025, 06:26 PM UTC

1. investigating Dec 01, 2025, 05:24 PM UTC

   We are investigating an incident affecting Jira Work Management, Jira, and Jira Service Management. We will provide updates via Statuspage shortly. The ability to view issues and boards is experiencing degraded performance for some users. Customers may notice a slowdown in accessing these functionalities.

2. investigating Dec 01, 2025, 05:26 PM UTC

   We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

3. investigating Dec 01, 2025, 05:30 PM UTC

   We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

4. investigating Dec 01, 2025, 06:26 PM UTC

   We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

5. resolved Dec 01, 2025, 06:26 PM UTC

   Impact Jira Software users experienced degraded performance affecting their ability to view issues and boards. Users may have encountered an error or slowdown during this time. Current Status The situation is currently mitigated due to actions taken on the affected systems, leading to a stabilization of services. Next Steps The team is actively monitoring the systems.

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:12 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 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 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:24 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 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:24 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 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:24 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 20, 2025, 09:48 PM UTC· resolved Nov 20, 2025, 09:48 PM UTC

1. identified Nov 20, 2025, 09:48 PM UTC

   The incident involves Ecosystem and Jira products, specifically affecting the Forge Jira Custom Fields. Customers may experience a loss of values upon selection on the Issue Create Screen. The root cause is identified and we are working on deploying a fix.

2. resolved Nov 20, 2025, 09:48 PM UTC

   On 20 November 2025, affected Jira users may have experienced some service disruption for Forge custom fields on Jira issue create. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Nov 20, 2025, 08:31 PM UTC· resolved Nov 20, 2025, 10:00 PM UTC

1. identified Nov 20, 2025, 08:31 PM UTC

   We understand that Users are experiencing issues with Forge Custom Fields not retaining selected values on Issue Create Screen. We have identified the root cause and actively working on deploying a fix. Issue start time: 2025-11-20T07:00

2. resolved Nov 20, 2025, 10:00 PM UTC

   On 20 November 2025, affected Jira users may have experienced some service disruption for Forge custom fields on Jira issue create. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →