Atlassian Outage History

The Atlassian status pages experienced an outage beginning Feb 10, 2026 1:36 AM UTC, during which public incident communications were unavailable. A user in Atlanta reported that the status pages were down and looked unusual at 9:43 PM UTC UTC. The problem prevented users from reliably checking service status across Atlassian cloud products during this period.

The status page returned to an operational state on Feb 11, 2026 11:35 AM UTC. The outage lasted approximately 34 hours. The Atlassian status page shows two status transitions in the incident timeline (down followed by up). External reports were limited (1), indicating a limited external impact while the service was inaccessible to some users during this window.

The outage began on 3:17 PM UTC and was resolved by 11:26 PM UTC, lasting 8 hours 9 minutes. During the incident, Atlassian's status page listed the affected services as down and later returned to up as services came back online, with two official updates posted as the outage progressed toward restoration.

The Atlassian cloud services experienced an outage beginning at Feb 8, 2026 11:51 PM UTC and ending at Feb 9, 2026 1:26 AM UTC. The incident disrupted access to Atlassian cloud tooling for about 1 hour 35 minutes.

On the Atlassian status page, the outage was shown as a down state during the affected period, followed by a return to up. The page logged two official status updates as the incident progressed.

The Atlassian status page indicated a brief outage across Atlassian cloud services from Feb 8, 2026 12:21 AM UTC to Feb 8, 2026 1:05 AM UTC, with service restored after 44 minutes. Users attempting to access Atlassian cloud products may have experienced interruptions during the window.

The provider published 2 status updates documenting the outage and restoration of services.

An outage affected Atlassian services beginning at 1:41 PM UTC and concluding at 4:31 PM UTC for a duration of about 2 hours and 50 minutes. The disruption briefly made Atlassian products unavailable for users during that window. The Atlassian status page issued two updates as the incident progressed and confirmed restoration at 4:31 PM UTC.

Atlassian experienced a brief outage that caused temporary unavailability of its services. The outage began on Feb 6, 2026 2:22 PM UTC and was resolved by Feb 6, 2026 2:46 PM UTC, lasting about 24 minutes. The Atlassian status page published two updates during the incident detailing the disruption and the subsequent restoration of services.

Atlassian's Statuspage service experienced an outage that disrupted access to status information for Atlassian products. The incident began with a degraded notice at Feb 4, 2026 11:31 AM UTC and escalated to a full outage of the Statuspage component at Feb 4, 2026 6:26 PM UTC. The issue was resolved by Feb 5, 2026 12:11 PM UTC, lasting approximately 17 hours and 45 minutes. During this period, users could not reliably view incident updates or service status on Atlassian's status page.

Atlassian Cloud services experienced a brief degraded period beginning at Feb 3, 2026 7:22 PM UTC and was restored by Feb 4, 2026 5:36 AM UTC. The outage lasted about 10 hours and 14 minutes, during which users may have encountered slower performance or intermittent access to Atlassian Cloud products.

Atlassian's status page documented the transition from degraded condition to full recovery, providing updates as the incident progressed. The incident was contained within the stated window with no indicated ongoing impact afterward.

The Atlassian Jira suite experienced degraded performance affecting Jira, Jira Service Management, Jira Product Discovery, and Atlassian Developers. The degradation began at 5:36 PM UTC when Atlassian Developers entered a degraded state, followed by Jira and related products showing degraded operation over the next hour. Users likely faced slower responses, intermittent access, and sporadic errors when using Jira and related tools. The incident lasted until 7:50 PM UTC when services appeared to return to normal. The Atlassian status page issued 6 updates during the incident to communicate progress and resolution.

From 5:36 PM UTC, Atlassian Developers entered a degraded state, followed by Jira and Jira Product Discovery entering degraded status by 6:15 PM UTC and Jira Service Management by 6:20 PM UTC. A user reported Jira issues earlier at 5:03 PM UTC from Englewood, Colorado: "Jira not working". The outage affected Jira workflows, including issue tracking, project planning, and service-management related operations across teams. The incident impacted four components: Jira, Jira Service Management, Jira Product Discovery, and Atlassian Developers.

Recovery progressed as components returned to normal over the following times: Atlassian Developers by 7:06 PM UTC, Jira Product Discovery and Jira Service Management by 7:46 PM UTC and Jira by 7:50 PM UTC. The incident was resolved as services returned to full operation, with status updates issued as components moved from warn to up.