Skip to content
OutageDeck

Incident detail

Some pipelines not triggering due to GitHub API failures

Resolved incidentMajor1 affected service

Timeline window

to

Outage alerts

Get alerted the next time CircleCI breaks

Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow CircleCI alerts work

Timeline

Incident updates

Every update CircleCI posted, oldest to newest, exactly as it appeared on their official status page.

  1. 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.

  2. Identified

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

  3. Monitoring

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

  4. Resolved

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

Keep exploring

More from CircleCI

Neighboring incidents on CircleCI's timeline and the rest of their record on OutageDeck.

← Older incident

Pipelines — Workflow Creation Errors and Missing GitHub Status Updates

Newer incident →

Usage API data for 4/1 is incomplete with multiple columns showing null values. Data prior to 4/1 is unaffected. We are investigating.

All CircleCI incidentsCircleCI live status