Atlassian Developer Status Page

Oct 1, 2026 · resolved Oct 1

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

Sep 28, 2026 · resolved Sep 28

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.

Sep 27, 2026 · resolved Sep 28

Update: Migration Postponed During our scheduled migration over the weekend, we encountered an unexpected issue and made the decision to roll back and postpone the transition at this time. What you need to know - Continue using the current portal: Please continue submitting tickets via https://developer.atlassian.com/support and managing existing ECOHELP tickets. - No impact to active tickets or SLAs: All existing tickets remain active and uninterrupted in the current portal, and our support team is operating as usual. - Rescheduled date: We are working through the root cause and will provide an updated migration timeline well in advance of our next attempt. For more information: https://community.developer.atlassian.com/t/changes-to-developer-and-marketplace-support-new-platform-experience/102859 Thank you for your patience and understanding.

Sep 17, 2026 · resolved Sep 17

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.

Sep 2, 2026 · resolved Sep 2

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.

Is Atlassian Developer down right now?

No — Atlassian Developer is up. All systems operational as of Oct 12, 4:50 AM UTC.

What is Atlassian Developer's current status?

Atlassian Developer: All Systems Operational. Alert24 checks Atlassian Developer's status page continuously and can notify you the moment it changes.

How do I get alerted when Atlassian Developer goes down?

Alert24 monitors Atlassian Developer and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.