Atlassian Compass had 29 outages in the last 2 years totaling 207h 8m of downtime — averaging 1.2 incidents per month.
There were 29 Atlassian Compass outages since June 3, 2024 totaling 207h 8m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are observing delays in Opsgenie, JSM ops and Compass ops notification flows. No alert has been lost and our team is actively working on it to mitigate the delays. We'll keep you posted with further updates.
We continue to work on resolving the notification delays for Jira Service Management, Opsgenie, and Compass. We have identified the root cause and expect recovery shortly.
We have identified the root cause of the notification delay for Opsgenie, JSM Ops and Compass Ops and have mitigated the problem. We are now monitoring closely.
Between 13:10 UTC to 14:00 UTC, we experienced notification delay for Jira Service Management, Opsgenie, and Compass in only EU-region. The issue has been resolved and the service is operating normally.
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.
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.
This incident has been resolved.
We were experiencing cases of degraded performance for outgoing emails from Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas and Compass Cloud customers. The system is recovering and mail is being processed normally as of 16:45 UTC. We will continue to monitor system performance and will provide more details within the next hour.
Between 2025-06-04 14:11 UTC to 20:18 UTC, we experienced delays in delivering emails for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Compass. The issue has been resolved and the service is operating normally.
We are currently investigating an issue impacting both the Compass UI and APIs. We are investigating this issue and will share an update once we have additional information.
The issue has been identified and a fix is being implemented. We have put some mitigation mechanisms in place and our systems are starting to recover.
We have verified that the incident has been resolved.
We are aware of an issue where users of GitHub for Jira connector may be missing pull requests and experiencing other data pipeline issues. Our team is looking into this with urgency and an update will be provided when available.
Our team has identified the root cause of this issue and have reverted the change that was causing these data processing errors. All new updates from GitHub should now be flowing correctly. We are actively working to address a potential data gap for previously impacted events, and will provide an update when available.
Processing of previously impacted events is now underway. An update will be provided when these operations have been completed and historical processing has been completed.
Existing events are continuing to be processed. Any updates to existing entities such as pull requests will also correct and update the data here as required. If there are any concerns about impact to your site with this connector please reach out to support and the team will address your concerns as soon as possible.
We're seeing a recurrence of the earlier issue around components not showing up in our search indexing. We're working on restoring the service.
We've implemented a fix for this issue and are seeing systems recover. We will keep monitoring to make sure we don't see a recurrence of this issue.
This incident has been resolved.
We are currently experiencing partial unavailability in managing Forge apps on different Atlassian platforms. Such as apps lifecycle (installation, removals), developer console usage (including tunnelling), and the creation and deployment of Forge apps. Our team is working diligently to resolve this issue and restore services quickly. We are in the process of identifying the root cause and implementing the necessary fixes. Next updates in 1 hour.
We are currently experiencing partial unavailability in managing Forge apps on different Atlassian platforms, such as apps lifecycle (installation, removals), developer console usage (including tunneling), and the creation and deployment of Forge apps. We have identified the root cause and are in the process of mitigating the impact. We'll keep you posted with further updates. Next updates in 1 hour.
The issues causing the unavailability of related Forge apps capabilities on multiple Atlassian platforms have been resolved, and services are now operating normally for all impacted customers. We will continue to closely monitor for stability.
Between 10:55 AM UTC to 13:15 PM UTC on April 28, 2025, we experienced partial unavailability in managing Forge apps; Such as lifecycle developer console usage, and the creation and deployment of Forge apps for Atlassian Partners, Jira Work Management, Jira, Atlassian Developer, Jira Product Discovery, Compass, and Atlassian Migrations. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The conditions that cause the bug have been addressed and we're actively working on a permanent fix. The issue has been resolved and the service is operating normally.
We are investigating cases of errors for some users creating new sites. We will provide more details within the next hour.
On March 14th, 2025, between 09:00 and 19:14 UTC, some customers experienced issues creating new sites. The errors occurring for some users during new site creation should now be resolved.
We are aware that some users of Confluence and Compass are currently experiencing errors when attempting to search. Our team is investigating this issue with urgency and will provide an update when available.
Issues causing error messages when users were attempting to search within Confluence and Compass should now be resolved. Our team is monitoring ongoing performance at this time.
Searches within Confluence and Compass should now be operating as normal. This issue will now be resolved.
We are investigating reports of the Operations page not loading for Compass Cloud customers. There is no impact to the API. We have identified the issue and are in the process of fixing it.
The issue has been resolved and the service is operating normally.
Compass customers using Github may have experienced intermittent problems in receiving events or leveraging features such as "config-as-code", this was due to an outage on Github
Compass customers using Gitlab may have experienced intermittent problems in receiving events or leveraging features such as "config-as-code", this was due to an outage on Gitlab.
Bitbucket Cloud is experiencing a major outage: https://bitbucket.status.atlassian.com/ . Compass cannot setup new integrations with BBC and is not able to process updates. Events and metrics that have already been synced from Bitbucket to Compass are not impacted.
We have verified that the Bitbucket integration is now working as expected. Marking this incident as Resolved.
We're seeing issues with the Gitlab integration, given Gitlab's ongoing issues: https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/67645861f92e4e58064f7d32
We're seeing issues with the Gitlab integration, given Gitlab's ongoing issues: https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/67645861f92e4e58064f7d32
Gitlab has mitigated the issue and we are seeing recovery and no errors during ingestion.
We're seeing issues accessing the Compass application. The team is working on identifying the underlying cause.
We're seeing recovery across all of our systems. The team is still working on ensuring that impact is fully mitigated.
This incident has been resolved.
We're seeing issues accessing Compass. The team has identified the issue and is currently rolling out a fix.
We've identified the issue and reverted the faulty change. We're monitoring the change propagation and are seeing systems recover across the board.
This incident has been resolved.
We are currently investigating an issue that is causing the Github app to be unavailable for some tenants.
We have identified the issue and are working on a fix at the moment.
This issue has now been fixed and the app is now available for ise.
We are currently investigating this issue.
We've identified the cause of the issue and are seeing service quality recover.
This incident has been resolved.
We're seeing issues with the Github integration, given Github's ongoing issues: https://www.githubstatus.com/incidents/kz4khcgdsfdv
This incident has been resolved.