Apr <var data-var='date'> 8</var>, <var data-var='time'>07:45</var> UTC Resolved - The outage affecting Forge app logs between 05:00 UTC and 07:00 UTC on 8 April 2026 has been resolved, and systems are now stable. We are currently working on recovery efforts, including retrieving logs from this downtime window and validating data completeness. During this process, you may temporarily see duplicate log entries; however, this will not result in duplicate usage or additional costs. We will continue to monitor the system closely and provide further updates as needed.Apr <var data-var='date'> 8</var>, <var data-var='time'>07:45</var> UTC Update - We have identified a failure in the Forge App logs experience, impacting Forge Ecosystem Cloud developers and vendors. Our teams are working on it's resolutionApr <var data-var='date'> 8</var>, <var data-var='time'>06:55</var> UTC Identified - We have identified a failure in the Forge App logs experience, impacting Forge Ecosystem Cloud developers and vendors. Our teams are working on it's resolutionApr <var data-var='date'> 8</var>, <var data-var='time'>06:55</var> UTC Investigating - We are investigating a failure in the Forge App logs experience, impacting Forge Ecosystem Cloud developers and vendors. We will provide more details once we identify the root cause.

Read/Write logs for Forge Apps down

Apr <var data-var='date'> 2</var>, <var data-var='time'>22:36</var> UTC Resolved - 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.Apr <var data-var='date'> 2</var>, <var data-var='time'>20:46</var> UTC Investigating - 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.

Disrupted Forge availability

Mar <var data-var='date'>30</var>, <var data-var='time'>00:00</var> UTC Completed - The scheduled maintenance has been completed.Mar <var data-var='date'>29</var>, <var data-var='time'>23:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Mar <var data-var='date'>20</var>, <var data-var='time'>03:30</var> UTC Scheduled - Atlassian will be undergoing scheduled maintenance with ~1 hour of intermittent downtime in the FedRAMP perimeter on 2026-03-29 between 23:00 and 2026-03-30 00:00 UTC. During the outage, you won’t be able to: - Create/upgrade/delete apps - Install/uninstall apps - Upgrade installations - Deploy apps - Grant/revoke access for apps - Grant consent to apps - Revoke consent to apps Expect to see the above operations fail with 500 status code and you will need to retry the operations after maintenance is successfully completed. We will continue to provide updates as we progress and when you can expect these services to be restored.

Scheduled Maintenance of Forge FedRAMP services

Mar <var data-var='date'>24</var>, <var data-var='time'>08:44</var> UTC Resolved - 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.Mar <var data-var='date'>24</var>, <var data-var='time'>07:59</var> UTC Identified - 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

Connect Apps Performance Degradation

Mar <var data-var='date'>17</var>, <var data-var='time'>11:37</var> UTC Resolved - 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.Mar <var data-var='date'>17</var>, <var data-var='time'>10:59</var> UTC Update - 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.Mar <var data-var='date'>17</var>, <var data-var='time'>10:34</var> UTC Update - We are continuing to investigate this issue.Mar <var data-var='date'>17</var>, <var data-var='time'>10:05</var> UTC Investigating - We are actively investigating reports of performance degradation affecting Forge apps and Developer console will share updates here as more information becomes available.

Incident impacting Forge app installations and Dev console

Mar <var data-var='date'>13</var>, <var data-var='time'>00:26</var> UTC Resolved - 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.Mar <var data-var='date'>12</var>, <var data-var='time'>13:38</var> UTC Identified - 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.Mar <var data-var='date'>12</var>, <var data-var='time'>13:38</var> UTC Update - 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.Mar <var data-var='date'>12</var>, <var data-var='time'>11:42</var> UTC Investigating - 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.

Static macro rendering is failing in Confluence Cloud

Mar <var data-var='date'> 4</var>, <var data-var='time'>03:04</var> UTC Resolved - 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.Mar <var data-var='date'> 3</var>, <var data-var='time'>17:06</var> UTC Update - 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.Mar <var data-var='date'> 2</var>, <var data-var='time'>16:15</var> UTC Monitoring - 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.

Inaccurate install counts for some Marketplace apps on Marketplace

Feb <var data-var='date'>19</var>, <var data-var='time'>17:12</var> UTC Resolved - 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.Feb <var data-var='date'>16</var>, <var data-var='time'>11:27</var> UTC Identified - 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.Feb <var data-var='date'>16</var>, <var data-var='time'>11:24</var> UTC Investigating - 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.

Forge billing subscriptions cancelled for some apps

Feb <var data-var='date'>19</var>, <var data-var='time'>08:04</var> UTC Resolved - 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.Feb <var data-var='date'>19</var>, <var data-var='time'>08:04</var> UTC Update - 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.Feb <var data-var='date'>19</var>, <var data-var='time'>00:51</var> UTC Monitoring - 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.Feb <var data-var='date'>17</var>, <var data-var='time'>05:40</var> UTC Update - 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.Feb <var data-var='date'>16</var>, <var data-var='time'>05:30</var> UTC Update - 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.Feb <var data-var='date'>16</var>, <var data-var='time'>00:24</var> UTC Update - 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.Feb <var data-var='date'>13</var>, <var data-var='time'>07:41</var> UTC Identified - 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.

Increased error rates on Jira and Jira Service Management Ecosystem Apps

Feb <var data-var='date'>14</var>, <var data-var='time'>07:00</var> UTC Completed - The scheduled maintenance has been completed.Feb <var data-var='date'>14</var>, <var data-var='time'>06:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Feb <var data-var='date'> 6</var>, <var data-var='time'>05:22</var> UTC Scheduled - Atlassian will be undergoing scheduled maintenance with ~1 hour of intermittent downtime in the FedRAMP perimeter on 2026-02-14 between 06:00 and 07:00 UTC. During the outage, you won’t be able to: - Create/upgrade/delete apps - Install/uninstall apps - Upgrade installations - Deploy apps - Grant/revoke access for apps - Grant consent to apps - Revoke consent to apps Expect to see the above operations fail with 500 status code and you will need to retry the operations after maintenance is successfully completed. We will continue to provide updates as we progress and when you can expect these services to be restored.

Feb <var data-var='date'> 6</var>, <var data-var='time'>11:32</var> UTC Resolved - 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.Feb <var data-var='date'> 6</var>, <var data-var='time'>10:39</var> UTC Identified - 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.Feb <var data-var='date'> 6</var>, <var data-var='time'>09:37</var> UTC Investigating - 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.

Scheduled Triggers not working for Forge apps

Feb <var data-var='date'> 3</var>, <var data-var='time'>10:50</var> UTC Resolved - 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.Feb <var data-var='date'> 3</var>, <var data-var='time'>10:24</var> UTC Update - 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.Feb <var data-var='date'> 3</var>, <var data-var='time'>10:19</var> UTC Investigating - 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.

Confluence, Jira Mobile and Forge users may experience authentication issues

Jan <var data-var='date'>28</var>, <var data-var='time'>19:20</var> UTC Resolved - 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.Jan <var data-var='date'>28</var>, <var data-var='time'>19:02</var> UTC Monitoring - The issue has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor closely to confirm stability.Jan <var data-var='date'>28</var>, <var data-var='time'>18:33</var> UTC Update - We continue to investigate the issue, and will share updates here as more information becomes available.Jan <var data-var='date'>28</var>, <var data-var='time'>17:34</var> UTC Investigating - We are actively investigating reports of a partial service disruption affecting Forge. We'll share updates here as more information is available.

Disrupted Forge Function Invocation availability

Dec <var data-var='date'>17</var>, <var data-var='time'>06:07</var> UTC Resolved - 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.Dec <var data-var='date'>16</var>, <var data-var='time'>16:14</var> UTC Identified - 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.Dec <var data-var='date'>16</var>, <var data-var='time'>16:14</var> UTC Monitoring - 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.Dec <var data-var='date'>16</var>, <var data-var='time'>05:47</var> UTC Update - 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.Dec <var data-var='date'>16</var>, <var data-var='time'>05:47</var> UTC Identified - 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.

Forge usage and charges data is missing from the developer console

Dec <var data-var='date'>11</var>, <var data-var='time'>04:37</var> UTC Resolved - 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.Dec <var data-var='date'>11</var>, <var data-var='time'>02:08</var> UTC Identified - 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.Dec <var data-var='date'>11</var>, <var data-var='time'>01:08</var> UTC Investigating - 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.

Errors installing Connect on Forge Apps in Confluence

Dec <var data-var='date'> 9</var>, <var data-var='time'>08:14</var> UTC Resolved - 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.

Auto publish failure for Marketplace forge app versions

Dec <var data-var='date'> 5</var>, <var data-var='time'>12:09</var> UTC Resolved - The feature flag causing the issue has been reverted, fixing the problem. With that this incident is resolved.Dec <var data-var='date'> 5</var>, <var data-var='time'>11:06</var> UTC Update - 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.Dec <var data-var='date'> 5</var>, <var data-var='time'>09:56</var> UTC Update - 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.Dec <var data-var='date'> 5</var>, <var data-var='time'>09:23</var> UTC Update - 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.Dec <var data-var='date'> 5</var>, <var data-var='time'>08:08</var> UTC Investigating - 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.

Multiple customer sites have lost access to Support tickets

Nov <var data-var='date'>23</var>, <var data-var='time'>06:30</var> UTC Completed - The scheduled maintenance has been completed.Nov <var data-var='date'>23</var>, <var data-var='time'>05:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Nov <var data-var='date'>14</var>, <var data-var='time'>11:05</var> UTC Scheduled - Atlassian will be undergoing scheduled maintenance with up to 1 minute of downtime in the commercial perimeter on 2025-11-23 between 5:30am to 6:30am UTC. During the write outage, you won’t be able to: - Create/upgrade/delete apps - Install/uninstall apps - Upgrade installations - Deploy app - Grant/revoke access for apps - Grant consent to apps - Revoke consent to apps Expect to see the above operations fail with 500 status code and you will need to retry the operations after maintenance is successfully completed. We will continue to provide updates as we progress and when you can expect these services to be restored.

Scheduled Maintenance for systems impacting Forge app lifecycle

Nov <var data-var='date'>10</var>, <var data-var='time'>14:03</var> UTC Resolved - 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.Nov <var data-var='date'>10</var>, <var data-var='time'>10:41</var> UTC Investigating - 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.

Degradation in forge logs availability

Oct <var data-var='date'>28</var>, <var data-var='time'>13:42</var> UTC Resolved - 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.Oct <var data-var='date'>28</var>, <var data-var='time'>13:04</var> UTC Monitoring - 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.Oct <var data-var='date'>28</var>, <var data-var='time'>04:22</var> UTC Update - 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.Oct <var data-var='date'>27</var>, <var data-var='time'>12:04</var> UTC Identified - 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.

Marketplace | Aggregated Sales, Transaction Reporting, and Export Transaction APIs experiencing Data Discrepancies

Oct <var data-var='date'>22</var>, <var data-var='time'>22:09</var> UTC Resolved - 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.Oct <var data-var='date'>22</var>, <var data-var='time'>20:07</var> UTC Update - 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.Oct <var data-var='date'>22</var>, <var data-var='time'>19:09</var> UTC Identified - 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.Oct <var data-var='date'>22</var>, <var data-var='time'>16:16</var> UTC Update - 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.Oct <var data-var='date'>22</var>, <var data-var='time'>14:20</var> UTC Update - We are continuing our investigation. We will provide the next update within two hours or sooner.Oct <var data-var='date'>22</var>, <var data-var='time'>13:14</var> UTC Update - Our team continues to investigate this issue. We will provide the next update within one hour or sooner.Oct <var data-var='date'>22</var>, <var data-var='time'>12:15</var> UTC Investigating - 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.

Confluence Webhooks are not being delivered

Oct <var data-var='date'>21</var>, <var data-var='time'>05:24</var> UTC Resolved - 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.Oct <var data-var='date'>21</var>, <var data-var='time'>03:24</var> UTC Update - 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.Oct <var data-var='date'>21</var>, <var data-var='time'>01:07</var> UTC Update - 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.Oct <var data-var='date'>21</var>, <var data-var='time'>00:03</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>22:58</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>21:26</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>18:38</var> UTC Monitoring - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>17:43</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>17:27</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>16:36</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>16:35</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>15:21</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>15:20</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>14:02</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>13:58</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>13:56</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>13:07</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>12:06</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>11:06</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>09:58</var> UTC Identified - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>09:24</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>09:23</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>08:24</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>07:56</var> UTC Investigating - 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.

Atlassian Cloud Services impacted

Oct <var data-var='date'>12</var>, <var data-var='time'>19:25</var> UTC Resolved - 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.Oct <var data-var='date'>12</var>, <var data-var='time'>18:33</var> UTC Monitoring - 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.Oct <var data-var='date'>12</var>, <var data-var='time'>17:19</var> UTC Update - 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.Oct <var data-var='date'>12</var>, <var data-var='time'>15:25</var> UTC Investigating - 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.

Forge authenticated egress intermittent failure

Oct <var data-var='date'>12</var>, <var data-var='time'>09:14</var> UTC Resolved - Between 06:30 12th Oct, 2025 UTC to 08:33 12th Oct, 2025 UTC, we experienced a degradation in us-east and ca-central regions affecting authenticated egress calls from Forge functions and from Forge bridge. The issue has been resolved and the service is operating normally.Oct <var data-var='date'>12</var>, <var data-var='time'>08:51</var> UTC Monitoring - The errors have gone down and not occurred in the last 30 minutes. The issue has been mitigated and we are continuing to monitor the situation closely.Oct <var data-var='date'>12</var>, <var data-var='time'>07:29</var> UTC Investigating - We are aware of an intermittent issue affecting some authenticated egress calls from Forge functions and from Forge bridge (including product API calls). The issue is primarily affecting invocations in the us-east and ca-central regions. We are investigating the root cause and will provide an update in 1 hour.

Oct <var data-var='date'>12</var>, <var data-var='time'>04:00</var> UTC Completed - The scheduled maintenance has been completed.Oct <var data-var='date'>12</var>, <var data-var='time'>03:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Oct <var data-var='date'> 2</var>, <var data-var='time'>01:47</var> UTC Scheduled - Atlassian will be undergoing scheduled maintenance with up to 1 minute of downtime in the commercial perimeter on 2025-10-12 between 3am to 4am UTC. During the write outage, you won’t be able to: - Create/upgrade/delete apps - Install/uninstall apps - Upgrade installations - Deploy app - Grant/revoke access for apps - Grant consent to apps - Revoke consent to apps Expect to see the above operations fail with 500 status code and you will need to retry the operations after maintenance is successfully completed. We will continue to provide updates as we progress and when you can expect these services to be restored.

Is Atlassian Developers down?

Atlassian Developers status is UP

Lastest published events

Read/Write logs for Forge Apps down

Disrupted Forge availability

Scheduled Maintenance of Forge FedRAMP services

Atlassian Developers Services, Components and Regions

Recent Atlassian Developers events

Read/Write logs for Forge Apps down

Disrupted Forge availability

Scheduled Maintenance of Forge FedRAMP services

Connect Apps Performance Degradation

Incident impacting Forge app installations and Dev console

Static macro rendering is failing in Confluence Cloud

Get your FREE account now,
5 monitors included!

Is Atlassian Developers down?

Atlassian Developers status is UP

Lastest published events

Read/Write logs for Forge Apps down

Disrupted Forge availability

Scheduled Maintenance of Forge FedRAMP services

Atlassian Developers Services, Components and Regions

Recent Atlassian Developers events

Read/Write logs for Forge Apps down

Disrupted Forge availability

Scheduled Maintenance of Forge FedRAMP services

Connect Apps Performance Degradation

Incident impacting Forge app installations and Dev console

Static macro rendering is failing in Confluence Cloud

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!