Is Atlassian Developer down?

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.