Travis CI outage, 25 May 2026

Build job(s) failures

Started
Resolved
25 May 2026, 19:26 UTC (after 5 h 13 min)
Impact
Minor
Affected
Log Processing, Notifications, Linux and Windows Builds, IBM Z Builds

Is this still happening?

No. Travis CI marked this incident resolved on 25 May 2026, 19:26 UTC, 5 h 13 min after it began.

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

Last update from Travis CI

The fix has been successful, and all systems are now operating normally. We will continue to monitor performance closely. Thank you for your patience and understanding as we addressed this issue. If you continue to experience any residual issues or have further questions, please reach out to our team at support@travis-ci.com

25 May 2026, 19:26 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 3 h 28 min

    Builds not being processed

  2. , resolved after 6 h 53 min

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

  3. , resolved after 55 min

    Some builds are not being triggerred

  4. , resolved after 21 min

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

  5. , resolved after 3 h 4 min

    Builds are not triggering for 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. Travis API errors.

All recorded Travis CI incidents