Provider
CircleCIIncident detail
Some pipelines not triggering due to GitHub API failures
Some pipelines not triggering due to GitHub API failures
Resolved incidentMajor1 affected service
Timeline window
to
Sponsored placement
Google AdSense placeholder
This slot is reserved for future AdSense placement. It stays as a non-invasive placeholder until a client ID and slot ID are configured.
Timeline
Incident updates
Updates are normalized from the official source chronology so timeline changes remain easy to scan.
Investigating
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
We are continuing to see very high error rates from GitHub's `GET /repos/{owner}/{repo}/commits` API.
Monitoring
GitHub's `GET /repos/{owner}/{repo}/commits` API has appeared to recover. We will continue to monitor this.
Resolved
It appears that GitHub's `GET /repos/{owner}/{repo}/commits` API is now stable and responsive.