Atlassian outage history

Users of the Atlassian Developer Console were affected by a display discrepancy on the Installations tab, with app versions and statuses shown as outdated. The problem did not impact core installation operations or automatic upgrades, which continued to function in the background. The impact was primarily visibility of installation data rather than a loss of functionality.

The incident began at 1:00 PM UTC, and engineers began deploying a fix to correct the UI. Ongoing updates over the following days indicated the fix was being refined and that related components (Statuspage and Atlassian Developers) were cycling between degraded and normal states as the fix rolled out. By 3:46 PM UTC, status entries show the affected components returning to up, suggesting the issue had been resolved.

There was only a single user report logged during the period, indicating limited external visibility.

Users attempting Bitbucket Pipelines faced delays and stuck builds starting around 9:35 AM UTC. Atlassian identified the underlying cause and recovery began, with normal queue processing returning by 10:21 AM UTC. The incident mainly disrupted CI workflows in Bitbucket Pipelines, causing slowed or stalled builds for affected projects.

Separately, the Developer Console showed a display discrepancy on the Installations page, where app versions and statuses appeared outdated. The issue began at 1:00 PM UTC and progressed through the afternoon, with a fix in progress and a full recovery by 3:25 PM UTC. Core app installations and upgrades continued to function in the background; the problem was isolated to the UI.

On Sept 22, Statuspage experienced a brief period of instability around 12:00 AM UTC, recovering by 12:30 AM UTC. An additional update later noted Atlassian Support services returning to normal by 3:46 PM UTC. In addition, a single Knoxville user report logged at 5:13 PM UTC described AE crashes in the morning, providing context but not indicating a widespread outage. Overall, the issues were limited in scope and resolved over the period.

An outage affected Opsgenie and Jira Service Management, marking a major disruption for Atlassian customers. The disruption began around 4:51 PM UTC, with on-call and incident-management workflows impacted as Jira Service Management and Opsgenie reported outages. After about an hour, updates indicated the issue was resolved and services were operating normally again, with ongoing monitoring to confirm stability by 5:30 PM UTC.

Over the next days, additional, separate issues affected Atlassian services. Bitbucket Pipelines Execution experienced delays starting around 9:35 AM UTC, with recovery underway and confirmed by 10:21 AM UTC. A separate Developer Console issue caused a display discrepancy on the Installations page starting around 1:00 PM UTC, with a fix in progress and further updates to follow. The period culminated in broader recovery across Atlassian services, with Statuspage and underlying systems returning to normal by Sep 22, 2026 3:46 PM UTC. User reports during this time were limited, indicating no widespread user outages beyond the main incident.

Users on Jira Software and Jira Service Management experienced degraded performance, with errors and delays when loading issue views and viewing boards. The degradation began at 7:50 AM UTC and was resolved by 8:15 AM UTC. A mitigation was deployed around 8:10 AM UTC, and Atlassian engineers monitored the environment as stability returned.

Users experienced intermittent reliability issues with Bitbucket Cloud starting around 6:35 AM UTC, with pages failing to load, timeouts, or endless spinning for some actions. Pull requests, commits view, related Bitbucket pages, and Pipelines activity were affected, disrupting development workflows for teams.

The incident also impacted Jira Software and Jira Service Management with degraded performance and delays loading issue views and boards, beginning around 7:50 AM UTC. A mitigation was deployed and recovery began; Bitbucket had already moved back to stable by 8:05 AM UTC, and Jira services continued to stabilize, with Jira Service Management returning to normal by 8:15 AM UTC. Overall, service health improved through the morning as fixes were applied and monitoring continued.

Users in the US East region experienced a Jira outage affecting project tracking and issue management. The incident began at 4:00 PM UTC when Jira became unavailable, disrupting typical workflows for teams relying on Jira in that region. A brief disruption to Jira Service Management appeared around 4:20 PM UTC before the overall Jira services were restored.

Jira Service Management showed a partial improvement around 4:20 PM UTC while the main Jira service remained down, and full recovery occurred by 4:40 PM UTC. The disruption was regional rather than global, with services returning to normal as the incident resolved.

Users in the US East region began experiencing degraded Jira Service Management performance around 2:25 PM UTC, with errors or slowness when viewing or interacting with the Affected Services field. Atlassian stated the issue and began investigating, with the root cause identified and a fix deployed by 3:25 PM UTC and recovery expected shortly.

The issue then escalated to a regional disruption affecting Jira availability in US East, beginning at 4:00 PM UTC. The Jira Service Management component moved to a degraded/down state during the outage, and by 4:40 PM UTC the Jira component had returned to up and services were restored. The regionally scoped outage lasted roughly forty minutes.

On Sep 1, 2026 5:10 PM UTC, Atlassian Jira began experiencing degraded performance, with forms functionality affected and users reporting slow or failing form submissions. The incident progressed toward mitigation, and Jira services were reported as operating normally again by 9:25 PM UTC.

Shortly after Jira was restored, a separate issue impacted Microsoft Teams notifications for Opsgenie customers. The status page documented ongoing mitigation with updates around 9:36 PM UTC and continued notices through 3:15 AM UTC and 3:20 AM UTC. The notification delivery problems extended into the early hours of 6:10 AM UTC, at which point Opsgenie-related components were back to normal and monitoring continued to confirm stability.

An Atlassian incident began with Jira Work Item transitions failing, impacting Jira Work Management and Jira users who could not move issues. The issue started at 9:15 AM UTC and the root cause was identified with a fix applied, with signs of recovery for Jira services by 10:15 AM UTC. Later that day, Jira forms functionality also showed degraded performance beginning around 5:10 PM UTC, with a broader recovery for Jira reported by 9:25 PM UTC. In parallel, there were separate disruptions to Microsoft Teams notification delivery for Opsgenie customers, first observed at 11:50 AM UTC and continuing through subsequent updates.

The incident extended to Opsgenie-related notifications, with recurring issues noted at 9:36 PM UTC and again on 3:15 AM UTC/ 3:20 AM UTC, before components returned to normal later on 6:10 AM UTC. Overall, users experienced partial Jira outages and degraded performance, along with intermittent notification delivery problems for Opsgenie customers. The situation was monitored and brought toward stability across the affected services over the period.

Jira email-based item creation and updates were disrupted starting around 6:30 PM UTC as Atlassian reported issues with fetching mails from Microsoft accounts. The problem prevented or slowed email-based Jira item creation and updates, with 500-level errors observed during mail fetch attempts. The impact spread to Jira and Jira Work Management capabilities that rely on incoming mail, affecting workflows that depend on email-triggered actions.

On 10:15 AM UTC, Atlassian identified the root cause of Jira Work Item transitions and rolled out a fix, with signs of recovery. However, Jira forms and item transitions continued to show degraded performance through the day, and services began returning to normal only after further mitigation, with Jira operating normally for affected customers by 9:25 PM UTC. Separately, delivery of Microsoft Teams notifications for Opsgenie customers experienced ongoing issues, with additional updates through the day and into the next, before Opsgenie components stabilized by 6:10 AM UTC.