Вход на сайт

Просмотр новости

Найдите то, что Вас интересует

Some customers are unable to access their organizations

Дата публикации: 29-06-2026 16:58:09


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.

Основное содержимое страницы с новостью.

Resolved

This incident has been resolved.

Posted Jun 29, 2026 - 16:58 UTC

Monitoring

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

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.

Posted Jun 29, 2026 - 15:54 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.

Posted Jun 29, 2026 - 12:16 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-Authentication

We will post another update once we have more certainty.

Posted Jun 29, 2026 - 11:44 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.

Posted Jun 29, 2026 - 11:33 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.

Posted Jun 29, 2026 - 10:23 UTC

This incident affected: CircleCI UI.

Схожие новости

#Наименование новостиТональностьИнформативностьДата публикации
1Errors accessing CircleCI and delays starting pipelines and scheduled workflows07.3417-07-2026
2Login issues for some Bitbucket users07.5214-07-2026
3Errors loading app.circleci.com0922-07-2026
4Errors with GitHub APIs delaying workflows08.5520-07-2026
5GitHub service degradation may impact customers using GitHub05.3812-08-2026
6GitHub service degradation may impact customers using GitHub05.3824-07-2026
7Scheduled Maintenance - Support Portal06.7706-08-2026
8Outage impacting web experience and pipelines starting08.902-07-2026
9Investigating — Usage API Not Available09.9625-06-2026
10Incident with Actions08.8206-08-2026

Классификация: . Схожих патентов: 0. Схожих новостей: 10. Тональность: 0. Информативность: 8.2. Источник: status.circleci.com.