Circle CI incident
Some pipelines not triggering due to GitHub API failures
Affected components
Pipelines & WorkflowsGitHub API Requests
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.
Looking to track Circle CI downtime and outages?
Pingoru polls Circle CI's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Circle CI reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Circle CI alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
Start monitoring Circle CI for free
5 free monitors · No credit card required