Atlassian Developer Outage History

Started Nov 04, 2026, 10:36 AM UTC· resolved Nov 04, 2026, 11:03 AM UTC

1. investigating Nov 04, 2026, 10:36 AM UTC

   We are investigating an issue where select Marketplace apps are encountering 429 rate limit errors, causing intermittent delays and impacting automated workflows in Jira Cloud. Core Jira functionality remains fully operational. Our teams are actively working on a resolution, and we will share our next update within 1 hour or sooner.

2. resolved Nov 04, 2026, 11:03 AM UTC

   Between 03 November 2026, 19:55 UTC and 04 November 2026, 10:21 UTC, select Marketplace apps encountered 429 rate limit errors, causing intermittent delays for automated workflows in Jira Cloud. The underlying issue has been identified and mitigated, and all affected apps and integrations are functioning normally. If you continue to experience any issues, please reach out to our team at Atlassian Support.

Read the full incident report →

Started Oct 27, 2026, 07:41 AM UTC· resolved Oct 27, 2026, 12:24 PM UTC

1. monitoring Oct 27, 2026, 07:41 AM UTC

   A fix has been implemented to resolve the event delivery delays affecting select Marketplace apps. Systems are recovering and queued events are being delivered normally. We are continuing to monitor telemetry and service stability closely. Our next update will be shared in 6 hours, or sooner.

2. resolved Oct 27, 2026, 12:24 PM UTC

   On October 26th, 2026, between 14:00 UTC and 21:30 UTC, some users and partners may have experienced delays in event and webhook delivery affecting select Marketplace apps across Jira and Confluence. The issue has now been resolved and the service is operating normally for all customers.

Read the full incident report →

Started Oct 15, 2026, 02:22 PM UTC· resolved Oct 15, 2026, 05:08 PM UTC

1. investigating Oct 15, 2026, 02:22 PM 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 in 60 minutes or sooner.

2. monitoring Oct 15, 2026, 03:23 PM 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 environment to ensure full service restoration. We will share our next update in 60 minutes or sooner.

3. monitoring Oct 15, 2026, 04:19 PM 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 Oct 15, 2026, 05:08 PM 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.

Read the full incident report →

Started Oct 01, 2026, 04:03 AM UTC· resolved Oct 01, 2026, 07:51 AM UTC

1. identified Oct 01, 2026, 04:03 AM 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 Oct 01, 2026, 05:00 AM 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 Management is not appearing as expected.

3. identified Oct 01, 2026, 07:01 AM 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 affecting the response times and backlog management of some tickets.

4. resolved Oct 01, 2026, 07:51 AM 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 affected customers. The impact to support tickets with missing SLA component and delayed notifications have also confirmed recovery. Note: For Bitbucket customers, if there was any scheduled pipelines that did not run during the incident window, you may wait for the next scheduled execution or trigger them manually.

5. postmortem Oct 09, 2026, 06:24 PM 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 background tasks, such as email-to-ticket processing and scheduled pipelines; interactive product use was not affected. The event was triggered when an unexpected volume of scheduled tasks became due simultaneously, overwhelming our shared job scheduling platform. Automated monitoring detected the incident within three minutes. Recovery began around 03:45 UTC as engineering scaled capacity and the platform worked through the backlog, with full resolution reached in 6 hours and 25 minutes. ### IMPACT Most scheduled tasks stopped running at 01:00 UTC and resumed from about 03:45 UTC. Most delayed work had caught up by about 06:00 UTC, and the remaining delays had cleared by 07:25 UTC. Across affected products: - Recurring scheduled tasks skipped or delayed runs due during the incident; skipped runs were not automatically re-run, and tasks resumed at their next scheduled time. - Most one-time scheduled tasks ran late; a small number may not have run. - Automation rules, including scheduled rules, ran normally, except as noted below. Bitbucket Cloud Scheduled pipelines due between 01:00 and about 03:50 UTC did not run. If a scheduled pipeline did not run during the incident, you can wait for the next scheduled execution or trigger it manually. Other pipeline runs were not affected. Confluence Some calendar event reminders due between 01:00 and about 03:45 UTC were not sent. Forge apps Scheduled triggers stopped at 01:00 UTC and resumed from about 04:00 UTC; missed invocations were not replayed. Goals Start of the month email reminders to update goals could be delayed. Jira and Jira Service Management Incoming emails stayed in their mailboxes and were processed automatically after recovery. Scheduled notifications, such as filter subscriptions, were delayed. In some service projects, automation rules and notifications triggered by SLAs or time in status ran late. SLA timer data remained intact. Atlassian Support Until 07:25 UTC, issues with our support tools may have slowed some of our responses. Based on our investigation to date, we have not identified any loss of work items, pages, repositories, or incoming emails. ### ROOT CAUSE Our shared job scheduling platform operates at high scale under normal conditions. One of the platform consumers scheduled an abnormally high volume of tasks to be executed at the same time on October 1st at 01:00 UTC. This order-of-magnitude surge exceeded our architectural and scaling limits, creating a processing backlog across dependent services. Engineering manually increased capacity to handle the abnormal load, enabling the service to process the backlog and return to normal operations. ### REMEDIAL ACTIONS PLAN & NEXT STEPS We know that delayed and missed work affects your productivity. We are prioritizing these actions to help reduce the likelihood and impact of similar incidents: - **Enhance workload isolation:** Implement fair scheduling guardrails so volume surges from a single source do not starve or delay tasks across other products. - **Strengthen surge controls:** Add operational capabilities to quickly throttle or pause scheduled workloads from specific sources during unexpected traffic spikes. - **Improve system scaling and recovery:** Enhance platform capacity and optimize scaling processes to handle extreme demand spikes and recover more rapidly. We apologize to customers whose services were impacted during this incident. Thanks, Atlassian

Read the full incident report →

Started Sep 28, 2026, 06:48 AM UTC· resolved Sep 28, 2026, 07:59 AM UTC

1. investigating Sep 28, 2026, 06:48 AM 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 is working to restore the approval flow used by the Marketplace console and is validating the service after redeployment. The issue is being investigated alongside recent changes made in internal support services. Next Steps Next communication will be sent in 60 minutes, or sooner if there is a significant update.

2. resolved Sep 28, 2026, 07:59 AM 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 Marketplace app publishing workflow was impacted due to a service account permission issue that prevented automated ticket creation required for approvals. The necessary permissions have since been restored, and the app publishing and submission flows are now operating normally. Impact Window: Start: 12:30 AM UTC (28 Sep 2026) End: 07:30 AM UTC (28 Sep 2026) Next Steps for Affected Users: If you previously encountered a Version publish failed error, please retry publishing your app version now. If you continue to experience any issues, please reach out to our team at Developer and marketplace support https://developer.atlassian.com/support . Thank you for your patience and understanding while we resolved this issue.

Read the full incident report →

Started Sep 17, 2026, 12:59 PM UTC· resolved Sep 17, 2026, 03:22 PM UTC

1. identified Sep 17, 2026, 12:59 PM 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 display in the Developer Console. We are actively deploying a fix to correct the display. We will provide the next update in 1 - hour or sooner.

2. identified Sep 17, 2026, 01:57 PM 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 Sep 17, 2026, 03:22 PM 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.

Read the full incident report →

Started Sep 02, 2026, 03:09 AM UTC· resolved Sep 02, 2026, 03:17 AM UTC

1. investigating Sep 02, 2026, 03:09 AM 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 Sep 02, 2026, 03:17 AM 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.

Read the full incident report →

Started Aug 25, 2026, 10:58 AM UTC· resolved Aug 25, 2026, 11:11 AM UTC

1. monitoring Aug 25, 2026, 10:58 AM 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 Aug 25, 2026, 11:11 AM 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.

Read the full incident report →

Started Aug 03, 2026, 03:26 AM UTC· resolved Aug 03, 2026, 03:37 AM UTC

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 →

Started Jul 13, 2026, 03:48 PM UTC· resolved Jul 13, 2026, 05:46 PM UTC

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 →

Started Jun 30, 2026, 02:45 AM UTC· resolved Jul 02, 2026, 04:43 AM UTC

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 are taking steps to ensure that impacted customers will be informed. 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 →

Started Jun 26, 2026, 02:32 PM UTC· resolved Jun 26, 2026, 09:39 PM UTC

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 →

Started Jun 10, 2026, 04:55 AM UTC· resolved Jun 10, 2026, 06:31 AM UTC

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 →

Started May 26, 2026, 10:40 AM UTC· resolved May 26, 2026, 01:55 PM UTC

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 →

Started May 20, 2026, 12:06 PM UTC· resolved May 20, 2026, 02:14 PM UTC

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 →

Started May 20, 2026, 10:16 AM UTC· resolved May 20, 2026, 10:16 AM UTC

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 →

Started May 14, 2026, 09:04 PM UTC· resolved May 14, 2026, 09:35 PM UTC

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 →

Started May 14, 2026, 05:11 AM UTC· resolved May 14, 2026, 06:49 AM UTC

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 approaching full system recovery at this time, and are performing final confirmations that services are restored.

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 →

Started May 12, 2026, 03:50 PM UTC· resolved May 12, 2026, 05:40 PM UTC

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 →

Started May 12, 2026, 02:03 PM UTC· resolved May 12, 2026, 06:11 PM UTC

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 →

Started May 11, 2026, 02:24 PM UTC· resolved May 11, 2026, 06:16 PM UTC

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 →

Started May 08, 2026, 04:10 AM UTC· resolved May 08, 2026, 07:45 PM UTC

1. investigating May 08, 2026, 04:10 AM 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 May 08, 2026, 04:10 AM 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 May 08, 2026, 04:10 AM 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 May 08, 2026, 04:10 AM 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 product page.

5. monitoring May 08, 2026, 05:53 AM 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 triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.

6. monitoring May 08, 2026, 08:03 AM 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 May 08, 2026, 11:12 AM 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 apologise for the disruption and thank you for your patience.

8. resolved May 08, 2026, 07:45 PM 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 May 20, 2026, 06:58 AM 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 performance and delays of background operations and automation execution. The incident started on May 8, 2026 at 00:22 and was detected within 4 minutes by automated monitoring systems. Our teams worked to restore core access by 06:08. Final cleanup of backlogged processes and minor issues progressed in stages from there was completed iteratively by 19:15. ### **IMPACT** The primary infrastructure affected in this incident was the event processing pipeline in the prod-east region, which distributes events between Atlassian services and underpins background operations such as automation execution, search indexing, notifications, permission synchronisation. * Between 00:22 and 06:08, an infrastructure incident in our hosting provider triggered an ingestion failure in our event processing pipeline. * At 02:50, event ingestion was failed over to an unaffected availability zone, progressively restoring live event flows. * At 06:08, reliability for new ingestion in prod-east recovered to 100%. The remaining work was to drain the accumulated cross-region backlog of messages, which completed by 17:00. * By 18:48, Automation had processed their backlog of events that were created while processing **Automation** Between 00:22 and 02:50, customers with automation rules triggered by events originating from the prod-east region experienced a significant reduction in rule executions. During this window, event-triggered automation rules were not firing because the events that trigger them were not being delivered. Rule authoring, saving, and rules triggered manually, by schedules, or by webhooks were not affected. At 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of live events to Automation and allowing new event-triggered rules to begin executing normally. However, events generated during the impact window still needed to be replayed before delayed automations could be processed. Beginning at 08:28, upstream services replayed their queued events in a coordinated sequence, and all replayed events were processed by 18:48. During the replay window, customers may have experienced automation rules executing later than expected, a small number of rules reaching daily processing limits due to compressed replay, and time-sensitive rules not completing as expected if internal timeout thresholds were exceeded. **Jira and Jira Service Management** Between 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruption to Jira and Jira Service Management event-driven features like automation, along with a short period of elevated errors during infrastructure failover. Core Jira experiences, including issue view, boards, and project navigation, remained available throughout the incident. Jira event delivery was affected by the primary impact, preventing downstream services from receiving issue lifecycle events. This affected automation rules triggered by Jira events, AI agent orchestration in Jira, notifications for issue updates and transitions, search indexing for newly created or modified issues, and event-driven integrations between Jira and other Atlassian products. At 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of new events. All events generated during the impact window were retained in a recovery queue and required replaying. This began at 08:28 and completed at 12:00. During the replay window, customers may have experienced automation rules executing later than expected, delayed notifications arriving hours after the triggering action, temporary gaps in search results for content created or modified during the impact window, and AI agent workflows not completing as expected where internal timeout thresholds were exceeded. **Confluence** Between 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruptions to event-driven services in Confluence. This resulted in delays to search indexing, notifications, automation rule execution, and permission synchronisation. The underlying event processing infrastructure failed over to an unaffected availability zone, after which live Confluence operations resumed normally. However, events generated during the impact window were queued for replay, and some background services remained delayed until that replay and related validation work completed. Between 10:14 and 17:00, a bulk replay of all the queued tenant replay tasks was completed to restore data consistency. During and immediately after the replay window, customers may have experienced search results not reflecting content created or modified during the outage, delayed or missing notifications for page and comment activity, automation rules firing later than expected, and brief delays in permission synchronisation for tenants relying on incremental identity sync. **Bitbucket and Pipelines** Between 00:22 and 06:08, customers using Bitbucket and Pipelines experienced failures and degraded functionality across event-driven workflows. Core Git operations, including push, pull, and clone, were not affected and continued to operate normally throughout the incident. Automatic pipeline triggers initiated by push or pull request events were unavailable during the impact window. Merge queues, custom merge checks, Forge-based triggers, workspace permission changes, and some workspace provisioning flows were also affected. Customers using merge queues were unable to merge pull requests, and some pipeline steps failed because queued work contributed to elevated concurrency limits. At approximately 03:57, Pipelines was reconfigured to consume events through an alternative path, restoring automatic pipeline triggering. Merge queues, custom merge checks, Forge triggers, and other affected workflows were progressively restored as the underlying event processing infrastructure recovered. All Bitbucket and Pipelines services were confirmed fully operational by 06:08. After recovery, queued events were reviewed and replayed where safe to restore data consistency for billing, audit logging, and other background processes. **Identity Services** Between 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced delays in the propagation of identity and group membership changes to downstream Atlassian products. Core identity operations, including authentication, login, and direct group management actions, were not affected and continued to function normally throughout the incident. The impact was limited to asynchronous, event-driven operations that depend on the event processing pipeline. This included delays in delivering group membership and user profile changes to products such as Jira and Confluence, which affected downstream permission synchronisation and crowd sync flows. A small number of SCIM-based identity synchronisation and site provisioning workflows also experienced temporary delays. After the event processing infrastructure recovered, backed-up identity and group directory events were replayed where required, restoring downstream consistency for affected products. No identity data was lost. Group membership changes, user profile updates, and provisioning-related events that occurred during the impact window were retained and processed after recovery. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know outages impact your productivity. While our monitoring and recovery processes helped us respond quickly, this incident highlighted opportunities to further strengthen resilience for event-driven services. We are prioritizing improvements that will: * **Enhance failover coverage** so critical event processing can recover more smoothly during infrastructure disruptions. * **Strengthen recovery handling** so replayed events can be processed more quickly. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support.

Read the full incident report →

Started May 05, 2026, 05:40 PM UTC· resolved May 05, 2026, 10:34 PM UTC

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 →

Started Apr 30, 2026, 08:59 AM UTC· resolved Apr 30, 2026, 02:56 PM UTC

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 →

Started Apr 28, 2026, 06:28 PM UTC· resolved Apr 28, 2026, 09:50 PM UTC

1. investigating Apr 28, 2026, 06:28 PM 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 Apr 28, 2026, 06:34 PM 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 Apr 28, 2026, 08:16 PM 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 available.

4. monitoring Apr 28, 2026, 09:34 PM 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 Apr 28, 2026, 09:50 PM UTC

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

Read the full incident report →