May <var data-var='date'>20</var>, <var data-var='time'>14:14</var> UTC Resolved - The root cause has been identified and a fix has been applied. Full service restoration has been completed. May <var data-var='date'>20</var>, <var data-var='time'>12:06</var> UTC Identified - Our teams have identified the root cause and are in process of deploying a fix. We will share further updates in next 3 hours, or sooner if we have any meaningful developments to report. The impact is limited to new deployments with Forge custom fields on Jira work items, however existing deployments with custom fields are running without any issues.

Forge custom fields are not getting created

May <var data-var='date'>20</var>, <var data-var='time'>10:16</var> UTC Resolved - Due to an incorrect deployment, a banner stating 'This app may stop working soon' was briefly displayed on the Marketplace Apps. This banner was not intended to appear on these apps. The feature has since been corrected and the banner is no longer appearing. No action is required, the banner was displayed in error and there is no impact to app functionality or availability. We apologise for any confusion this may have caused.

Incorrect Banner appeared on MarketPlace Apps

May <var data-var='date'>14</var>, <var data-var='time'>21:35</var> UTC Resolved - On May 14, 2026, Developer and Marketplace service desks were inaccessible for affected users. The issue has now been resolved, and the service is operating normally for all affected customers. May <var data-var='date'>14</var>, <var data-var='time'>21:20</var> UTC Monitoring - The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability. May <var data-var='date'>14</var>, <var data-var='time'>21:04</var> UTC Identified - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience inaccessibility for Developer and Marketplace service desks. We will continue to share additional updates here as more information is available.

Disrupted Service Desk availability

May <var data-var='date'>14</var>, <var data-var='time'>06:49</var> UTC Resolved - All products and services impacted by this incident should now be fully recovered, and this incident is resolved. May <var data-var='date'>14</var>, <var data-var='time'>06:41</var> UTC Update - We are approaching full system recovery at this time, and are performing final confirmations that services are restored. May <var data-var='date'>14</var>, <var data-var='time'>06:40</var> UTC Update - We are now able to see recovery for all impacted products, and users should be able to access their products as expected. Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed. May <var data-var='date'>14</var>, <var data-var='time'>05:43</var> UTC Monitoring - Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place. May <var data-var='date'>14</var>, <var data-var='time'>05:34</var> UTC Update - Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products. At this time, Atlassian customers should also be able to once again raise support requests with our team. We will provide further update within an hour as we are able to progress mitigating this issue. May <var data-var='date'>14</var>, <var data-var='time'>05:24</var> UTC Update - It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident. We are continuing to receive reports about expanded product impact resulting from this incident. While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information. We will provide further update within one hour, or sooner as further information becomes available. May <var data-var='date'>14</var>, <var data-var='time'>05:11</var> UTC Identified - Further confirmations of impacted products have now been added to the incident. Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

Users experiencing issues accessing multiple Atlassian products

May <var data-var='date'>12</var>, <var data-var='time'>18:11</var> UTC Resolved - On May 12, 2026, some users in EU West region may have experienced delayed or queued webhook events. The issue has now been resolved, and the service is operating normally for all affected customers. May <var data-var='date'>12</var>, <var data-var='time'>17:52</var> UTC Monitoring - Delayed or queued webhook events issue has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability. May <var data-var='date'>12</var>, <var data-var='time'>16:27</var> UTC Identified - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience delayed or queued webhook events. We will continue to share additional updates here as more information is available. May <var data-var='date'>12</var>, <var data-var='time'>15:00</var> UTC Update - Our teams are still investigating the root cause, and we will provide further updates within the next 2 hours. May <var data-var='date'>12</var>, <var data-var='time'>14:03</var> UTC Investigating - We are aware of delays in Webhook event delivery that may be impacting Marketplace app integrations, primarily in the EU-West region. Some partners may experience delayed or queued Webhook Events. Our teams are investigating the root cause, and we will provide further updates within the next 1 hour.

Delay in Jira Webhook Delivery

May <var data-var='date'>12</var>, <var data-var='time'>17:40</var> UTC Resolved - On May 12, 2026, some users in US East region may have experienced intermittent failures with forge invocations for some applications. The issue has now been resolved, and the service is operating normally for all affected customers. May <var data-var='date'>12</var>, <var data-var='time'>17:17</var> UTC Monitoring - Intermittent failures with forge invocations for some applications have been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability. May <var data-var='date'>12</var>, <var data-var='time'>16:57</var> UTC Update - We are seeing improvements in intermittent failures with forge invocations for some applications. Our team continues to work diligently on full mitigation, and we will continue to share additional updates as more information becomes available. May <var data-var='date'>12</var>, <var data-var='time'>15:50</var> UTC Identified - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience intermittent failures with forge invocations for some applications. We will continue to share additional updates here as more information is available.

Degraded performance of forge invocations

May <var data-var='date'>11</var>, <var data-var='time'>18:16</var> UTC Resolved - On May 11, 2026, users in EU West and US East regions may have experienced performance degradation with delayed or queued webhook events. The issue has now been resolved, and the service is operating normally for all affected customers. May <var data-var='date'>11</var>, <var data-var='time'>18:00</var> UTC Monitoring - The issue has been resolved, and services are now operating normally for all affected customers. We will continue to monitor closely to confirm stability. May <var data-var='date'>11</var>, <var data-var='time'>16:42</var> UTC Update - Our team continues to see improvements in US East region with delayed or queued webhook events declining. Next update will be provided in 90 minutes. May <var data-var='date'>11</var>, <var data-var='time'>15:45</var> UTC Update - Our team has applied mitigation and is seeing improvement in US East region. Next update will be provided in one hour. May <var data-var='date'>11</var>, <var data-var='time'>14:48</var> UTC Update - Webhook event delivery in the EU West region has recovered and is operating normally. However, we are now seeing reports of similar delays in the US East region. Our team is actively investigating and working to resolve this. We will continue to monitor and provide further updates. May <var data-var='date'>11</var>, <var data-var='time'>14:24</var> UTC Identified - We are aware of delays in webhook event delivery that may be impacting Marketplace app integrations, primarily in the EU west region. Some partners may experience delayed or queued webhook events. Our team has identified the root cause and has taken action to mitigate the issue. We will continue to monitor and provide updates as the situation progresses.

Delays in Jira Webhook delivery

May <var data-var='date'> 8</var>, <var data-var='time'>19:45</var> UTC Resolved - On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers. May <var data-var='date'> 8</var>, <var data-var='time'>11:12</var> UTC Update - Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team. We apologise for the disruption and thank you for your patience. May <var data-var='date'> 8</var>, <var data-var='time'>08:03</var> UTC Update - We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour. May <var data-var='date'> 8</var>, <var data-var='time'>05:53</var> UTC Monitoring - The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared. May <var data-var='date'> 8</var>, <var data-var='time'>04:10</var> UTC Update - We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each product page. May <var data-var='date'> 8</var>, <var data-var='time'>04:10</var> UTC Update - Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available. May <var data-var='date'> 8</var>, <var data-var='time'>04:10</var> UTC Identified - We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available. May <var data-var='date'> 8</var>, <var data-var='time'>04:10</var> UTC Investigating - We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

Multiple Atlassian services are experiencing issues

May <var data-var='date'> 5</var>, <var data-var='time'>22:34</var> UTC Resolved - On Tuesday, May 5, 2026, some Forge users may have experienced performance delays in webhook delivery in the US East region. The issue has now been resolved, and the service is operating normally for all affected customers. May <var data-var='date'> 5</var>, <var data-var='time'>20:37</var> UTC Update - Our teams have identified the cause of the issue and are continuing to work on mitigations. We continue to see signs of improvement. Affected users may experience some delays in web hook delivery in the US East region. We'll continue to share additional updates here as more information is available. May <var data-var='date'> 5</var>, <var data-var='time'>18:58</var> UTC Identified - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. We are seeing signs of improvement. Affected users may experience some delays in web hook delivery in the US East region. We'll continue to share additional updates here as more information is available. May <var data-var='date'> 5</var>, <var data-var='time'>17:40</var> UTC Investigating - We are actively investigating reports of performance degradation affecting Forge webhook delivery in the US East region. We will share updates here as more information is available.

Degraded performance of Forge trigger

Apr <var data-var='date'>30</var>, <var data-var='time'>14:56</var> UTC Resolved - The issue causing intermittent delays in our webhook delivery has been resolved. A fix was deployed to address a resource constraint in our systems. Our monitoring shows webhook delivery is now operating normally. Apr <var data-var='date'>30</var>, <var data-var='time'>13:36</var> UTC Monitoring - A fix has been deployed to address the intermittent delays in Jira webhook delivery. We are actively monitoring the situation to confirm full recovery. We will continue to provide updates as available. Apr <var data-var='date'>30</var>, <var data-var='time'>10:05</var> UTC Identified - We have identified the cause of the delayed Jira webhook delivery and are deploying a fix. We will continue to provide updates as more information becomes available. Apr <var data-var='date'>30</var>, <var data-var='time'>08:59</var> UTC Investigating - We are investigating reports of delays in webhook delivery. Customers may experience intermittent delays when receiving webhooks. Our engineering teams are actively investigating and working to resolve the issue. We will provide updates as more information becomes available.

Delays in Jira webhook delivery

Apr <var data-var='date'>28</var>, <var data-var='time'>21:50</var> UTC Resolved - The issue has now been resolved, and the service is operating normally for all affected customers. Apr <var data-var='date'>28</var>, <var data-var='time'>21:34</var> UTC Monitoring - The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability. Apr <var data-var='date'>28</var>, <var data-var='time'>20:16</var> UTC Identified - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers. We will continue to share additional updates here as more information is available. Apr <var data-var='date'>28</var>, <var data-var='time'>18:34</var> UTC Update - We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available. Apr <var data-var='date'>28</var>, <var data-var='time'>18:28</var> UTC Investigating - We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Apr <var data-var='date'>23</var>, <var data-var='time'>16:14</var> UTC Resolved - The issue has now been resolved, and the service is operating normally for all affected customers. Apr <var data-var='date'>23</var>, <var data-var='time'>15:27</var> UTC Monitoring - The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability. Apr <var data-var='date'>22</var>, <var data-var='time'>23:29</var> UTC Update - We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution. Apr <var data-var='date'>22</var>, <var data-var='time'>16:21</var> UTC Update - After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if there are any major developments. Apr <var data-var='date'>22</var>, <var data-var='time'>08:53</var> UTC Identified - Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report. Apr <var data-var='date'>22</var>, <var data-var='time'>06:57</var> UTC Investigating - We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted. If your app is impacted by this issue, the 429 response will contain the following headers: X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0 Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly. Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Some Forge apps experiencing increased Jira API rate limiting errors (429)

Apr <var data-var='date'>13</var>, <var data-var='time'>15:11</var> UTC Resolved - The issue has now been resolved, and the service is operating normally for all affected customers. Apr <var data-var='date'>13</var>, <var data-var='time'>13:32</var> UTC Identified - Transaction information for Marketplace apps has been restored and is now appearing again in partner reports. You may still see up to a 3-hour delay before new transactions show in your reports while we work to bring this back to normal. We are closely monitoring the situation and will continue to share updates. Apr <var data-var='date'>13</var>, <var data-var='time'>10:58</var> UTC Investigating - We are aware that transaction-related information for Marketplace apps has not been available in partner reports since April 10, 2026. Our team is actively investigating the root cause and working to restore the data. Partners may notice missing transaction records for this period. We will provide updates as we have more information. We apologize for the inconvenience.

Missing Marketplace transaction data in partner reports since April, 10 2026

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 resolution Apr <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 resolution Apr <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.

Is Atlassian Developers down?

Atlassian Developers status is UP

Lastest published events

Forge custom fields are not getting created

Incorrect Banner appeared on MarketPlace Apps

Disrupted Service Desk availability

Atlassian Developers Services, Components and Regions

Recent Atlassian Developers events

Forge custom fields are not getting created

Incorrect Banner appeared on MarketPlace Apps

Disrupted Service Desk availability

Users experiencing issues accessing multiple Atlassian products

Delay in Jira Webhook Delivery

Degraded performance of forge invocations

Get your FREE account now,
5 monitors included!

Is Atlassian Developers down?

Atlassian Developers status is UP

Lastest published events

Forge custom fields are not getting created

Incorrect Banner appeared on MarketPlace Apps

Disrupted Service Desk availability

Atlassian Developers Services, Components and Regions

Recent Atlassian Developers events

Forge custom fields are not getting created

Incorrect Banner appeared on MarketPlace Apps

Disrupted Service Desk availability

Users experiencing issues accessing multiple Atlassian products

Delay in Jira Webhook Delivery

Degraded performance of forge invocations

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!