Jun 29, 16:58 UTC
Resolved - This incident has been resolved. Jun 29, 16:44 UTC
Monitoring - Error rates viewing orgs are recovering. We will continue to monitor to verify the fix resolves the issues. Jun 29, 15:54 UTC
Identified - We have identified the cause of errors accessing orgs. We are implementing a fix, and will monitor for recovery as the change rolls out. Jun 29, 12:16 UTC
Update - 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. Jun 29, 11:44 UTC
Update - 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-AuthenticationWe will post another update once we have more certainty. Jun 29, 11:33 UTC
Update - 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. Jun 29, 10:23 UTC
Investigating - 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.
This incident has been resolved.
Posted Jun 29, 2026 - 16:58 UTC
Error rates viewing orgs are recovering. We will continue to monitor to verify the fix resolves the issues.
Posted Jun 29, 2026 - 16:44 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.
Posted Jun 29, 2026 - 15:54 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.
Posted Jun 29, 2026 - 12:16 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.
Posted Jun 29, 2026 - 11:44 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.
Posted Jun 29, 2026 - 11:33 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.
Posted Jun 29, 2026 - 10:23 UTC
This incident affected: CircleCI UI.
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | Errors accessing CircleCI and delays starting pipelines and scheduled workflows | 0 | 7.34 | 17-07-2026 |
| 2 | Login issues for some Bitbucket users | 0 | 7.52 | 14-07-2026 |
| 3 | Errors loading app.circleci.com | 0 | 9 | 22-07-2026 |
| 4 | Errors with GitHub APIs delaying workflows | 0 | 8.55 | 20-07-2026 |
| 5 | GitHub service degradation may impact customers using GitHub | 0 | 5.38 | 12-08-2026 |
| 6 | GitHub service degradation may impact customers using GitHub | 0 | 5.38 | 24-07-2026 |
| 7 | Scheduled Maintenance - Support Portal | 0 | 6.77 | 06-08-2026 |
| 8 | Outage impacting web experience and pipelines starting | 0 | 8.9 | 02-07-2026 |
| 9 | Investigating — Usage API Not Available | 0 | 9.96 | 25-06-2026 |
| 10 | Incident with Actions | 0 | 8.82 | 06-08-2026 |