- Level
- confirmed
- Worst impact
- Degraded
- Components
- GitHub Pull Requests
- Down Index
- 21of 100
What to do
Check whether you use CircleCI GitHub Pull 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 3h 32m it lasted.
Anything that failed between 2026-05-06 17:54 UTC and 2026-05-06 21:26 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 3
- monitoring
GitHub is reporting a major incident for degraded pull request availability. This does not impact running CircleCI builds for newly created pull requests or push events.
provider
- monitoring
We are continuing to monitor for any further 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-1bbb3f2634
Is CircleCI still down?
No, this incident was resolved 2026-05-06 21:26 UTC. For CircleCI's live state, see https://down.guide/circleci.
How long did it last?
3h 32m, from 2026-05-06 17:54 UTC to 2026-05-06 21:26 UTC, by the times CircleCI posted.
What was affected?
CircleCI named GitHub Pull 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.