Skip to main content
down.guideby Sazabi
Menu
Travis CI

Incident

Travis API errors.

Degraded Lasted 1h 18m · started · Travis CI's page

DWN-26f96efce6Travis CIResolved

Level
confirmed
Worst impact
Degraded
Components
API, Linux and Windows Builds
Down Index
20of 100

What to do

  • Check whether you use Travis CI API, Linux and Windows 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 1h 18m it lasted.

    Anything that failed between 2023-10-28 12:15 UTC and 2023-10-28 13:32 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 3

  1. investigating

    Travis API errors discovered. Builds may be breaking.

    provider

  2. monitoring

    Issue found and fixed. Monitoring system.

    provider

  3. resolved

    Operation back to normal.

    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-26f96efce6

Is Travis CI still down?

No, this incident was resolved 2023-10-28 13:32 UTC. For Travis CI's live state, see https://down.guide/providers/travis-ci.

How long did it last?

1h 18m, from 2023-10-28 12:15 UTC to 2023-10-28 13:32 UTC, by the times Travis CI posted.

What was affected?

Travis CI named API, Linux and Windows 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