Circle CI incident
Some pipelines not triggering due to GitHub API failures
Resolved after 28 minutes, affecting Pipelines & Workflows and GitHub API Requests, on April 1, 2026.
It appears that GitHub's `GET /repos/{owner}/{repo}/commits` API is now stable and responsive.
Affected components
Update timeline
- investigating Apr 01, 2026, 11:55 AM UTC
Some pipelines may not trigger due to a high rate of API failures on one of GitHub's API endpoints. This includes some manually-triggered pipelines, some OAuth hooks and some scheduled pipelines.
- identified Apr 01, 2026, 11:58 AM UTC
We are continuing to see very high error rates from GitHub's `GET /repos/{owner}/{repo}/commits` API.
- monitoring Apr 01, 2026, 12:12 PM UTC
GitHub's `GET /repos/{owner}/{repo}/commits` API has appeared to recover. We will continue to monitor this.
- resolved Apr 01, 2026, 12:23 PM UTC
It appears that GitHub's `GET /repos/{owner}/{repo}/commits` API is now stable and responsive.
Your product runs on more than Circle CI
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services