SonarQube Outage History

Started Mar 11, 2026, 03:06 PM UTC· resolved Mar 11, 2026, 04:18 PM UTC

1. investigating Mar 11, 2026, 03:06 PM UTC

   We are currently experiencing delays with Automatic Analysis and intermittent login failures due to an ongoing service disruption with a third-party vendor. Current Status: While the root cause is an upstream outage affecting API requests and webhooks, our engineering team is proactively investigating potential internal solutions we can deliver to mitigate the impact while the vendor's issue is still ongoing. Impact: Automatic Analysis: Extended processing times. Authentication: Intermittent failures when logging in via the affected provider. We are monitoring the situation closely and will provide an update as soon as more information or a mitigation becomes available.

2. resolved Mar 11, 2026, 04:18 PM UTC

   The third-party vendor has resolved their service disruption. Our team has confirmed that Automatic Analysis and Login services are now functioning normally. Thank you for your patience!

Read the full incident report →

Started Feb 13, 2026, 02:00 PM UTC· resolved Feb 13, 2026, 03:05 PM UTC

1. investigating Feb 13, 2026, 02:00 PM UTC

   We are currently experiencing a major service interruption affecting Automatic Analysis in our EU Instance. The US regions are operating normally. Our team is actively investigating the EU issue to restore service. We will provide an update as soon as we have a recovery timeline.

2. monitoring Feb 13, 2026, 02:39 PM UTC

   We have implemented a fix for the issues affecting our EU Instance. We can confirm that Automated Analysis is now working correctly, and requests are processing as expected. We also recognize that the Pull Request experience was impacted by these failures; this should no longer be affected, and PR statuses should update normally moving forward. We are continuing to monitor the service closely to ensure full stability.

3. resolved Feb 13, 2026, 03:05 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 02, 2026, 04:37 PM UTC· resolved Feb 02, 2026, 07:00 PM UTC

1. identified Feb 02, 2026, 04:37 PM UTC

   We are experiencing an issue resulting in JaCoCo coverage being reporting as zero. This could result in Quality Gates failing in error. The issue has been identified and is being addressed. After the issue is fixed, new analysis will be required to correct the Quality Gates. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

2. resolved Feb 02, 2026, 07:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 29, 2026, 01:00 PM UTC· resolved Jan 29, 2026, 06:21 PM UTC

1. investigating Jan 29, 2026, 01:00 PM UTC

   We are experiencing a problem where users are not able to view the issues within the issues page of an organization. The problem is currently being investigated. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional problems or share your observations, please visit the Sonar Community or contact Support.

2. resolved Jan 29, 2026, 06:21 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 28, 2026, 04:25 PM UTC· resolved Jan 28, 2026, 04:29 PM UTC

1. investigating Jan 28, 2026, 04:25 PM UTC

   We are currently investigating an issue impacting users who are trying to log in to sonarcloud.io using Bitbucket. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

2. resolved Jan 28, 2026, 04:29 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 28, 2026, 02:11 PM UTC· resolved Jan 28, 2026, 05:49 PM UTC

1. investigating Jan 28, 2026, 02:11 PM UTC

   We are experiencing an issue causing delays in Autoscan analyses in the SonarQube EU instance. The issue is currently being investigated. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

2. monitoring Jan 28, 2026, 03:20 PM UTC

   We are still investigating the root cause, but we have implemented temporary measures to mitigate the issue, and we are currently not seeing any delays in Autoscan analyses. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

3. resolved Jan 28, 2026, 05:49 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 26, 2026, 03:30 AM UTC· resolved Jan 26, 2026, 11:15 AM UTC

1. resolved Jan 26, 2026, 01:25 PM UTC

   We experienced a service disruption to Automatic Analysis on SonarQube Cloud (EU) between 11:30 and 12:15 CET today. During this window, 70% of tasks submitted to Automatic Analysis failed to complete successfully. We have implemented a fix and all systems are operational as of 12:15 CET. If your analysis failed during the impact window, please manually re-trigger or resubmit the affected analyses. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Jan 21, 2026, 04:44 PM UTC· resolved Jan 21, 2026, 06:58 PM UTC

1. identified Jan 21, 2026, 04:44 PM UTC

   Code Coverage calculation for Go is currently not working. We have identified the issue and are actively working on the fix. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

2. resolved Jan 21, 2026, 06:58 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 07, 2026, 02:15 PM UTC· resolved Jan 07, 2026, 02:47 PM UTC

1. investigating Jan 07, 2026, 02:15 PM UTC

   Analysis fails with Sonar Scanner for NPM version 4.3.3. We are actively working on the fix. The workaround is to explicitly invoke version 4.3.2. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

2. resolved Jan 07, 2026, 02:47 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 17, 2025, 01:38 PM UTC· resolved Dec 17, 2025, 01:53 PM UTC

1. identified Dec 17, 2025, 01:38 PM UTC

   We are currently investigating an issue where some Autoscan analyses are failing due to authentication errors. Our team has identified the root cause and is currently working on a resolution. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

2. resolved Dec 17, 2025, 01:53 PM UTC

   Our engineering team has successfully redeployed and refreshed all Autoscan workers across all environments. All services are now operating normally, and failed analyses are being re-processed. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Dec 15, 2025, 09:36 AM UTC· resolved Dec 15, 2025, 02:54 PM UTC

1. investigating Dec 15, 2025, 09:36 AM UTC

   We are experiencing an issue where automatic analysis are not being processed in a reasonable time. The issue is currently being investigated. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

2. identified Dec 15, 2025, 10:56 AM UTC

   The issue has been fixed for SonarQube Cloud US. Remediation work is currently in progress for SonarQube Cloud EU. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

3. monitoring Dec 15, 2025, 01:18 PM UTC

   The underlying issue affecting analysis processing on SonarQube Cloud EU has been resolved. The system is currently working through the backlog of analysis requests submitted during the incident. While processing, you may still experience increased latency. We anticipate that all latency will return to normal within the next 2 hours. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

4. resolved Dec 15, 2025, 02:54 PM UTC

   The incident affecting analysis request processing on SonarQube Cloud EU is now fully resolved. System performance has been restored, the analysis backlog has been successfully cleared, and latency is operating at normal parameters. We appreciate your patience and apologize for any disruption this may have caused.

Read the full incident report →

Started Oct 30, 2025, 10:55 AM UTC· resolved Oct 30, 2025, 11:26 AM UTC

1. resolved Oct 30, 2025, 03:49 PM UTC

   During a deployment a downtime of 5 minutes occurred on both EU and US instances causing failed analysis, quality gates related operations during EU Instance (12:55-13:00 CEST) and US Instance (13:15-13:26 CEST) on Oct 30, 2025. Analyses that failed during this period will need to be resubmitted. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

Read the full incident report →

Started Oct 22, 2025, 03:03 PM UTC· resolved Oct 23, 2025, 12:07 PM UTC

1. investigating Oct 22, 2025, 03:03 PM UTC

   We are experiencing an issue with the Report processor that causes Analysis to fail intermittently. The issue is currently being investigated. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

2. monitoring Oct 22, 2025, 07:49 PM UTC

   We have implemented mitigation steps and are no longer observing any new analysis failures. Our team is still investigating and working to resolve residual slowness affecting some users. Action Required: Please resubmit any analysis that failed during the incident window. We apologize for the inconvenience.

3. identified Oct 23, 2025, 08:26 AM UTC

   We're observing increased latency across the service. Our team is actively investigating the cause and working to mitigate the impact. Additional updates will be shared on this page as necessary. We apologize for any inconvenience.

4. monitoring Oct 23, 2025, 09:18 AM UTC

   The analyses no longer display the increased latency previously observed. Our team will continue to monitor the service. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

5. resolved Oct 23, 2025, 12:07 PM UTC

   A fix has been successfully deployed, and the incident is now considered resolved. Thank you for your patience during this time. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

Read the full incident report →

Started Oct 20, 2025, 03:06 PM UTC· resolved Oct 21, 2025, 08:45 AM UTC

1. investigating Oct 20, 2025, 03:06 PM UTC

   We are continuing to experience issues with AWS infrastructure in the US-EAST-1 Region due to which Analysis is not processing since 2 pm UTC. We are monitoring the situation closely and are awaiting updates from our provider. You can track the status of the underlying infrastructure directly on the AWS Health Dashboard: https://health.aws.amazon.com/health/status We apologize for the inconvenience and will provide our next update as soon as we receive new information from AWS.

2. identified Oct 20, 2025, 06:28 PM UTC

   Our cloud provider, AWS, has identified the root cause and is actively working on a mitigation. We are closely monitoring their progress and will share another update as soon as we have more definitive information. We apologize for the inconvenience and thank you for your patience. We will provide our next update as soon as we receive new details from AWS.

3. monitoring Oct 20, 2025, 07:50 PM UTC

   AWS is observing continued recovery across most of the affected services in the US-EAST-1 Region. We are also seeing recovery across our platform and is currently working through the remaining backlog, which we are closely monitoring. Action Required: Any Analysis that failed during the outage will need to be resubmitted. We apologize for the inconvenience and thank you for your patience.

4. monitoring Oct 20, 2025, 09:22 PM UTC

   AWS is reporting continued recovery across the majority of impacted services in the US-EAST-1 Region. We are also seeing widespread recovery across our platform. While analysis has resumed, processing speed is slower than normal as systems stabilize. We are closely monitoring the situation and taking all necessary steps to restore full performance. We sincerely apologize for the disruption and appreciate your continued patience.

5. monitoring Oct 20, 2025, 09:31 PM UTC

   We are continuing to monitor for any further issues.

6. resolved Oct 21, 2025, 08:45 AM UTC

   The outage is fully resolved, and all systems are now completely operational. The AWS incident that impacted the US-EAST-1 region between 11:49 PM PDT on October 19 and 3:01 PM PDT on October 20 is officially closed. All SonarQube Cloud services are functioning normally. Please ensure that any analysis that failed during the disruption is resubmitted. We greatly appreciate your patience during this period of recovery.

Read the full incident report →

Started Oct 20, 2025, 07:30 AM UTC· resolved Oct 20, 2025, 10:41 AM UTC

1. investigating Oct 20, 2025, 07:30 AM UTC

   We are currently experiencing an issue that may cause requests to our endpoints to fail intermittently. This degradation is a result of an ongoing infrastructure issue being reported by Amazon Web Services (AWS). We are monitoring the situation closely and are awaiting updates from our provider. You can track the status of the underlying infrastructure directly on the AWS Health Dashboard: https://health.aws.amazon.com/health/status We apologize for the inconvenience and will provide our next update as soon as we receive new information from AWS.

2. investigating Oct 20, 2025, 08:44 AM UTC

   We are still experiencing intermittent failures on our endpoints and have observed that the underlying AWS issue is causing wider impact, specifically affecting Bitbucket login functionality on sonarcloud.io. AWS is actively investigating the root cause of this infrastructure issue. Our teams are currently focused on closely monitoring their progress via their official status page and assessing the complete impact on our services. For the latest updates from our infrastructure provider, please refer to the AWS Health Dashboard: https://health.aws.amazon.com/health/status We will provide our next update immediately upon a significant status change from AWS.

3. identified Oct 20, 2025, 09:07 AM UTC

   AWS has identified a potential root cause for the high error rates: a problem with DNS resolution for the DynamoDB API endpoint in the US-EAST-1 Region. The issues affecting Bitbucket login on sonarcloud.io are consistent with this wider outage. AWS is working on multiple parallel paths to accelerate recovery. Our team remains focused on monitoring their progress and preparing our systems for recovery once the AWS issue is resolved. For the most immediate and detailed information, please monitor the official AWS Health Dashboard: https://health.aws.amazon.com/health/status We will provide our next update as soon as AWS shares new information, or if we observe a change in service stability.

4. identified Oct 20, 2025, 09:30 AM UTC

   We have received notification that Amazon Web Services (AWS) has implemented initial mitigation strategies for the DNS resolution issue in the US-EAST-1 Region. We are actively monitoring our endpoints and the Bitbucket/sonarcloud.io login functionality to confirm full service restoration. You can continue to track the official AWS Health Dashboard here: https://health.aws.amazon.com/health/status We will provide our next update as soon as we have confirmation of full stability or further information from AWS.

5. monitoring Oct 20, 2025, 09:48 AM UTC

   We have received confirmation that Amazon Web Services (AWS) is now observing significant signs of recovery following the applied mitigations. Most requests should now be succeeding, indicating that the core DNS resolution issue in US-EAST-1 is largely resolved. Consequently, issues with our entitlement endpoints and Bitbucket login on sonarcloud.io should be improving rapidly. AWS is working through a backlog of queued requests, so please note that you may still see slightly increased latency as the remaining work is fully processed. We are continuing to monitor our services closely and will issue a final status notification once the incident is officially resolved. You can follow the official AWS Health Dashboard for their next update: https://health.aws.amazon.com/health/status

6. monitoring Oct 20, 2025, 10:25 AM UTC

   We are pleased to share that Amazon Web Services (AWS) is observing continued recovery across most of the affected services in the US-EAST-1 Region. AWS has also confirmed that global services and features that rely on US-EAST-1 have now recovered. This strongly suggests that the impact on our endpoints and the Bitbucket login on sonarcloud.io has subsided. While AWS continues to work toward full resolution of the underlying issue, the major impact appears to be over. We will issue a final all-clear notification once we confirm sustained stability across all our services and the incident is officially closed by AWS. You can monitor the official AWS Health Dashboard here: https://health.aws.amazon.com/health/status

7. resolved Oct 20, 2025, 10:41 AM UTC

   We are happy to share the final significant update from AWS: the underlying DNS issue has been fully mitigated, and most AWS service operations are succeeding normally now. This confirms that the root cause impacting our entitlement endpoints and the Bitbucket login on sonarcloud.io has been addressed. If you are a user still experiencing issues resolving the DynamoDB service endpoints in US-EAST-1, AWS recommends flushing your DNS caches. Thank you for your patience throughout this event. You can monitor the official AWS Health Dashboard here: https://health.aws.amazon.com/health/status

Read the full incident report →

Started Oct 17, 2025, 07:35 AM UTC· resolved Oct 17, 2025, 08:28 AM UTC

1. investigating Oct 17, 2025, 07:35 AM UTC

   We are experiencing an issue impacting some SonarQube Cloud users attempting to log in via Single Sign-On (SSO). The issue is currently being investigated. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

2. identified Oct 17, 2025, 08:09 AM UTC

   We have successfully implemented the fix, and the issue is now resolved for users in the EU region. We are currently working on a fix for the US instance.

3. resolved Oct 17, 2025, 08:28 AM UTC

   We have successfully implemented the solution and confirmed service restoration. Thank you for your patience while our team worked diligently to resolve this incident.

Read the full incident report →

Started Oct 09, 2025, 02:30 PM UTC· resolved Oct 09, 2025, 02:30 PM UTC

1. resolved Oct 09, 2025, 03:41 PM UTC

   A GitHub outage caused Autoscan to receive 0% of webhook requests from Github. Any users who submitted code in their own repo would not trigger Autoscan. This also impacted customers who use CI-based analysis related to Github. CI customers who do not use Github were unaffected. GitHub has indicated recovery at 17:26 (GMT +2) and the backlog queue is processing without issue. As of 17:45 (GMT +2), we have completed processing of the backlog. Impact Start: 2025-10-09 16:30 (GMT +2) Mitigation (GitHub recovery, start of backlog processing): 2025-10-09 17:26 (GMT +2) Impact End (Full return to normal operations): 2025-10-09 17:45 (GMT +2) https://www.githubstatus.com/incidents/k7bhmjkblcwp

Read the full incident report →

Started Sep 30, 2025, 03:59 PM UTC· resolved Sep 30, 2025, 04:25 PM UTC

1. identified Sep 30, 2025, 03:59 PM UTC

   We're aware that some users are intermittently experiencing an Internal Server Error affecting various services. We've identified the root cause and are actively working on a resolution now. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

2. resolved Sep 30, 2025, 04:25 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 30, 2025, 09:37 AM UTC· resolved Sep 30, 2025, 11:23 AM UTC

1. investigating Sep 30, 2025, 09:37 AM UTC

   We are aware of reports of an issue affecting user authentication for SonarQube Cloud. This issue is also confirmed to be impacting CI-based analysis that relies on SonarQube Cloud authentication. Our engineering team is actively investigating the cause and working on a resolution to restore all affected services. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

2. identified Sep 30, 2025, 09:46 AM UTC

   We've identified a recent configuration change as the likely root cause of the current authentication and CI analysis issues. Our team is now actively rolling back this change. We apologize for the disruption and will post another update with more details shortly.

3. monitoring Sep 30, 2025, 10:11 AM UTC

   The rollback of the recent configuration change has been successfully implemented. We are currently in a dedicated monitoring phase to confirm that authentication services and CI-based analysis have fully recovered and are running stably. We are seeing positive signs of recovery for the SonarQube Cloud EU. We are working on implementing the fix for the SonarQube Cloud US. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

4. monitoring Sep 30, 2025, 10:21 AM UTC

   The rollback of the recent configuration change has been successfully implemented across both our EU and US regions. We are now in a dedicated monitoring phase to confirm that authentication services and CI-based analysis have fully recovered and are running stably across the board. We are seeing continued positive trends and expect to post the final update confirming the full resolution of this incident shortly. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

5. resolved Sep 30, 2025, 11:23 AM UTC

   This incident is now resolved. Following the successful rollback of the recent configuration change across both the EU and US regions, we have confirmed that all services, including user authentication and CI-based analysis, have fully recovered and are running stably. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

Read the full incident report →

Started Sep 16, 2025, 06:22 PM UTC· resolved Sep 16, 2025, 08:27 PM UTC

1. investigating Sep 16, 2025, 06:22 PM UTC

   We are currently experiencing an issue affecting Server-side Analysis processing. You may experience a timeout waiting for Quality Gate results. Affected analyses will need to be rerun. Additionally there maybe issues navigating the UI. We will provide further updates on this page as needed. We apologize for any inconvenience this may cause. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

2. resolved Sep 16, 2025, 08:27 PM UTC

   The incident has been resolved. Please rerun the failed Analysis. We apologize for the inconvenience. Thank you.

Read the full incident report →

Started Aug 04, 2025, 02:05 PM UTC· resolved Aug 11, 2025, 12:56 PM UTC

1. investigating Aug 04, 2025, 02:05 PM UTC

   We are experiencing an issue causing sporadic failure of Automatic and CI-based analysis across all languages. The issue is currently being investigated. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

2. investigating Aug 06, 2025, 03:20 PM UTC

   We are actively working to reduce the error rate and collaborating with our cloud provider to investigate further. We hope to resolve the root cause soon. We apologize again for the ongoing disruption and appreciate your patience.

3. monitoring Aug 06, 2025, 09:44 PM UTC

   Our Cloud provider has identified the root cause of the issue and has already addressed the issue in the region with the highest rate of failure. We have confirmed that the rate of failure has dropped to zero in that region. Now we are waiting for the fix to be applied across all regions. Thank you for your continued patience and understanding as we work to fully resolve the issue

4. monitoring Aug 07, 2025, 08:39 AM UTC

   Our Cloud provider is actively rolling out the fix and prioritizing the most affected regions, to restore service as quickly as possible. However, due to the nature of this global deployment, the rollout will take some time. You may continue to experience the error until the fix is fully deployed. Thank you for your patience and understanding as we work to fully resolve the issue.

5. resolved Aug 11, 2025, 12:56 PM UTC

   This incident has been resolved. Thank you for your patience and support during this period of time.

Read the full incident report →

Started Jul 29, 2025, 10:39 AM UTC· resolved Jul 29, 2025, 11:09 AM UTC

1. investigating Jul 29, 2025, 10:39 AM UTC

   We have received reports where customers are experiencing 422 errors while trying to onboard GitHub projects in SonarQube Cloud. The issue is currently being investigated.

2. resolved Jul 29, 2025, 11:09 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 23, 2025, 09:46 AM UTC· resolved Jul 23, 2025, 10:06 AM UTC

1. investigating Jul 23, 2025, 09:46 AM UTC

   We are currently investigating this issue.

2. resolved Jul 23, 2025, 10:06 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 04, 2025, 09:31 AM UTC· resolved Jun 04, 2025, 12:47 PM UTC

1. investigating Jun 04, 2025, 09:31 AM UTC

   We are experiencing an issue resulting in Analyses being processed with a delay. The issue is currently being investigated. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

2. investigating Jun 04, 2025, 10:49 AM UTC

   We appreciate your patience as we continue to investigate this. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

3. identified Jun 04, 2025, 12:04 PM UTC

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

4. resolved Jun 04, 2025, 12:47 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 26, 2025, 08:19 AM UTC· resolved May 26, 2025, 09:53 AM UTC

1. investigating May 26, 2025, 08:19 AM UTC

   We want to inform you that GitHub is currently experiencing degraded performance for API requests and git operations. As a result, some users may encounter login failures when attempting to sign in with their GitHub accounts. We are actively monitoring the situation via GitHub’s status page and will keep you updated as more information becomes available. Thank you for your patience and understanding.

2. resolved May 26, 2025, 09:53 AM UTC

   GitHub has reported that the incident has been resolved.

Read the full incident report →