- Level
- confirmed
- Worst impact
- Degraded
- Components
- Pipelines & Workflows
- Down Index
- 19of 100
What to do
Check whether you use CircleCI Pipelines & Workflows. 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 1h 22m it lasted.
Anything that failed between 2026-07-16 23:04 UTC and 2026-07-17 00: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 4
- investigating
We're investigating an issue where customers may see errors loading the CircleCI web app and signing in, along with pipelines and scheduled workflows failing to start or running late. This is related to an ongoing incident affecting GitHub. You can follow GitHub's status at https://www.githubstatus.com/incidents/gxycch3076xk. Our engineers are actively investigating. We will provide another update as soon as we have more information to share.
provider
- identified
We are continuing to see high failure rates from GitHub APIs which are impacting login and workflow processing. We will continue to monitor the GitHub API for recovery.
provider
- monitoring
What's happening The upstream incident affecting GitHub has been mitigated and is now being monitored on GitHub's side. You can follow GitHub's status at https://www.githubstatus.com/. What can you expect Access to the CircleCI web app, sign-in, and pipeline and workflow processing are returning to normal. You may still see intermittent errors or delayed scheduled pipelines and workflows as systems stabilize. Thank you for your patience while we monitor for full recovery.
provider
- resolved
An incident affecting GitHub's API caused CircleCI customers to experience errors loading the web app and signing in, along with pipelines and scheduled workflows failing to start or running late. GitHub has resolved the underlying incident (https://www.githubstatus.com/) and all affected functionality has returned to normal. Customers whose jobs or pipelines failed may rerun them. Scheduled pipelines and workflows that were missed during the incident will not run automatically and will need to be re-triggered. We thank you for your patience.
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-b5502bacd8
Is CircleCI still down?
No, this incident was resolved 2026-07-17 00:26 UTC. For CircleCI's live state, see https://down.guide/circleci.
How long did it last?
1h 22m, from 2026-07-16 23:04 UTC to 2026-07-17 00:26 UTC, by the times CircleCI posted.
What was affected?
CircleCI named Pipelines & Workflows.
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.