Atlassian Developer Outage History

Started Apr 02, 2026, 08:46 PM UTC· resolved Apr 02, 2026, 10:36 PM UTC

1. investigating Apr 02, 2026, 08:46 PM UTC

   We are actively investigating reports of a partial service disruption affecting Forge Remote applications integrating with JIRA. We will share updates here as more information is available.

2. resolved Apr 02, 2026, 10:36 PM UTC

   On April 2, 2026, affected users may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Mar 24, 2026, 07:59 AM UTC· resolved Mar 24, 2026, 08:44 AM UTC

1. identified Mar 24, 2026, 07:59 AM UTC

   We are receiving reports of degraded performance on the Connect APIs impacting Connect apps. We have identified the cause and are rolling out a fix now. We are monitoring the deployment and will provide another update within two hours, or sooner

2. resolved Mar 24, 2026, 08:44 AM UTC

   On March 24, 2026, between 04:14 AM UTC and 08:40 AM UTC, Connect Apps using connect API's experienced performance degradation. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Mar 17, 2026, 10:05 AM UTC· resolved Mar 17, 2026, 11:37 AM UTC

1. investigating Mar 17, 2026, 10:05 AM UTC

   We are actively investigating reports of performance degradation affecting Forge apps and Developer console will share updates here as more information becomes available.

2. investigating Mar 17, 2026, 10:34 AM UTC

   We are continuing to investigate this issue.

3. investigating Mar 17, 2026, 10:59 AM UTC

   We are investigating an incident impacting Forge app management and related developer tooling. Customers may experience errors when attempting to: -Install, upgrade, or deploy Forge apps -Use Forge app tunnelling (particularly newly created tunnels and tunnels older than 30 minutes) -Access or manage apps via the Atlassian Developer Console In addition, some underlying app platform capabilities used by Forge and related services are affected, including: -Certain app data residency operations -Rovo MCP consent flows and other app management operations that rely on the app platform At this time, existing Forge apps continue to run, and app invocations are not impacted. Our engineering teams are actively investigating the issue and working to restore normal operation. We will provide the next update in 60 mins or sooner if we have significant progress to share.

4. resolved Mar 17, 2026, 11:37 AM UTC

   On March 17th, 2026, between 9:05 AM UTC and 11:10 AM UTC, Forge app management and related developer tooling experienced some service disruption. The issue has now been resolved, and the service is operating normally for affected customers.

Read the full incident report →

Started Mar 12, 2026, 11:42 AM UTC· resolved Mar 13, 2026, 12:26 AM UTC

1. investigating Mar 12, 2026, 11:42 AM UTC

   Confluence Cloud users may experience errors when accessing certain Marketplace macros. Affected customers are seeing the message Error rendering macro 'static-macro': Page loading failed. Our team is actively investigating this issue. We will provide another update within 2 hours, or sooner.

2. investigating Mar 12, 2026, 01:38 PM UTC

   Confluence Cloud users may experience errors when accessing certain Marketplace macros. Affected customers are seeing the message Error rendering macro 'static-macro': Page loading failed. Our team is actively investigating this issue. We will provide another update within 2 hours, or sooner.

3. identified Mar 12, 2026, 01:38 PM UTC

   Our team has identified the cause of this issue, and a fix is currently being deployed. We are monitoring the deployment, and we will provide another update within 2 hours, or sooner if needed.

4. resolved Mar 13, 2026, 12:26 AM UTC

   On March 12, 2026, affected Confluence Cloud users may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Mar 02, 2026, 04:15 PM UTC· resolved Mar 04, 2026, 03:04 AM UTC

1. monitoring Mar 02, 2026, 04:15 PM UTC

   Since Feb 27, 2026 some Marketplace Partners may see incorrect install counts in their Marketplace Partner Portal and listing for their apps. The Marketplace team has identified the bug and is working to correct the same. Please note, the actual customer installs for these apps remain unaffected. As next Steps, the Marketplace team is working on a fix and expects to restore accurate install counts by Mar 3, 2026, EOD.

2. monitoring Mar 03, 2026, 05:06 PM UTC

   We are providing an update regarding the install count discrepancy that some partners may have observed for some apps since Feb 27, 2026. - The install counts displayed on app listings are now accurate for the impacted apps. - The Active Installations tab in the Marketplace Partner Portal may still reflect incorrect counts for some apps; this will be corrected following tonight's scheduled update at 12:00 AM UTC on Mar 4, 2026. - Please note that actual customer installs were not impacted; only the reported counts displayed in the Partner Portal and on app listings were affected for some apps. We will share another update once the Partner Portal Active Installations tab has been fully corrected and validated. Thank you for your patience and understanding.

3. resolved Mar 04, 2026, 03:04 AM UTC

   We are providing a further update regarding the install count discrepancy that some partners may have observed for some apps since Feb 27, 2026. - The Active Installations tab in the Marketplace Partner Portal is now showing accurate install counts for impacted apps from Mar 3, 2026 onward. - The install counts displayed on app listings remain accurate for impacted apps. - Please note that data from Mar 3, 2026 onward will remain accurate going forward. - You may notice a temporary dip in install counts for Mar 2, 2026. We are backfilling the data, and counts for that date will be restored once complete. - Actual customer installs were not impacted; only the reported counts displayed in the Partner Portal and on app listings were affected for some apps, and this is now fully functional. Thank you for your patience and understanding.

Read the full incident report →

Started Feb 16, 2026, 11:24 AM UTC· resolved Feb 19, 2026, 05:12 PM UTC

1. investigating Feb 16, 2026, 11:24 AM UTC

   Some Forge app billing admins may have received subscription cancellation emails, but we want to assure you that there is no disruption or impact to the functioning of your Forge apps, your apps will continue to operate as normal. Our team is actively working to reactivate any affected subscriptions. To help prevent any future interruptions, we kindly request that admins ensure a valid billing payment method is added before the next billing cycle. We apologise for any confusion and appreciate your understanding.

2. identified Feb 16, 2026, 11:27 AM UTC

   Some Forge app billing admins may have received subscription cancellation emails, but we want to assure you that there is no disruption or impact to the functioning of your Forge apps, your apps will continue to operate as normal. Our team is actively working to reactivate any affected subscriptions. To help prevent any future interruptions, we kindly request that admins ensure a valid billing payment method is added before the next billing cycle. We apologise for any confusion and appreciate your understanding.

3. resolved Feb 19, 2026, 05:12 PM UTC

   We have now reactivated all subscriptions that were previously cancelled. Impacted users may have received email notifications confirming this change. There has been no impact to the functioning of the app, it should continue to work as expected. To help prevent any future interruptions, we kindly request that billing admins ensure a valid billing payment method is added before the next billing cycle. We apologise for any confusion and appreciate your understanding.

Read the full incident report →

Started Feb 13, 2026, 07:41 AM UTC· resolved Feb 19, 2026, 08:04 AM UTC

1. identified Feb 13, 2026, 07:41 AM UTC

   Our teams identified two fix paths: a quick fix and a longer, time-consuming fix. We will test the quick fix over the weekend and, if no issues arise, implement it on Monday. We will provide the next update on Monday, Feb 16, 2026.

2. identified Feb 16, 2026, 12:24 AM UTC

   Impact Ecosystem, Jira, and Jira Service Management customers might experience API call failures when using OAuth 2.0 apps, receiving 'The app is not installed on this instance' errors. The incident is attributed to OAuth scope mismatches between different internal services. Approximately 17,168 clients could be potentially affected, involving several cloud instances. The incident has resulted in 2LO permissions being incorrectly enabled, causing potential access issues. Some customers may notice unauthorized system users in their directories, which currently pose no identified security risk. Current Status The short term fix involving Workspace ARI's will be rolled out cautiously over today and should resolve some highly impacted installations. Full restoration via backfill scripts is being developed, though this will at least take the remainder of the week to cautiously roll out to production. Next Steps The backfill process for a permanent data correction is set to begin, with rigorous monitoring planned to observe system behavior. New communication updates are scheduled to occur within the next 12 hours, or sooner if significant developments arise. If you believe that you are impacted by this incident, and need assistance, then we recommend raising a support ticket.

3. identified Feb 16, 2026, 05:30 AM UTC

   Our teams have identified customers that are actively experiencing issues relating to loss of access to their apps, and we are progressively rolling out a fix to these customers with urgency. We will provide further update within 24 hours or sooner if available.

4. identified Feb 17, 2026, 05:40 AM UTC

   Our team is continuing to work on correcting the impact from this issue. A tested and validated process is now running to restore affected apps and our team is closely monitoring traffic to help to rule out any issues. Please raise a support request if you require further assistance. An update will be provided within 72 hours with our status on the backfill operation and estimated time to completion.

5. monitoring Feb 19, 2026, 12:51 AM UTC

   Our team has resolved the permission errors relating to this incident across all Apps, and we will continue to monitor for any unexpected issues. For customers still experiencing errors, this may indicate a legitimate permission configuration issue on your side and should be investigated as usual. We'll provide another update within 24 hours on the results of our monitoring.

6. monitoring Feb 19, 2026, 08:04 AM UTC

   This issue is resolved. In our monitoring no other unexpected issues were seen. For customers still experiencing errors, this may indicate a legitimate permission configuration issue on your side and should be investigated as usual.

7. resolved Feb 19, 2026, 08:04 AM UTC

   This issue is resolved. In our monitoring no other unexpected issues were seen. For customers still experiencing errors, this may indicate a legitimate permission configuration issue on your side and should be investigated as usual.

Read the full incident report →

Started Feb 06, 2026, 09:37 AM UTC· resolved Feb 06, 2026, 11:32 AM UTC

1. investigating Feb 06, 2026, 09:37 AM UTC

   Impact We are currently experiencing an issue affecting the Forge platform, specifically impacting scheduled triggers. Users may notice that these triggers are not executing as expected. This issue was initially observed around 2 AM UTC. Current Status Our engineering team is actively investigating the issue and working toward restoring full service. The team is focused on identifying the root cause and implementing a solution to resolve the incident. Next Steps We will provide a status update in 60 minutes. The restoration of service is our priority, and the team will continue to monitor and address the situation as developments occur.

2. identified Feb 06, 2026, 10:39 AM UTC

   Impact We are currently experiencing an issue affecting the Forge platform, specifically impacting scheduled triggers. Users may notice that these triggers are not executing as expected. This issue was initially observed around 2 AM UTC. Current Status Our engineering team is actively investigating the issue. The issue is suspected to be related to a recent change that was deployed. The team is currently rolling back the changes. Next Steps We will provide a status update in 60 minutes. The restoration of service is our priority, and the team will continue to monitor and address the situation as developments occur.

3. resolved Feb 06, 2026, 11:32 AM UTC

   Impact We are currently experiencing an issue affecting the Forge platform, specifically related to scheduled triggers. Users may encounter instances where these triggers are not executing as anticipated, disrupting the normal operation of their Forge apps. This behavior began approximately at 2 AM UTC. Current Status Our engineering team identified the root cause and performed a rollback deployment to resolve the issue.

Read the full incident report →

Started Feb 03, 2026, 10:19 AM UTC· resolved Feb 03, 2026, 10:50 AM UTC

1. investigating Feb 03, 2026, 10:19 AM UTC

   Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

2. investigating Feb 03, 2026, 10:24 AM UTC

   Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

3. resolved Feb 03, 2026, 10:50 AM UTC

   Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.

Read the full incident report →

Started Jan 28, 2026, 05:34 PM UTC· resolved Jan 28, 2026, 07:20 PM UTC

1. investigating Jan 28, 2026, 05:34 PM UTC

   We are actively investigating reports of a partial service disruption affecting Forge. We'll share updates here as more information is available.

2. investigating Jan 28, 2026, 06:33 PM UTC

   We continue to investigate the issue, and will share updates here as more information becomes available.

3. monitoring Jan 28, 2026, 07:02 PM UTC

   The issue has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor closely to confirm stability.

4. resolved Jan 28, 2026, 07:20 PM UTC

   On January 28, 2026, some customers may have experienced Forge function invocation availability disruption. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Dec 16, 2025, 05:47 AM UTC· resolved Dec 17, 2025, 06:07 AM UTC

1. identified Dec 16, 2025, 05:47 AM UTC

   We have identified an issue with the Forge Developer Console, which is not displaying data on the Usage and Charges page. We are actively working to resolve this issue and will provide more details within the next hour.

2. identified Dec 16, 2025, 05:47 AM UTC

   We have identified an issue with the Forge Developer Console not displaying data on the Usage and Charges page. We are actively working to resolve this issue and will provide more details within the next hour.

3. monitoring Dec 16, 2025, 04:14 PM UTC

   The issue affecting the display of data on the Usage and Charges page in the Forge Developer Console has been largely resolved. All charge elements, except for Forge Compute, are now displaying accurate values. We are actively working to resolve the remaining issue with Forge Compute. We will provide another update once this final issue has been fully mitigated.

4. identified Dec 16, 2025, 04:14 PM UTC

   The issue affecting the display of data on the Usage and Charges page in the Forge Developer Console has been largely resolved. All charge elements, except for Forge Compute, are now displaying accurate values. We are actively working to resolve the remaining issue with Forge Compute. We will provide another update once this final issue has been fully mitigated.

5. resolved Dec 17, 2025, 06:07 AM UTC

   The issue is completely resolved and Developer Console is now displaying all the usage metrics correctly. 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, 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 Nov 10, 2025, 10:41 AM UTC· resolved Nov 10, 2025, 02:03 PM UTC

1. investigating Nov 10, 2025, 10:41 AM UTC

   Impact Customers may experience degraded performance navigating logs, as there is an issue with log ingestion that could manifest as delays or incomplete data being visible. Current Status Support teams are actively engaged in diagnosing the situation and planning the steps necessary for service restoration. Next Steps The incident management team is focused on identifying the root cause of the performance degradation and implementing measures to restore normal operations. The next update will be communicated in 60 minutes or when an important milestone is reached.

2. resolved Nov 10, 2025, 02:03 PM UTC

   Impact Customers experienced degraded performance in log ingestion services affecting the Ecosystem, particularly the Forge platform. Due to this issue, accessing logs ingested from the morning of the incident (starting 06:00 UTC) was impacted, leading to delays or incomplete data visibility through the Dev Console and related channels. Current Status This incident has been resolved, and Forge Logs are back in operational mode.

Read the full incident report →

Started Oct 27, 2025, 12:04 PM UTC· resolved Oct 28, 2025, 01:42 PM UTC

1. identified Oct 27, 2025, 12:04 PM UTC

   High-Level Impact: Following three vendor reporting flows are experiencing data discrepancies for the period between 12:00 AM 25th October 2025 and 2:00 PM 27th October 2025 IST: Aggregated Sales Reporting Transaction Reporting Export Transaction APIs All other reporting flows and data outside this window remain accurate and unaffected. Details about the Impact: Between 12:00 AM 25th October 2025 and 2:00 PM 27th October 2025 IST, data in the above three reports may be incomplete or inaccurate. Timeline: 2025-10-25 00:00 IST: Impact started 2025-10-27 14:00 IST: Impact ended (data discrepancies limited to this window) 2025-10-27 11:00 IST: Issue detected and remediation initiated Expected Resolution Timeframe: Our team is actively working to resolve the issue. We expect to fix the discrepancies and replay the affected data within approximately 12 hours from now. Mitigation: The engineering team is addressing the root cause and will replay the affected data for the impacted period. No action is required from your side at this time. Workaround: Currently, there is no workaround available. We recommend holding off on any critical reporting or reconciliation activities for the affected period in these three reports until the issue is resolved. Next Update: We will provide another update as soon as we have more information.

2. identified Oct 28, 2025, 04:22 AM UTC

   We are in the final stages of resolving the data discrepancy that affected reports from 25th October 2025 through 2:00 PM IST on 27th October 2025. The data replay for October 25th and 26th is complete, and the final replay for October 27th is expected to conclude in approximately 7 hours. Once the replay concludes, we will begin a thorough validation of the Aggregated Sales Reporting, Transaction Reporting, and Export Transaction APIs to confirm the data is fully restored for the entire impact window.

3. monitoring Oct 28, 2025, 01:04 PM UTC

   Data replay for the impacted window (25 Oct 2025 00:00 IST – 27 Oct 2025 14:00 IST) is complete. We are performing final validation of Aggregated Sales Reporting, Transaction Reporting, and Export Transaction APIs to confirm full restoration for this period. No action is required from vendors at this time. We will post the next update after validation; if successful, we will close this incident.

4. resolved Oct 28, 2025, 01:42 PM UTC

   Validation is complete. All tables backing Aggregated Sales Reporting, Transaction Reporting, and Export Transaction APIs have been fully repopulated. Data for the impacted window (25 Oct 2025 00:00 IST – 27 Oct 2025 14:00 IST) has been restored and verified. No action is required from vendors. We are closing this incident.

Read the full incident report →

Started Oct 22, 2025, 12:15 PM UTC· resolved Oct 22, 2025, 10:09 PM UTC

1. investigating Oct 22, 2025, 12:15 PM UTC

   We are aware that Confluence Webhooks are not being delivered and our team is actively investigating the same. We shall provide next update in one hour, if not sooner.

2. investigating Oct 22, 2025, 01:14 PM UTC

   Our team continues to investigate this issue. We will provide the next update within one hour or sooner.

3. investigating Oct 22, 2025, 02:20 PM UTC

   We are continuing our investigation. We will provide the next update within two hours or sooner.

4. investigating Oct 22, 2025, 04:16 PM UTC

   We are continuing to investigate the issue causing Confluence Webhooks to not be delivered. While we have not yet identified the root cause, our team is making progress. We will provide another update at 18:20 UTC, or sooner as new information becomes available.

5. identified Oct 22, 2025, 07:09 PM UTC

   We have identified the issue causing Confluence Webhooks to not be delivered and are in the process of applying mitigations. We will provide another update at 20:00 UTC, or sooner if the mitigation is applied or new information becomes available.

6. identified Oct 22, 2025, 08:07 PM UTC

   We have identified the issue causing Confluence Webhooks to not be delivered. We are currently testing a fix internally. We will provide another update at 22:00 UTC, or sooner if the fix is applied or new information becomes available.

7. resolved Oct 22, 2025, 10:09 PM UTC

   Between 01:00 and 20:47 UTC on October 22, 2025, App Developers experienced an issue where Confluence webhooks were not being delivered. We have deployed a fix to mitigate the problem, and the service is now operating normally. This outage did not affect Forge events. However, it did impact: 1) All Connect Apps 2) Forge apps that use webhooks via connectModules Please note: Atlassian cannot replay or resend the missed webhook events. As a result, these events are permanently lost. Recommended Action: To recover, we recommend that all affected apps use their resynchronization (resync) mechanisms to fetch the latest data directly from Confluence. This will help ensure your app’s data is up to date and that any information missed during the outage is restored. Once we complete our internal incident review process, we will publish a more detailed postmortem of what went wrong, along with steps we're taking to prevent this from happening again in the future.

8. postmortem Nov 08, 2025, 04:22 AM UTC

   ### Summary On October 22, 2025, Confluence Cloud webhook events were not delivered to Connect apps and Forge apps that use webhooks via `connectModules`. This outage began after a backend deployment introduced a code change that prevented Confluence from recognizing registered webhook listeners. As a result, no webhook events were generated for approximately 20 hours, impacting apps that depend on webhooks. The issue was resolved by rolling back to a previous stable deployment. We’re taking steps to improve detection and rollback processes. ### **IMPACT** Between 01:12 UTC and 21:46 UTC on October 22, 2025, Confluence was unable to send out webhook events. As a result, none of the apps that rely on these events received them during this time. This includes Connect apps and Forge apps that use webhooks through `connectModules`. Customers may have noticed outdated content appearing in their Marketplace apps, or new content not syncing. ### **ROOT CAUSE** The issue was caused by a change to Confluence backend systems. As a result, no webhook events were delivered to Connect and Forge apps that use webhooks via `connectModules`. This occurred because a Java class was loaded by 2 different classloaders, causing Confluence to fail to find registered webhook listeners and thus not emit events. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** Webhooks are a critical functionality for many apps. On this occasion, our system did not generate any errors because it was inadvertently using an incorrect version of a Java class, which was loaded by a different ClassLoader. As a result, the issue occurred silently and couldn’t be detected via existing automated error monitoring. We are prioritizing the following improvement actions to help prevent this issue from reoccurring: * Additional integration tests to identify problems before merging code to our main branch. * Additional detectors and alerts to identify when webhook event volume drops below a certain threshold. * Exploring resync / lost event recovery mechanism without overloading Atlassian infrastructure * We acknowledge that the availability of Connect apps is important for our customers and ecosystem partners, and we will endeavour to provide support for these apps in line with our public roadmap for Connect end of life. You can read our announcement here: [Announcing Connect End of Support: Timeline and Next Steps - Work Life by Atlassian](https://www.atlassian.com/blog/developer/announcing-connect-end-of-support-timeline-and-next-steps) While this incident primarily impacted Connect, we would like to note that Forge currently includes additional internal capabilities, such as retry [Atlassian app events](https://developer.atlassian.com/platform/forge/events-reference/product_events/#retry-atlassian-app-events) and internal DLQ, that could assist with recovery in these types of incidents.. We highly encourage partners to migrate to Forge to utilize the latest webhook infrastructure. We apologize to customers and ecosystem partners 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 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:06 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:21 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, 04:36 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.

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

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

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

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

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

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

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

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

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

25. postmortem Oct 24, 2025, 05:45 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 12, 2025, 03:25 PM UTC· resolved Oct 12, 2025, 07:25 PM UTC

1. investigating Oct 12, 2025, 03:25 PM UTC

   Impact The issue is affecting Forge Egress within the Ecosystem, leading to intermittent failures in authenticated egress calls. This has impacted functionalities such as Jira Incoming Mail, causing delays in fetching emails from providers like Gmail and Microsoft, and consequently affecting work item creation. Additionally, Forge Compass apps are currently failing to send data to Compass. Current Status We have identified the root cause and are in the process of deploying a fix. Next Steps Post-deployment, we will continue to closely monitor the fix to ensure stability. The next update will be provided in 60 minutes.

2. investigating Oct 12, 2025, 05:19 PM UTC

   We are deploying a fix that will alleviate some of the issues. We are still investigating the root cause behind the intermittent failures. Our team continues to closely monitor the errors and explore additional mitigations to ensure stability.

3. monitoring Oct 12, 2025, 06:33 PM UTC

   We have identified the root cause of the intermittent errors and have mitigated the problem by putting in a temporary measure. We are now monitoring closely.

4. resolved Oct 12, 2025, 07:25 PM UTC

   Between 06:58 12 Oct UTC to 18:30 12 Oct UTC, we experienced calls from a some forge apps to external services (outside of Atlassian) intermittently fail. The issue has been resolved and the service is operating normally.

Read the full incident report →

Started Oct 03, 2025, 03:43 AM UTC· resolved Oct 03, 2025, 06:24 AM UTC

1. identified Oct 03, 2025, 03:43 AM UTC

   We are currently experiencing an issue where some Forge app users are seeing unexpected Allow access OAuth consent prompts when first using the app UI. There is no security impact; affected users can proceed by approving the prompt and continue using the app normally. This primarily affects apps that use auto‑consent with UI, including newly installed apps and upgraded apps where permissions changed and the user does not already have a consent grant. Our engineering team has identified the cause and is deploying a fix. We will provide our next update by 06:00 UTC. We apologize for the inconvenience and appreciate your patience.

2. monitoring Oct 03, 2025, 06:04 AM UTC

   We identified the root cause of the unexpected Allow access prompts in Forge app UI and have mitigated the problem. We are now monitoring closely.

3. resolved Oct 03, 2025, 06:24 AM UTC

   Between 29 Sep 2025 07:10 UTC and 03 Oct 2025 06:00 UTC, some customers experienced unexpected Allow access OAuth consent prompts when using the Forge app UI. The issue has been resolved, and the service is operating normally.

Read the full incident report →

Started Sep 29, 2025, 03:32 PM UTC· resolved Sep 29, 2025, 05:07 PM UTC

1. identified Sep 29, 2025, 03:32 PM UTC

   We are investigating cases of degraded performance of log delivery for some app developers. We are working on implementing a fix. We will provide more details within the next hour.

2. resolved Sep 29, 2025, 05:07 PM UTC

   Between 08:30 AM UTC to 16:30 UTC on September 29, 2025, some developers experienced delays of log delivery for the Dev Console. The root cause was an unexpected spike in volume that required updates to autoscaling configurations to address. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The conditions that cause the bug have been addressed and we’re actively working on a permanent fix. The issue has been resolved and the service is processing logs normally. We are currently processing the delayed logs and anticipate completion by 17:00 UTC today, September 29, 2025.

Read the full incident report →

Started Sep 26, 2025, 10:09 AM UTC· resolved Sep 26, 2025, 10:45 AM UTC

1. identified Sep 26, 2025, 10:09 AM UTC

   We are currently experiencing technical difficulties with our internal data pipelines, resulting in 5XX errors for Marketplace Reporting APIs. Consequently, Marketplace partners are unable to access reporting APIs, and users of the Partner Portal may experience degraded performance. Our engineering team is actively investigating the issue and working diligently to resolve it as quickly as possible. We will provide regular updates as more information becomes available. We apologize for the inconvenience and appreciate your patience and understanding

2. identified Sep 26, 2025, 10:10 AM UTC

   We are continuing to work on a fix for this issue.

3. monitoring Sep 26, 2025, 10:28 AM UTC

   A fix has been implemented and monitoring the fix.

4. resolved Sep 26, 2025, 10:45 AM UTC

   Issues affecting Marketplace Reporting APIs and Partner Portal have been resolved. Both services are now back up and running normally. This incident has been resolved.

Read the full incident report →

Started Sep 25, 2025, 08:14 AM UTC· resolved Sep 25, 2025, 08:14 AM UTC

1. resolved Sep 25, 2025, 08:14 AM UTC

   We experienced a disruption affecting all JSM assets APIs using Connect JWT and user impersonation for connect apps, starting on September 13th at 2:05 AM UTC and lasting until September 17th at 3:36 PM UTC. This issue was caused by an internal routing change within Atlassian systems. During this time, all Assets API calls using Connect authentications were disrupted. The issue has now been resolved, and all affected APIs are fully operational again. We sincerely apologise for any inconvenience caused and thank you for your patience and understanding.

Read the full incident report →