Atlassian Developer

Affected: Forge Function Invocation

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-15 14:22 UTC

   We are investigating reports of an issue affecting select Marketplace apps across our cloud products. Users may experience intermittent errors or delays with affected webhooks functionality of apps. Our teams are actively analysing the issue, and we will provide our next update...

2. monitoring 2026-10-15 15:23 UTC

   We have applied mitigations to resolve the disruption affecting select Marketplace apps. We are observing positive signs of recovery across app operations, though minor intermittent delays may persist as traffic stabilises. Teams remain engaged and are actively monitoring the...

3. monitoring 2026-10-15 16:19 UTC

   Recovery continues across app operations, although some users may experience intermittent delays. We will continue to share additional updates here as more information becomes available.

4. resolved 2026-10-15 17:08 UTC

   On October 15, 2026, Marketplace app users in EU-West region may have experienced performance degradation. The issue has now been resolved, and the service is operating normally for all affected customers.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Forge Function Invocation

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-01 04:03 UTC

   Our teams have taken corrective steps to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered.

2. identified 2026-10-01 05:00 UTC

   Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. Along with impact to scheduled and asynchronous work across several products, we also identified SLA component in Jira Service...

3. identified 2026-10-01 07:01 UTC

   Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. There is also an impact to the new support tickets created in terms of missing SLA component, notifications which may be...

4. resolved 2026-10-01 07:51 UTC

   On 01st Oct 2026, between 01:00 UTC and 07:25 UTC, users may have seen missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected. We have now implemented a fix and and services have been restored to normal operation for...

5. postmortem 2026-10-09 18:24 UTC

   ### Summary On October 1, 2026, between 01:00 and 07:25 UTC, degraded job processing and scheduling impacted Atlassian products including Bitbucket Cloud, Confluence, Forge apps, Jira, and Jira Service Management in all commercial cloud regions. This caused delayed or missed...

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: App submissions

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-28 06:48 UTC

   Impact Marketplace app publishing is failing for some users in the Marketplace console. Affected users may see a generic Version publish failed message when trying to make a new app or app version public. Dozens of app publish attempts have been affected. Current Status The team...

2. resolved 2026-09-28 07:59 UTC

   The issue impacting Marketplace app and version publishing in the Atlassian Marketplace has been resolved. The publishing and approval workflows are now fully restored, and all services are operating normally. Root Cause: During scheduled maintenance over the weekend, the...

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Developer service desk, Marketplace service desk

Failure mode: A schema or data migration caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-09-27 05:45 UTC

   Scheduled maintenance window from September 25 @ 5PM PST to Monday, September 28 @ 10AM, AEST Our support portal is moving to a new home. New ticket submissions and ticket access including comments via email will be unavailable during this window. Starting September 28, submit...

2. investigating 2026-09-27 23:17 UTC

   We are currently experiencing an outage with our support infrastructure for Ecosystem Support (Developer and Marketplace Support) and services are temporarily unavailable. Our team is actively working on it and we expect services to be restored shortly. Next update will be...

3. resolved 2026-09-28 00:50 UTC

   Update: Migration Postponed During our scheduled migration over the weekend, we encountered an unexpected issue and made the decision to roll back and postpone the transition at this time. What you need to know - Continue using the current portal: Please continue submitting...

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Developer console

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-17 12:59 UTC

   We have identified the cause of the issue affecting the Developer Console where app versions and statuses in the Installation tab appear outdated. Please note that app installations and auto-upgrades continue to function normally in the background; this is isolated to the...

2. identified 2026-09-17 13:57 UTC

   The fix to correct the display discrepancy in the Developer Console Installation tab remains underway. Core app installations and upgrades are unaffected. We will provide the next update in 2 hours, or sooner.

3. resolved 2026-09-17 15:22 UTC

   On September 17, 2026, some Developer Console users may have experienced performance degradation where versions and statuses in the Installation tab were outdated. The issue has now been resolved, and the service is operating normally for all affected customers.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations, Forge Object Store

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-02 03:09 UTC

   We are investigating reports of Forge developer installation requests failing intermittently with 'InstallationRequestFailedError' message. We will share more information within the next 1 hour or sooner.

2. resolved 2026-09-02 03:17 UTC

   We have identified the cause of the issue impacting installation requests and deployed a fix. The issue is now resolved, and the service is operating normally for all affected customers.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations, Forge Object Store

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-08-25 10:58 UTC

   A fix has been successfully deployed for the issue affecting scheduled triggers (5-minute intervals) for some Marketplace apps. We continue to monitor the situation and should be fully recovered soon. We should be able to provide more updates in the one hour.

2. resolved 2026-08-25 11:11 UTC

   On Aug 25th, 2026, between 08:12 UTC and 11:03 UTC, some Marketplace apps may have experienced scheduled triggers (5-minute intervals) not firing as expected. The issue has now been resolved and the 5-minute scheduled triggers are operating normally for all customers.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations, Forge Object Store

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-03 03:26 UTC

   Our team is aware of an issue that was impacting the ability to install, uninstall or manage Forge and OAuth 2.0 integrated apps between 2026-08-03 01:47 UTC and 02:29 UTC. Apps that were already installed should have continued to run as normal during this impact window. We...

2. resolved 2026-08-03 03:37 UTC

   We have confirmed that the issues relating to installing, uninstalling and managing Forge and OAuth 2.0 apps should now be fully resolved.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations, Forge Object Store

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-13 15:48 UTC

   Marketplace partner pages are unavailable. Partners are unable to access dashboards and management interfaces, experiencing timeouts when attempting to load these pages. All partner-related functionality is affected. Investigation into the underlying cause is underway. Next...

2. monitoring 2026-07-13 17:17 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.

3. resolved 2026-07-13 17:46 UTC

   On Jul 13, 2026, partner operations may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations, Forge Object Store

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-30 02:45 UTC

   We are aware that some customers that are using the Time Tracker for Jira Cloud and DC app were incorrectly notified about the app converting to a free or a trial subscription. Our team is investigating this issue with urgency, and we are taking steps to ensure that impacted...

2. resolved 2026-07-02 04:43 UTC

   All customers that had previously received the incorrect notifications about the Time Tracker for Jira Cloud and DC app should have received corrective communications at this time. We are now resolving this issue.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-26 14:32 UTC

   We have identified the source of service performance issues, affecting your forge remote-apps services. Our team has initiated a remediation and is actively monitoring recovery. We will provide the next update within the next one hour.

2. identified 2026-06-26 15:28 UTC

   Our team has applied the mitigation, and we are seeing recovery. We will continue to share additional updates here as more information becomes available.

3. identified 2026-06-26 19:43 UTC

   Our team continues to monitor the recovery in progress, and we will share additional updates here as more information becomes available.

4. monitoring 2026-06-26 21:24 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.

5. resolved 2026-06-26 21:39 UTC

   On June 26, 2026, some customers may have experienced performance degradation with remote Forge apps facing rate-limiting issues. The issue has now been resolved, and the service is operating normally for all affected customers.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-10 04:55 UTC

   We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps. Our team is looking...

2. identified 2026-06-10 05:39 UTC

   Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products. At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers. We will...

3. monitoring 2026-06-10 06:14 UTC

   Our team has now determined that performance has returned to expected levels for those impacted by this incident. Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products...

4. resolved 2026-06-10 06:31 UTC

   We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-26 10:40 UTC

   We are investigating an issue where some custom extensions may fail to load when editing Confluence Cloud pages. Affected users may see 'Error loading the extension!' messages or notice that certain macros are missing from the editor's extension selection menu. Viewing published...

2. investigating 2026-05-26 11:58 UTC

   We are investigating an issue where some custom extensions may fail to load when editing Confluence Cloud pages. Affected users may see 'Error loading the extension!' messages or notice that certain macros are missing from the editor's extension selection menu. Viewing published...

3. investigating 2026-05-26 11:58 UTC

   We are actively investigating an issue affecting the editing macros in Confluence Cloud editor. Our team is working to identify the root cause. We will provide an update within approximately one hour.

4. resolved 2026-05-26 13:55 UTC

   Between 08:30 UTC and 13:51 UTC on 26 May 2026, some users were unable to load or edit certain macros in the Confluence Cloud page editor. Our engineering team identified and resolved the underlying issue, and macro functionality has been fully restored.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-20 12:06 UTC

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

2. resolved 2026-05-20 14:14 UTC

   The root cause has been identified and a fix has been applied. Full service restoration has been completed.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Forge App Alerts

Failure mode: A code release introduced the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-05-20 10:16 UTC

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

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-05-14 21:04 UTC

   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.

2. monitoring 2026-05-14 21:20 UTC

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

3. resolved 2026-05-14 21:35 UTC

   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.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-05-14 05:11 UTC

   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.

2. identified 2026-05-14 05:24 UTC

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

3. identified 2026-05-14 05:34 UTC

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

4. monitoring 2026-05-14 05:43 UTC

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

5. monitoring 2026-05-14 06:40 UTC

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

6. monitoring 2026-05-14 06:41 UTC

   We are approaching full system recovery at this time, and are performing final confirmations that services are restored.

7. resolved 2026-05-14 06:49 UTC

   All products and services impacted by this incident should now be fully recovered, and this incident is resolved.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Forge Function Invocation

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-05-12 15:50 UTC

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

2. identified 2026-05-12 16:57 UTC

   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.

3. monitoring 2026-05-12 17:17 UTC

   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.

4. resolved 2026-05-12 17:40 UTC

   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.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-12 14:03 UTC

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

2. investigating 2026-05-12 15:00 UTC

   Our teams are still investigating the root cause, and we will provide further updates within the next 2 hours.

3. identified 2026-05-12 16:27 UTC

   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.

4. monitoring 2026-05-12 17:52 UTC

   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.

5. resolved 2026-05-12 18:11 UTC

   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.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-11 14:24 UTC

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

2. identified 2026-05-11 14:48 UTC

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

3. identified 2026-05-11 15:45 UTC

   Our team has applied mitigation and is seeing improvement in US East region. Next update will be provided in one hour.

4. identified 2026-05-11 16:42 UTC

   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.

5. monitoring 2026-05-11 18:00 UTC

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

6. resolved 2026-05-11 18:16 UTC

   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.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-08 04:10 UTC

   We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

2. identified 2026-05-08 04:10 UTC

   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.

3. identified 2026-05-08 04:10 UTC

   Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

4. identified 2026-05-08 04:10 UTC

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

5. monitoring 2026-05-08 05:53 UTC

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

6. monitoring 2026-05-08 08:03 UTC

   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.

7. monitoring 2026-05-08 11:12 UTC

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

8. resolved 2026-05-08 19:45 UTC

   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.

9. postmortem 2026-05-20 06:58 UTC

   All dates and times below are in UTC unless stated otherwise. ### Summary On May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in prod-east which led to Atlassian customers experiencing degraded...

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-05 17:40 UTC

   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.

2. identified 2026-05-05 18:58 UTC

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

3. identified 2026-05-05 20:37 UTC

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

4. resolved 2026-05-05 22:34 UTC

   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.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-30 08:59 UTC

   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.

2. identified 2026-04-30 10:05 UTC

   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.

3. monitoring 2026-04-30 13:36 UTC

   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.

4. resolved 2026-04-30 14:56 UTC

   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.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-28 18:28 UTC

   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.

2. investigating 2026-04-28 18:34 UTC

   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.

3. identified 2026-04-28 20:16 UTC

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

4. monitoring 2026-04-28 21:34 UTC

   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.

5. resolved 2026-04-28 21:50 UTC

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

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-22 06:57 UTC

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

2. identified 2026-04-22 08:53 UTC

   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.

3. identified 2026-04-22 16:21 UTC

   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.

4. identified 2026-04-22 23:29 UTC

   We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

5. monitoring 2026-04-23 15:27 UTC

   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.

6. resolved 2026-04-23 16:14 UTC

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

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-13 10:58 UTC

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

2. identified 2026-04-13 13:32 UTC

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

3. resolved 2026-04-13 15:11 UTC

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

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-08 06:55 UTC

   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.

2. identified 2026-04-08 06:55 UTC

   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

3. identified 2026-04-08 07:45 UTC

   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

4. resolved 2026-04-08 07:45 UTC

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

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-02 20:46 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 2026-04-02 22:36 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.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-24 07:59 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 2026-03-24 08:44 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.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-17 10:05 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 2026-03-17 10:34 UTC

   We are continuing to investigate this issue.

3. investigating 2026-03-17 10:59 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...

4. resolved 2026-03-17 11:37 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.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-12 11:42 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...

2. investigating 2026-03-12 13:38 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...

3. identified 2026-03-12 13:38 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 2026-03-13 00:26 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.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: App listings, Reporting APIs and dashboards, Search

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-03-02 16:15 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...

2. monitoring 2026-03-03 17:06 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...

3. resolved 2026-03-04 03:04 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,...

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Developer console

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-16 11:24 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...

2. identified 2026-02-16 11:27 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...

3. resolved 2026-02-19 17:12 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...

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-13 07:41 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 2026-02-16 00:24 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....

3. identified 2026-02-16 05:30 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 2026-02-17 05:40 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...

5. monitoring 2026-02-19 00:51 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...

6. monitoring 2026-02-19 08:04 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 2026-02-19 08:04 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.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Forge Function Invocation

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-06 09:37 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...

2. identified 2026-02-06 10:39 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...

3. resolved 2026-02-06 11:32 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...

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-03 10:19 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...

2. investigating 2026-02-03 10:24 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...

3. resolved 2026-02-03 10:50 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.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-28 17:34 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 2026-01-28 18:33 UTC

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

3. monitoring 2026-01-28 19:02 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 2026-01-28 19:20 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.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Developer console

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-12-16 05:47 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 2025-12-16 05:47 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 2025-12-16 16:14 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...

4. identified 2025-12-16 16:14 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...

5. resolved 2025-12-17 06:07 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.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-11 01:08 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 2025-12-11 02:08 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...

3. resolved 2025-12-11 04:37 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.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: App listings, App submissions

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-12-09 08:14 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...

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-12-05 08:08 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...

2. investigating 2025-12-05 09:23 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....

3. investigating 2025-12-05 09:56 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....

4. investigating 2025-12-05 11:06 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....

5. resolved 2025-12-05 12:09 UTC

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

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-10 10:41 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...

2. resolved 2025-11-10 14:03 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...

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Reporting APIs and dashboards

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-10-27 12:04 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...

2. identified 2025-10-28 04:22 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...

3. monitoring 2025-10-28 13:04 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...

4. resolved 2025-10-28 13:42 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...

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Webhooks

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-22 12:15 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 2025-10-22 13:14 UTC

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

3. investigating 2025-10-22 14:20 UTC

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

4. investigating 2025-10-22 16:16 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 2025-10-22 19:09 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 2025-10-22 20:07 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 2025-10-22 22:09 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,...

8. postmortem 2025-11-08 04:22 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...

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 07:56 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 2025-10-20 08:24 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 2025-10-20 09:23 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...

4. investigating 2025-10-20 09:24 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...

5. identified 2025-10-20 09:58 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 2025-10-20 11:06 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 2025-10-20 12:06 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 2025-10-20 13:07 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 2025-10-20 13:56 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 2025-10-20 13:58 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 2025-10-20 14:02 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...

12. identified 2025-10-20 15:20 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...

13. identified 2025-10-20 15:21 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...

14. identified 2025-10-20 16:35 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...

15. identified 2025-10-20 16:36 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...

16. identified 2025-10-20 17:27 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...

17. identified 2025-10-20 17:43 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...

18. monitoring 2025-10-20 18:38 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....

19. monitoring 2025-10-20 21:26 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...

20. monitoring 2025-10-20 22:58 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 2025-10-21 00:03 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...

22. monitoring 2025-10-21 01:07 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...

23. monitoring 2025-10-21 03:24 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...

24. resolved 2025-10-21 05:24 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...

25. postmortem 2025-10-24 17:45 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...

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-12 15:25 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...

2. investigating 2025-10-12 17:19 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 2025-10-12 18:33 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 2025-10-12 19:25 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.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-12 07:29 UTC

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

2. monitoring 2025-10-12 08:51 UTC

   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.

3. resolved 2025-10-12 09:14 UTC

   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.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: End-user consent

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-10-03 03:43 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...

2. monitoring 2025-10-03 06:04 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 2025-10-03 06:24 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.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Forge App Logs

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-09-29 15:32 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 2025-09-29 17:07 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...

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.

Affected: Reporting APIs and dashboards

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-09-26 10:09 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...

2. identified 2025-09-26 10:10 UTC

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

3. monitoring 2025-09-26 10:28 UTC

   A fix has been implemented and monitoring the fix.

4. resolved 2025-09-26 10:45 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.

Excerpts are shortened. Read the full incident on Atlassian Developer's status page.