- Level
- confirmed
- Worst impact
- Degraded
- Components
- GitHub API Requests
- Down Index
- 15of 100
What to do
Check whether you use CircleCI GitHub API Requests. 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 10m it lasted.
Anything that failed between 2026-06-10 16:30 UTC and 2026-06-10 16:41 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 4
- investigating
Some users may have seen delays or missing commit statuses on GitHub PRs due to an ongoing GitHub API incident. We are continuing to process builds as normal. We will provide further updates as we get more information
provider
- investigating
We are continuing to investigate this issue.
provider
- monitoring
We are seeing signs of recovery from the GitHub API.
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-5f9f4d52df
Is CircleCI still down?
No, this incident was resolved 2026-06-10 16:41 UTC. For CircleCI's live state, see https://down.guide/circleci.
How long did it last?
10m, from 2026-06-10 16:30 UTC to 2026-06-10 16:41 UTC, by the times CircleCI posted.
What was affected?
CircleCI named GitHub API Requests.
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.