Atlassian outage history

An incident briefly impacted Atlassian's Statuspage service, with the Statuspage component listed as degraded starting at 11:30 PM UTC and returning to normal by 1:16 AM UTC. The window represents a brief degradation of the status page itself, which could have affected visibility of ongoing incident updates for a short period before full restoration. The transitions show the Statuspage component moving from up to a degraded state and then back to up, with users potentially experiencing intermittent gaps in status visibility during that time.

Select Marketplace apps used with Jira Cloud encountered 429 rate limit errors, causing intermittent delays in automated workflows. Core Jira functionality remained available, but users experienced slower or stalled automation tied to Marketplace integrations. The incident began at 10:40 AM UTC and was resolved by 11:06 AM UTC, with Atlassian indicating that teams were actively investigating and would provide an update within about an hour. The issue appeared confined to Marketplace app integrations, with no broader Jira components affected.

Users across Jira Work Items, Jira Product Discovery, Jira Service Management, and Jira Work Management experienced missing fields, disrupting searching and automations. The impact began at 12:15 AM UTC and persisted for about 25 minutes before a resolution. A configuration change was identified as the likely cause and was reverted by 12:30 AM UTC, with recovery visible across impacted operations. All services returned to normal by 12:40 AM UTC.

Users in the Atlassian ecosystem experienced delays delivering webhooks and app events, impacting a subset of Marketplace apps. The issue began at 7:45 AM UTC and a fix was implemented to resolve the event delivery delays; systems are recovering and queued events are being delivered normally. The problem appeared to be isolated to Atlassian Developers and did not indicate a full service outage, with recovery underway as telemetry showed improvement.

User workflows relying on Atlassian’s Rovo MCP Server connections began experiencing degraded performance and intermittent errors around 2:45 PM UTC. Reports described slow responses and occasional connection failures, impacting processes that depend on the MCP channel. Atlassian’s status page noted a Degraded Performance and Intermittent Errors state and indicated telemetry was being analyzed to implement a mitigation, with updates shared as more details emerged.

Engineers continued investigation and later identified a likely cause while applying mitigation. By 6:05 PM UTC, the Rovo MCP service returned to normal and the incident was marked as resolved on the status page. While impact during the window varied, the service disruption was contained and users began to see normal performance as the mitigation took effect.

Users on Atlassian's Bitbucket experienced a brief outage starting at 5:26 PM UTC, when Bitbucket became unavailable. Atlassian acknowledged the disruption and began investigating as the Bitbucket component entered a down state. By 5:55 PM UTC Bitbucket services were restored for all affected customers, with the component returning to normal operation.

A separate issue affected Rovo MCP with degraded performance beginning at 6:05 PM UTC; a fix deployment was in progress and improvements were observed as error rates declined. By 6:20 PM UTC Rovo MCP had recovered and Atlassian continued monitoring to confirm stability.

Impact began at Oct 21, 2026 3:35 PM UTC when Jira Project Sidebar Loading Degradation was first observed, with mitigations in place and Jira Cloud navigation starting to recover. From 3:50 PM UTC onward, Rovo MCP experienced degraded performance, including timeouts for certain operations; a fix deployment was in progress and improvements were observed over the next hours, with final recovery by 6:20 PM UTC. Around 5:26 PM UTC, Bitbucket availability was disrupted and then recovered by 5:55 PM UTC. The incident produced a mix of degraded Jira navigation, intermittent Rovo MCP performance, and brief Bitbucket disruption, with services returning to normal as updates progressed.

Atlassian's Jira Cloud experienced a brief degradation affecting project navigation as the project sidebar loaded slowly or became unavailable, causing timeouts and missing menus when opening project views. The impact spanned Jira Cloud services including Jira, Jira Service Management, Jira Work Management, and Jira Product Discovery. The issue began at 2:32 PM UTC and lasted about 33 minutes, with users across projects affected until the service recovered by 3:05 PM UTC.

Bitbucket was placed in maintenance for a short window, during which Bitbucket operations could be briefly unavailable. The maintenance began at 4:00 PM UTC and concluded at 4:30 PM UTC, lasting about thirty minutes. Other Atlassian services were not affected. The status updates show Bitbucket entering maintenance and then returning to normal as the window closed.

Users across Atlassian cloud products experienced intermittent errors and delays with Marketplace apps, particularly affecting webhook delivery. The issue impacted the Atlassian Developers component and manifested as unreliable webhook functionality for a subset of apps, starting at Oct 15, 2026 2:25 PM UTC.

Status page updates indicated ongoing investigation, and by 3:25 PM UTC the issue was resolved with the Atlassian Developers component returning to baseline. The incident lasted roughly an hour, affecting a subset of Marketplace apps and their webhook functionality.