Atlassian Compass Outage History

Atlassian Compass is up right now

Atlassian Compass had 29 outages in the last 2 years totaling 16h 11m of downtime — averaging 1.2 incidents per month.

There were 29 Atlassian Compass outages since June 3, 2024 totaling 16h 11m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://compass.status.atlassian.com

Minor August 8, 2024

Event ingestion delayed

Detected by Pingoru
Aug 08, 2024, 10:49 PM UTC
Resolved
Aug 09, 2024, 02:55 AM UTC
Duration
4h 6m
Affected: Metrics
Timeline · 5 updates
  1. investigating Aug 08, 2024, 10:49 PM UTC

    We're seeing event ingestion and metric derivation delayed. The team is working on resolving the issue.

  2. identified Aug 08, 2024, 11:28 PM UTC

    The team has identified the cause for the delays and is rolling out a fix.

  3. monitoring Aug 09, 2024, 12:08 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Aug 09, 2024, 12:39 AM UTC

    Event ingestion times are back to normal, and we're seeing the delay between event ingestion and metric derivation go down. We're still monitoring the fix and will update once things are back to nominal.

  5. resolved Aug 09, 2024, 02:55 AM UTC

    Event ingestion and metric derivation are both working at normal capacity. This incident is resolved.

Read the full incident report →

Minor July 3, 2024

Issues logging in to Compass

Detected by Pingoru
Jul 03, 2024, 08:31 PM UTC
Resolved
Jul 04, 2024, 12:33 AM UTC
Duration
4h 2m
Affected: GraphQLBitbucketWebhooksComponent TemplatesScorecardsGitHub API RequestsRESTComponentsAuthentication and User ManagementGitlabEmailMetricsGitHub WebhooksSearchCircleCICheckOpsCircleCI CircleCI WebhooksJSMActivity TimelineJSWPurchasing & LicensingNewRelicOpsgenieSignupPagerDutySlackSwaggerUIStatuspageGithub
Timeline · 4 updates
  1. investigating Jul 03, 2024, 08:31 PM UTC

    We're seeing customers experience issues logging into Compass and using the service. The team has been notified and is investigating the cause.

  2. identified Jul 03, 2024, 08:41 PM UTC

    We're seeing recovery but are still working on identifying the root cause of the issue.

  3. monitoring Jul 03, 2024, 09:44 PM UTC

    The team has implemented a mitigation and we're seeing service quality hold. We're continuing to look into the root cause of the issue. We've also been able to isolate the time of impact to a 20-minute timeframe between 8:08pm 03/07 UTC and 08:31pm 03/07 UTC.

  4. resolved Jul 04, 2024, 12:33 AM UTC

    Between 03-07-2024 20:08 UTC to 03-07-2024 20:31 UTC, we experienced downtime for Compass. The issue has been resolved and the service is operating normally.

Read the full incident report →

Major June 17, 2024

The Developer Experience and Pull Requests dashboard (in the Teams page) include incorrect PR data

Detected by Pingoru
Jun 17, 2024, 05:39 AM UTC
Resolved
Jun 17, 2024, 12:29 PM UTC
Duration
6h 50m
Affected: Bitbucket
Timeline · 3 updates
  1. identified Jun 17, 2024, 05:39 AM UTC

    The Developer Experience and Pull Requests dashboard in the Teams page include incorrect PR data from other repositories (in the same workspace) connected to the Compass instance. The root cause has been identified and a fix is in progress.

  2. monitoring Jun 17, 2024, 08:48 AM UTC

    We've resolved the issue and are monitoring to verify changes.

  3. resolved Jun 17, 2024, 12:29 PM UTC

    The incident has been resolved.

Read the full incident report →

Minor June 3, 2024

Users experiencing errors using when using the product

Detected by Pingoru
Jun 03, 2024, 10:45 PM UTC
Resolved
Jun 03, 2024, 11:57 PM UTC
Duration
1h 12m
Affected: GraphQLRESTAuthentication and User Management
Timeline · 4 updates
  1. investigating Jun 03, 2024, 10:45 PM UTC

    We're seeing errors around authentication across the platform. The team has been alerted and is working on identifying the underlying issue.

  2. identified Jun 03, 2024, 10:59 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jun 03, 2024, 11:06 PM UTC

    We've rolled back the change that was identified as having caused the issues and we're seeing systems recover. We will continue monitoring recovery and will post further updates as needed.

  4. resolved Jun 03, 2024, 11:57 PM UTC

    This incident has been resolved.

Read the full incident report →