Atlassian Developer Outage History

Atlassian Developer is up right now

Atlassian Developer had 49 outages in the last 2 years totaling 272h 28m of downtime — averaging 2 incidents per month.

There were 49 Atlassian Developer outages since August 29, 2025 totaling 272h 28m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://developer.status.atlassian.com

Critical August 3, 2026

Issues installing, uninstalling and managing Forge or OAuth 2.0 apps

Detected by Pingoru
Aug 03, 2026, 03:26 AM UTC
Resolved
Aug 03, 2026, 03:37 AM UTC
Duration
11m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags EvaluationsForge Object Store
Timeline · 2 updates
  1. investigating Aug 03, 2026, 03:26 AM 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 believe we have now rectified this issue and are monitoring for ongoing impact. We apologize for any inconvenience this may have caused.

  2. resolved Aug 03, 2026, 03:37 AM UTC

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

Read the full incident report →

Minor July 13, 2026

Marketplace : Partner operations are down

Detected by Pingoru
Jul 13, 2026, 03:48 PM UTC
Resolved
Jul 13, 2026, 05:46 PM UTC
Duration
1h 57m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags EvaluationsForge Object Store
Timeline · 3 updates
  1. investigating Jul 13, 2026, 03:48 PM 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 comms will be sent in 60 minutes or upon significant progress.

  2. monitoring Jul 13, 2026, 05:17 PM UTC

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

  3. resolved Jul 13, 2026, 05:46 PM 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.

Read the full incident report →

Minor June 30, 2026

Some customers received incorrect Time Tracker for Jira Cloud and DC app emails relating to free and trial subscriptions.

Detected by Pingoru
Jun 30, 2026, 02:45 AM UTC
Resolved
Jul 02, 2026, 04:43 AM UTC
Duration
2d 1h
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags EvaluationsForge Object Store
Timeline · 2 updates
  1. investigating Jun 30, 2026, 02:45 AM 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 will plan to notify any customers that received the incorrect email with a correction. There is no action required from those customers that have incorrectly received these emails. We apologize for any inconvenience this may have caused.

  2. resolved Jul 02, 2026, 04:43 AM 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.

Read the full incident report →

Minor June 26, 2026

Remote Forge Apps facing rate-limiting issues

Detected by Pingoru
Jun 26, 2026, 02:32 PM UTC
Resolved
Jun 26, 2026, 09:39 PM UTC
Duration
7h 6m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags Evaluations
Timeline · 5 updates
  1. identified Jun 26, 2026, 02:32 PM 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 Jun 26, 2026, 03:28 PM 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 Jun 26, 2026, 07:43 PM UTC

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

  4. monitoring Jun 26, 2026, 09:24 PM UTC

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

  5. resolved Jun 26, 2026, 09:39 PM 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.

Read the full incident report →

Minor June 10, 2026

Delays in processing incoming Emails, Work Item notifications, and Scheduled Triggers in Marketplace Apps

Detected by Pingoru
Jun 10, 2026, 04:55 AM UTC
Resolved
Jun 10, 2026, 06:31 AM UTC
Duration
1h 35m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags Evaluations
Timeline · 4 updates
  1. investigating Jun 10, 2026, 04:55 AM 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 into this with urgency and we will provide further update within one hour as our investigation continues.

  2. identified Jun 10, 2026, 05:39 AM 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 provide further update within one hour or when we have seen a full recovery of all task processing across these products.

  3. monitoring Jun 10, 2026, 06:14 AM 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 would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

  4. resolved Jun 10, 2026, 06:31 AM 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.

Read the full incident report →

Notice May 26, 2026

Some macros failing to load in the Confluence Cloud editor

Detected by Pingoru
May 26, 2026, 10:40 AM UTC
Resolved
May 26, 2026, 01:55 PM UTC
Duration
3h 15m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags Evaluations
Timeline · 4 updates
  1. investigating May 26, 2026, 10:40 AM 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 pages is not affected. Our engineering team is actively investigating and working toward a resolution. We will provide an update within an hour or as more information becomes available.

  2. investigating May 26, 2026, 11:58 AM 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 pages is not affected. Our engineering team is actively investigating and working toward a resolution. We will provide an update within an hour or as more information becomes available.

  3. investigating May 26, 2026, 11:58 AM 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 May 26, 2026, 01:55 PM 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.

Read the full incident report →

Minor May 20, 2026

Forge custom fields are not getting created

Detected by Pingoru
May 20, 2026, 12:06 PM UTC
Resolved
May 20, 2026, 02:14 PM UTC
Duration
2h 8m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags Evaluations
Timeline · 2 updates
  1. identified May 20, 2026, 12:06 PM 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, however existing deployments with custom fields are running without any issues.

  2. resolved May 20, 2026, 02:14 PM UTC

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

Read the full incident report →

Notice May 20, 2026

Incorrect Banner appeared on MarketPlace Apps

Detected by Pingoru
May 20, 2026, 10:16 AM UTC
Resolved
May 20, 2026, 10:16 AM UTC
Duration
Affected: Forge App Alerts
Timeline · 1 update
  1. resolved May 20, 2026, 10:16 AM 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 required, the banner was displayed in error and there is no impact to app functionality or availability. We apologise for any confusion this may have caused.

Read the full incident report →

Critical May 14, 2026

Disrupted Service Desk availability

Detected by Pingoru
May 14, 2026, 09:04 PM UTC
Resolved
May 14, 2026, 09:35 PM UTC
Duration
31m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags Evaluations
Timeline · 3 updates
  1. identified May 14, 2026, 09:04 PM 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 May 14, 2026, 09:20 PM 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 May 14, 2026, 09:35 PM 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.

Read the full incident report →

Critical May 14, 2026

Users experiencing issues accessing multiple Atlassian products

Detected by Pingoru
May 14, 2026, 05:11 AM UTC
Resolved
May 14, 2026, 06:49 AM UTC
Duration
1h 38m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags Evaluations
Timeline · 7 updates
  1. identified May 14, 2026, 05:11 AM 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 May 14, 2026, 05:24 AM 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 continues to investigate the issue with urgency, we will continue to provide further updates here with additional information. We will provide further update within one hour, or sooner as further information becomes available.

  3. identified May 14, 2026, 05:34 AM 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 within an hour as we are able to progress mitigating this issue.

  4. monitoring May 14, 2026, 05:43 AM 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 place.

  5. monitoring May 14, 2026, 06:40 AM 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 validated and the incident is closed.

  6. monitoring May 14, 2026, 06:41 AM 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 validated and the incident is closed.

  7. resolved May 14, 2026, 06:49 AM UTC

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

Read the full incident report →

Minor May 12, 2026

Degraded performance of forge invocations

Detected by Pingoru
May 12, 2026, 03:50 PM UTC
Resolved
May 12, 2026, 05:40 PM UTC
Duration
1h 50m
Affected: Forge Function Invocation
Timeline · 4 updates
  1. identified May 12, 2026, 03:50 PM 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 available.

  2. identified May 12, 2026, 04:57 PM 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 May 12, 2026, 05:17 PM 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 May 12, 2026, 05:40 PM 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.

Read the full incident report →

Minor May 12, 2026

Delay in Jira Webhook Delivery

Detected by Pingoru
May 12, 2026, 02:03 PM UTC
Resolved
May 12, 2026, 06:11 PM UTC
Duration
4h 8m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags Evaluations
Timeline · 5 updates
  1. investigating May 12, 2026, 02:03 PM 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 within the next 1 hour.

  2. investigating May 12, 2026, 03:00 PM UTC

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

  3. identified May 12, 2026, 04:27 PM 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 May 12, 2026, 05:52 PM 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 May 12, 2026, 06:11 PM 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.

Read the full incident report →

Minor May 11, 2026

Delays in Jira Webhook delivery

Detected by Pingoru
May 11, 2026, 02:24 PM UTC
Resolved
May 11, 2026, 06:16 PM UTC
Duration
3h 51m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags Evaluations
Timeline · 6 updates
  1. identified May 11, 2026, 02:24 PM 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. We will continue to monitor and provide updates as the situation progresses.

  2. identified May 11, 2026, 02:48 PM 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 updates.

  3. identified May 11, 2026, 03:45 PM UTC

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

  4. identified May 11, 2026, 04:42 PM 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 May 11, 2026, 06:00 PM 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 May 11, 2026, 06:16 PM 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.

Read the full incident report →

Minor May 8, 2026

Multiple Atlassian services are experiencing issues

Detected by Pingoru
May 08, 2026, 04:10 AM UTC
Resolved
May 08, 2026, 07:45 PM UTC
Duration
15h 35m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags Evaluations
Timeline · 9 updates

Read the full incident report →

Minor May 5, 2026

Degraded performance of Forge trigger

Detected by Pingoru
May 05, 2026, 05:40 PM UTC
Resolved
May 05, 2026, 10:34 PM UTC
Duration
4h 54m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags Evaluations
Timeline · 4 updates
  1. investigating May 05, 2026, 05:40 PM 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 May 05, 2026, 06:58 PM 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 more information is available.

  3. identified May 05, 2026, 08:37 PM 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 information is available.

  4. resolved May 05, 2026, 10:34 PM 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.

Read the full incident report →

Minor April 30, 2026

Delays in Jira webhook delivery

Detected by Pingoru
Apr 30, 2026, 08:59 AM UTC
Resolved
Apr 30, 2026, 02:56 PM UTC
Duration
5h 57m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags Evaluations
Timeline · 4 updates
  1. investigating Apr 30, 2026, 08:59 AM 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 Apr 30, 2026, 10:05 AM 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 Apr 30, 2026, 01:36 PM 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 Apr 30, 2026, 02:56 PM 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.

Read the full incident report →

Major April 22, 2026

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

Detected by Pingoru
Apr 22, 2026, 06:57 AM UTC
Resolved
Apr 23, 2026, 04:14 PM UTC
Duration
1d 9h
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags Evaluations
Timeline · 6 updates
  1. investigating Apr 22, 2026, 06:57 AM 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 429 response will contain the following headers: X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0 Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly. Our teams are investigating this issue with urgency, and we will provide an update within two hours.

  2. identified Apr 22, 2026, 08:53 AM 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 Apr 22, 2026, 04:21 PM 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 Apr 22, 2026, 11:29 PM UTC

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

  5. monitoring Apr 23, 2026, 03:27 PM 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 Apr 23, 2026, 04:14 PM UTC

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

Read the full incident report →

Major April 13, 2026

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

Detected by Pingoru
Apr 13, 2026, 10:58 AM UTC
Resolved
Apr 13, 2026, 03:11 PM UTC
Duration
4h 13m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags Evaluations
Timeline · 3 updates
  1. investigating Apr 13, 2026, 10:58 AM 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 period. We will provide updates as we have more information. We apologize for the inconvenience.

  2. identified Apr 13, 2026, 01:32 PM 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 and will continue to share updates.

  3. resolved Apr 13, 2026, 03:11 PM UTC

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

Read the full incident report →

Critical April 8, 2026

Read/Write logs for Forge Apps down

Detected by Pingoru
Apr 08, 2026, 06:55 AM UTC
Resolved
Apr 08, 2026, 07:45 AM UTC
Duration
50m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags Evaluations
Timeline · 4 updates
  1. investigating Apr 08, 2026, 06:55 AM 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 Apr 08, 2026, 06:55 AM 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 Apr 08, 2026, 07:45 AM 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 Apr 08, 2026, 07:45 AM 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 process, you may temporarily see duplicate log entries; however, this will not result in duplicate usage or additional costs. We will continue to monitor the system closely and provide further updates as needed.

Read the full incident report →

Major April 2, 2026

Disrupted Forge availability

Detected by Pingoru
Apr 02, 2026, 08:46 PM UTC
Resolved
Apr 02, 2026, 10:36 PM UTC
Duration
1h 49m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge Monetisation
Timeline · 2 updates
  1. investigating Apr 02, 2026, 08:46 PM UTC

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

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

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

Read the full incident report →

Major March 24, 2026

Connect Apps Performance Degradation

Detected by Pingoru
Mar 24, 2026, 07:59 AM UTC
Resolved
Mar 24, 2026, 08:44 AM UTC
Duration
45m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge Monetisation
Timeline · 2 updates
  1. identified Mar 24, 2026, 07:59 AM UTC

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

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

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

Read the full incident report →

Major March 17, 2026

Incident impacting Forge app installations and Dev console

Detected by Pingoru
Mar 17, 2026, 10:05 AM UTC
Resolved
Mar 17, 2026, 11:37 AM UTC
Duration
1h 32m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQL
Timeline · 4 updates
  1. investigating Mar 17, 2026, 10:05 AM UTC

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

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

    We are continuing to investigate this issue.

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

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

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

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

Read the full incident report →

Major March 12, 2026

Static macro rendering is failing in Confluence Cloud

Detected by Pingoru
Mar 12, 2026, 11:42 AM UTC
Resolved
Mar 13, 2026, 12:26 AM UTC
Duration
12h 43m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQL
Timeline · 4 updates
  1. investigating Mar 12, 2026, 11:42 AM UTC

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

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

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

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

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

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

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

Read the full incident report →

Minor March 2, 2026

Inaccurate install counts for some Marketplace apps on Marketplace

Detected by Pingoru
Mar 02, 2026, 04:15 PM UTC
Resolved
Mar 04, 2026, 03:04 AM UTC
Duration
1d 10h
Affected: App listingsReporting APIs and dashboardsSearch
Timeline · 3 updates
  1. monitoring Mar 02, 2026, 04:15 PM UTC

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

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

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

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

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

Read the full incident report →

Major February 16, 2026

Forge billing subscriptions cancelled for some apps

Detected by Pingoru
Feb 16, 2026, 11:24 AM UTC
Resolved
Feb 19, 2026, 05:12 PM UTC
Duration
3d 5h
Affected: Developer console
Timeline · 3 updates
  1. investigating Feb 16, 2026, 11:24 AM UTC

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

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

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

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

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

Read the full incident report →