Some pipelines not triggering due to GitHub API failures

Summary

Some pipelines not triggering due to GitHub API failures

It appears that GitHub's `GET /repos/{owner}/{repo}/commits` API is now stable and responsive.

• Started

  Apr 1, 2026 · 11:55 AM

• Resolved

  Apr 1, 2026 · 12:23 PM

• Duration

  28m

• Severity

  Major

• ◐

  Investigating

  Apr 1 · 11:55 AM CircleCI

  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 1 · 11:58 AM CircleCI

  We are continuing to see very high error rates from GitHub's `GET /repos/{owner}/{repo}/commits` API.

• ◉

  Monitoring

  Apr 1 · 12:12 PM CircleCI

  GitHub's `GET /repos/{owner}/{repo}/commits` API has appeared to recover. We will continue to monitor this.

• ✓

  Resolved

  Apr 1 · 12:23 PM CircleCI

  It appears that GitHub's `GET /repos/{owner}/{repo}/commits` API is now stable and responsive.