Atlassian Compass incident

Intermittent failure in Forge app invocation

Major Resolved View vendor source →

Atlassian Compass experienced a major incident on July 10, 2025 affecting GraphQL and Bitbucket and 1 more component, lasting 22m. The incident has been resolved; the full update timeline is below.

Started
Jul 10, 2025, 08:32 AM UTC
Resolved
Jul 10, 2025, 08:55 AM UTC
Duration
22m
Detected by Pingoru
Jul 10, 2025, 08:32 AM UTC

Affected components

GraphQLBitbucketWebhooksComponent TemplatesScorecardsGitHub API RequestsOn-call flowsRESTComponentsAuthentication and User Management

Update timeline

  1. monitoring Jul 10, 2025, 08:32 AM UTC

    We are investigating reports of intermittent errors for some Confluence, Jira Work Management, Jira Service Management, Jira, and Compass Cloud customers failing invocation, mostly scheduled triggers and smart links from 5:44 am UTC to 7:44 am UTC. We have put mitigations in place, and the errors have receded. We are monitoring the incident resolution. Customers will sometimes see errors in app functionality during this time and scheduled triggers might not work. We have replayed the scheduled triggers.

  2. resolved Jul 10, 2025, 08:55 AM UTC

    Between 10th July 5:44 am UTC to 7:44 am UTC, we experienced intermittent failure in some app funstionality(smart links, scheduled triggers) for Confluence, Jira Work Management, Jira Service Management, Jira, and Compass. The issue has been resolved and the service is operating normally. All scheduled triggers has been replayed.