Travis CI outage, 24 March 2023

Build job errors when acquiring repository from GitHub (GitHub SSH key update)

Started
Resolved
24 Mar 2023, 17:05 UTC (after 6 h 53 min)
Impact
Minor
Affected
GitHub, Linux and Windows Builds

Is this still happening?

No. Travis CI marked this incident resolved on 24 Mar 2023, 17:05 UTC, 6 h 53 min after it began.

Right now: Travis CI reports all systems operational. (as of 30 Oct, 11:38 UTC) Live Travis CI status

Last update from Travis CI

The issue seems resolved. If you encounter further roadbloacks in repositories using Custom SSH Key in Travis CI, specifically on git repository cloning stage, please validate if a matching key pair is still available at GitHub. If not, removing old Custom SSH Key in Travis CI repository settings and regenerating the Custom SSH Key in Travis CI may help unblock your build jobs.

24 Mar 2023, 17:05 UTC

Read the full incident on the official Travis CI status page

Similar Travis CI incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved after 5 h 13 min

    Build job(s) failures

  2. , resolved after 3 h 28 min

    Builds not being processed

  3. , resolved after 1 h 17 min

    Travis API errors.

  4. , resolved after 55 min

    Some builds are not being triggerred

  5. , resolved after 21 min

    Builds are not triggering for app.travis-ci.com

Other recent Travis CI incidents

  1. Trials not working

  2. arm64 jobs not running

  3. DPLv2 dependency update causes DPLv2 deployments to fail

  4. s390x and ppc64le jobs not running

  5. macOS builds failing

  6. Build jobs from branches/tags on GitHub ran on main/master branch in Travis CI

  7. GitHub sync blocked or lasting long - degraded performance

  8. Synchronization with GitHub fails

All recorded Travis CI incidents