Atlassian outage history

Users attempting to access Atlassian Jira and Jira Service Management experienced an outage affecting access and performance. Impact began at 11:35 AM UTC and lasted about 50 minutes, with Jira and Jira Service Management temporarily unavailable before service was restored at 12:25 PM UTC.

Atlassian's status page described an initial investigation into performance and access issues and indicated ongoing work to identify and resolve the underlying cause, followed by confirmation that the affected components were back online.

Atlassian Jira experienced a brief degraded performance affecting Jira and associated products, with users reporting errors when viewing issues and boards. The affected components included Jira, Jira Service Management, and Jira Work Management.

The degradation began at 1:25 AM UTC and was resolved by 1:40 AM UTC, lasting about 15 minutes. Atlassian's status updates indicated ongoing investigation and eventual restoration, and users should now see normal operation across the Jira family.

Atlassian conducted a scheduled maintenance window affecting the Atlassian Developers component. The maintenance began at 4:00 AM UTC and lasted roughly three hours, concluding at 7:00 AM UTC. During the window, the Atlassian Developers component was moved into maintenance and later returned to normal operation, with status updates indicating the transition back to up. The maintenance was planned, resulting in a brief disruption followed by a prompt recovery for users relying on Atlassian Developers features.

Atlassian reported a partial outage affecting the installation, uninstallation, and management of Forge and OAuth 2.0 integrated apps. Users attempting to add, remove, or configure Forge or OAuth-enabled apps could experience failures during the impact window. Apps that were already installed were expected to continue running normally. The impact began at 1:47 AM UTC and was resolved by 2:29 AM UTC after Atlassian indicated the issue had been rectified and monitoring was underway. The Atlassian Developers component briefly faced impact before services returned to normal.

Atlassian reported a partial outage affecting voice call notifications for a small subset of Jira Service Management and Opsgenie customers using India-based mobile numbers. Affected users may have seen failed voice call logs and did not receive the expected paging alert. The issue began at 7:00 AM UTC and was resolved by 1:10 PM UTC. Status updates indicated a third-party notification provider was actively working to restore delivery.

The disruption was limited to India-based numbers, with other notification channels remaining unaffected. Jira Service Management and Opsgenie returned to normal after the provider's remediation, per the final updates.

Users of Jira and Jira Service Management faced delays in automation rule executions, disrupting workflows and automated processes. The impact began at 8:20 PM UTC and persisted as Atlassian investigated. The status updates described degraded performance for Jira Automation rules, affecting Jira and Jira Service Management. On Jul 21, 2026 4:55 AM UTC the team identified a root cause and began enacting scaling changes to stabilize performance, with monitoring planned for the next 24 hours.

By 1:00 AM UTC services had returned to normal operation.

Users experienced degraded performance in Jira Automation rule executions during a brief Atlassian incident, affecting Jira and Jira Service Management automation tasks. The issue began at 5:25 PM UTC and was resolved by 5:31 PM UTC, after Atlassian identified a likely cause and implemented a mitigation. The affected automation tasks returned to normal soon after, and no broader service outages were reported.

Users experienced degraded performance in Jira Automation rules affecting automation for Jira and Jira Service Management. The issue began at 4:05 PM UTC and persisted into the evening, with automation rule executions slowed and occasionally failing to trigger as expected, impacting workflows that rely on automation across Jira and Jira Service Management.

Status updates indicated ongoing investigation and a mitigation effort, with signs of improvement as the incident progressed. The Jira component moved from degraded to up at 5:25 PM UTC and Jira Service Management followed at 5:31 PM UTC, with full restoration across affected automation features by 5:31 PM UTC.

An incident affected the Atlassian Statuspage component, with visibility to status information potentially impacted. The degraded state began at 8:51 AM UTC and lasted for about 3 hours and 40 minutes, until 12:31 PM UTC when the component returned to normal operation. During this period, the Statuspage entry transitioned from up to warn and then back to up, indicating a temporary degradation that was resolved by 12:31 PM UTC.

On Jul 13, 2026 3:50 PM UTC, Atlassian reported an outage in Marketplace partner operations, rendering partner pages unavailable and causing dashboards and management interfaces to time out for partners. All partner-related functionality was affected while an investigation got underway, with next communications planned in about 60 minutes or upon progress.

By 5:21 PM UTC, the issue was resolved and Atlassian Developers moved from warn to up, restoring access to partner pages, dashboards, and management interfaces. The outage lasted roughly one and a half hours.