CircleCI incident: Some customers are unable to access their organizations

Affected components

• CircleCI UI

1. resolvedJun 29, 2026, 16:58 UTC

   This incident has been resolved.

2. monitoringJun 29, 2026, 16:44 UTC

   Error rates viewing orgs are recovering. We will continue to monitor to verify the fix resolves the issues.

3. identifiedJun 29, 2026, 15:54 UTC

   We have identified the cause of errors accessing orgs. We are implementing a fix, and will monitor for recovery as the change rolls out.

4. investigatingJun 29, 2026, 12:16 UTC

   We are continuing to investigate reports that some customers cannot access their organizations in CircleCI. Our investigation continues to point to an authorization issue between CircleCI and GitHub. Some affected users have received a 403 from GitHub indicating the resource is SAML protected and the OAuth token may not be authorized. We previously shared re-authenticating as a potential workaround. We have since received reports that this didn't restore access for all affected customers, so we don't consider it a reliable resolution at this time. Our engineering team is continuing to investigate this to determine the cause and next steps. We will post another update as soon as we have more information. We apologize for the continued disruption and appreciate your patience.

5. investigatingJun 29, 2026, 11:44 UTC

   We are still investigating reports that some customers cannot access their organizations in CircleCI. Early findings suggest the problem may be related to GitHub authorization, where affected users receive a 403 from GitHub indicating the resource is SAML protected and the OAuth token may not be authorized. We have not yet confirmed this as the root cause. As a potential workaround, some users may be able to restore access by performing a re-authentication: https://support.circleci.com/hc/en-us/articles/360051228052-How-to-Perform-a-Re-Authentication We will post another update once we have more certainty.

6. investigatingJun 29, 2026, 11:33 UTC

   We are continuing to investigate reports that some customers are unable to access their organizations in CircleCI. Those affected may see errors when loading their organizations. Our engineering team are still working to identify the cause. We will share another update as soon as we have more information.

7. investigatingJun 29, 2026, 10:23 UTC

   We are investigating reports that some customers are unable to access their organizations in CircleCI. Those affected may see errors when loading their organizations. Our engineering team is actively investigating.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in CircleCI's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Mapbox: Elevated Rate of Partial Response (206) and Not Found (404) Errors in the Search Box APIMajor · Jun 29, 2026, 08:53 UTC
• Expo: Elevated error rates and latency for EAS Build, Workflows, and SubmitMajor · Jun 29, 2026, 15:14 UTC
• Smartsheet: Increased spam activity with Smartsheet FormsMinor · Jun 18, 2026, 21:42 UTC
• Snyk: Third-Party Vendor Security Incident (Klue)Minor · Jun 19, 2026, 23:15 UTC
• Linode: Service Issue - ACLP MetricsMinor · Jun 26, 2026, 17:35 UTC
• Akamai: Cloudlets issues while activating Application Load Balancing configurationsMinor · Jun 28, 2026, 14:45 UTC
• Confluent Cloud: Confluent Cloud Metrics API is currently experiencing elevated error ratesMinor · Jun 29, 2026, 11:40 UTC
• Expo: Elevated error rates and latency for EAS Build, Workflows, and SubmitMinor · Jun 29, 2026, 15:28 UTC
• Elasticsearch: Issues delivering static assets to productsMinor · Jun 29, 2026, 16:32 UTC

How often does CircleCI have incidents?

CircleCI reported 22 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 1h 38m. See CircleCI's uptime and incident history