Atlassian Outage History

From 2:46 PM UTC to 5:01 PM UTC, Atlassian experienced a brief degraded performance across its services, with a status transition from up to warn and back to up. Users may have faced slower response times or intermittent access during this window. The incident lasted about two hours and fifteen minutes before services returned to normal. The Atlassian status page posted two updates during the incident, documenting the progression and recovery.

Atlassian Cloud faced a brief period of degraded performance starting at 11:02 PM UTC and resolved by 12:27 AM UTC, lasting roughly 1 hour and 25 minutes. Users attempting to access Atlassian Cloud products may have encountered slower responses or intermittent connectivity during this window. The Atlassian status page indicated a degraded state before services returned to normal shortly after, marking a brief disruption.

The Atlassian cloud experienced a period of degraded performance affecting users of Atlassian cloud products. The issue began at Feb 16, 2026 6:51 AM UTC when the status page listed a degraded state and was resolved by Feb 16, 2026 8:56 AM UTC, for a total duration of approximately 2 hours and 5 minutes. During the window, users may have encountered slower responses and intermittent access across Atlassian services. The issue was acknowledged and tracked on Atlassian's status page as it unfolded. Atlassian later confirmed restoration to normal status on the page.

Atlassian experienced a brief degradation starting at 12:39 PM UTC, with the status page expanding from up to warn, and then returning to up at 1:04 PM UTC. The incident lasted approximately 25 minutes and affected Atlassian services during that window. The provider communicated via the status page, noting a temporary degradation and restoration to normal service after the brief incident.

Atlassian experienced a brief degraded performance starting at 12:02 PM UTC and was restored by 12:33 PM UTC, lasting 31 minutes. The Atlassian status page showed the incident as degraded before returning to full operation, with a short update confirming recovery. The event impacted Atlassian cloud services during the window and is now resolved per the status page.

Atlassian experienced a brief degradation across its services. The status page moved from Up to Degraded (Warn) at 12:57 AM UTC, with users potentially experiencing slower performance or intermittent access during the event. The outage lasted roughly 2 hours and 49 minutes, ending with a return to normal by 3:46 AM UTC.

Atlassian experienced a brief degradation in services, with the status page showing a transition from up to a degraded state at Feb 14, 2026 12:27 PM UTC and back to normal by Feb 14, 2026 12:36 PM UTC. The incident lasted about 9 minutes, during which users may have faced intermittent performance issues. Atlassian issued a warning during the window and subsequently restored full functionality; no further details on the root cause or affected components were provided in the updates available.

The Atlassian status page indicated a brief period of degraded performance beginning at 9:37 AM UTC and ending at 10:21 AM UTC, for a total duration of about 44 minutes. The incident started with Atlassian entering a degraded state (warn) and subsequently returned to normal. The status page reflected the transition from up to warn and back to up as the incident progressed.

An outage began for Atlassian services on Feb 13, 2026 6:46 AM UTC, with Rovo Dev temporarily down. By 7:00 AM UTC the issue remained, and at 7:46 AM UTC Atlassian Developers was listed as degraded (warn) while other components were recovering. The service returned to normal by 8:17 AM UTC.

Atlassian experienced a cloud services outage lasting about 11 hours, with users unable to access Atlassian cloud products during the window. The outage began on 3:46 PM UTC and was resolved by 2:46 AM UTC.

The Atlassian status page tracked the incident from an initial outage to restoration, but detailed information on the root cause or affected components was not provided in the updates. The outage timeline included a transition from up to down and back to up.