- Level
- confirmed
- Worst impact
- Degraded
- Components
- CircleCI UI
- Regions
- us
- Down Index
- 26of 100
What to do
Check whether you use CircleCI CircleCI UI in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 6h 35m it lasted.
Anything that failed between 2026-06-29 10:23 UTC and 2026-06-29 16:58 UTC may need a replay.Subscribe to CircleCI's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=circleci works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from CircleCI 7
- 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.
provider
- investigating
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.
provider
- investigating
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.
provider
- investigating
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.
provider
- 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.
provider
- monitoring
Error rates viewing orgs are recovering. We will continue to monitor to verify the fix resolves the issues.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-700113213e
Is CircleCI still down?
No, this incident was resolved 2026-06-29 16:58 UTC. For CircleCI's live state, see https://down.guide/circleci.
How long did it last?
6h 35m, from 2026-06-29 10:23 UTC to 2026-06-29 16:58 UTC, by the times CircleCI posted.
What was affected?
CircleCI named CircleCI UI in us.
What caused it?
CircleCI hasn't published a root cause. If it does, it shows here.
Where does this come from?
CircleCI's official status page, https://status.circleci.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.