Skip to main content
down.guideby Sazabi
Menu
Travis CI

Incident

Builds not being processed

Degraded Lasted 3h 28m · started · Travis CI's page

DWN-1fd072172bTravis CIResolved

Level
confirmed
Worst impact
Degraded
Components
Linux and Windows Builds, IBM Z Builds
Down Index
22of 100

What to do

  • Check whether you use Travis CI Linux and Windows Builds, IBM Z Builds. Check your stack

    Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.

  • Confirm your retries, queues and scheduled jobs caught up after the 3h 28m it lasted.

    Anything that failed between 2024-08-28 22:31 UTC and 2024-08-29 02:00 UTC may need a replay.

  • Subscribe to Travis CI's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=travis-ci works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Travis CI 2

  1. investigating

    We are currently investigating an issue that is preventing some builds from working properly.

    provider

  2. resolved

    This issue has been resolved and now builds are running as expected.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-1fd072172b

Is Travis CI still down?

No, this incident was resolved 2024-08-29 02:00 UTC. For Travis CI's live state, see https://down.guide/providers/travis-ci.

How long did it last?

3h 28m, from 2024-08-28 22:31 UTC to 2024-08-29 02:00 UTC, by the times Travis CI posted.

What was affected?

Travis CI named Linux and Windows Builds, IBM Z Builds.

What caused it?

Travis CI hasn't published a root cause. If it does, it shows here.

Where does this come from?

Travis CI's official status page, https://www.traviscistatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.

Sources

Feed