Skip to main content

CircleCI vs GitHub

Front door check counts, what each vendor’s status page recorded and SLA terms for these vendors.

30-day window ending

Front door checks

Every 15 minutes we send a request to a documented endpoint for each vendor from a single CheckUpstream location and count the answers. A reachable front door does not confirm that a customer action worked.

Front door check counts: CircleCI and GitHub
Last 30 daysCircleCIGitHub
Front door reachableOut of checks with a clear answer
  • 2,878 of 2,878

    checks to circleci.com

  • 2,661 of 2,661

    checks to api.github.com

Checks 15 minutes apart cannot see disruptions shorter than that. Each vendor is checked at its own endpoints, so the counts cover different things.

CircleCI · check scope

  • circleci.comapi · No vendor region

    Front door reachable in 2,878 of 2,878 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    1 more check gave no clear answer and is not counted.

    First check in this window
    Latest clear answer
View CircleCI record

GitHub · check scope

  • api.github.comapi · No vendor region

    Front door reachable in 2,661 of 2,661 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    218 more checks gave no clear answer and are not counted.

    First check in this window
    Latest clear answer
View GitHub record

What each vendor’s status page says

Recorded starts in the same 30-day window, excluding maintenance. Vendors report incidents differently; fewer posts don’t prove better reliability.

Recorded incidents: CircleCI and GitHub
Last 30 daysCircleCIGitHub
Incidents recorded

6

12

Recorded incident durationMedian

1h 49m

6 valid durations

1h 12m

12 valid durations

Duration uses at least 5 incidents with vendor-supplied starts and recorded closure times. First-observed starts are excluded. A record may close when a post disappears or our tracking period expires; this does not confirm recovery. A missing closure time does not mean an outage is ongoing.

CircleCI says

  • Delays starting Gen 2 Docker Jobs

    Started
    Closed in record
    Source incident
  • Delays in processing new signups and plan changes

    Started
    Closed in record
    Source incident
  • Delays starting Linux Machine jobs

    Started
    Closed in record
    Source incident

GitHub says

  • Actions Job Delays

    Started
    Closed in record
    Source incident
  • Elevated request latency

    Started
    Closed in record
    Source incident
  • Copilot Code Review is unable to complete reviews

    Started
    Closed in record
    Source incident

Check the terms for your plan

An SLA applies to specific products and plans. Credit eligibility also depends on exclusions, evidence and filing deadlines.

CircleCI

No public terms recorded here.

Review CircleCI SLA guide

GitHub

1 public term record.

Product not specified

Review GitHub SLA guide