Circle CI incident
Errors accessing CircleCI and delays starting pipelines and scheduled workflows
Circle CI experienced a minor incident on July 16, 2026 affecting Pipelines & Workflows, lasting 1h 22m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 16, 2026, 11:04 PM UTC
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.
- identified Jul 16, 2026, 11:42 PM UTC
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.
- monitoring Jul 17, 2026, 12:09 AM UTC
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.
- resolved Jul 17, 2026, 12:26 AM UTC
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.