Atlassian Developer Outage History

Multiple Atlassian services experienced elevated error rates and degraded performance for 15.6 hours due to an infrastructure outage from their public cloud provider, affecting authentication, APIs, app management, marketplace functions, and various developer tools. The incident impacted asynchronous event processing, causing issues with notifications, automation triggers, and data syncs across Jira Cloud, Confluence Cloud, Bitbucket Cloud, and other Atlassian products. The underlying infrastructure issue was mitigated and services were restored, with teams working to clear the backlog of queued events that accumulated during the outage.

Atlassian Developer experienced degraded performance affecting Forge webhook delivery in the US East region for 5 hours on May 5, 2026. Users experienced delays in webhook delivery during this period. The issue was identified and resolved, with service returning to normal operation for all affected customers.

Atlassian Developer experienced a 6-hour incident where customers encountered intermittent delays in Jira webhook delivery, affecting multiple components including APIs, authentication, app management, and marketplace services. The engineering team identified the root cause as a resource constraint in their systems and deployed a fix to resolve the delivery delays. Webhook delivery returned to normal operation after the fix was implemented and monitored for stability.

Atlassian Developer experienced performance degradation affecting Forge webhook delivery and triggers in the prod-euwest region for 3.4 hours. The incident impacted multiple components including authentication, app deployment, Bitbucket and Confluence Cloud APIs, Jira Cloud APIs, webhooks, and various marketplace services. The issue was identified and resolved through mitigation efforts, with services returning to normal operation.

Some Forge apps experienced increased 429 "Too Many Requests" errors when calling Jira REST APIs, causing disruption for end users of affected applications. The issue was caused by gateway-level rate limiting that prevented apps from making successful API calls, while Confluence APIs remained unaffected. Atlassian resolved the incident after 33.3 hours by implementing initial remediation through increased rate limits, followed by additional mitigations that restored normal service operations.

Atlassian Developer experienced a major incident where Marketplace transaction data was missing from partner reports starting April 10, 2026, affecting the Reporting APIs and dashboards for 4.3 hours. Partners were unable to access transaction records for their Marketplace apps during this period. The issue was resolved on April 13th with transaction information restored to partner reports, though a temporary 3-hour delay for new transactions remained while the service fully normalized.

The Forge App logs experience failed, preventing Forge Ecosystem Cloud developers and vendors from accessing read/write functionality for their application logs. The incident lasted 52 minutes before all log search and ingestion services were restored. Teams continued monitoring and worked to restore visibility for logs that were impacted during the outage period.

Atlassian Developer experienced a partial service disruption affecting Forge Remote applications that integrate with JIRA, specifically impacting Forge Function Invocation. The incident lasted 1.9 hours before being resolved, with service returning to normal operation for all affected customers.

Connect Apps experienced performance degradation for 4 hours and 26 minutes on March 24, 2026, affecting Confluence Cloud APIs, app management, webhooks, and web triggers. The incident impacted Connect API functionality, causing degraded performance for applications relying on these services. Atlassian identified the root cause and deployed a fix, fully resolving the issue and restoring normal service operations.

Atlassian Developer experienced a service disruption on March 17th, 2026 from 9:05 AM to 11:10 AM UTC affecting Forge app management and developer tooling. Users encountered errors when installing, upgrading, or deploying Forge apps, using app tunneling, and accessing the Developer Console, while some app platform capabilities including data residency operations and Rovo MCP consent flows were also impacted. The issue was resolved after 1.6 hours with existing Forge apps continuing to run normally throughout the incident.