Skip to main content
Travis CI

travis-ci.com throws "504 Gateway Timeout" error

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

Level
confirmed
Worst impact
Degraded
Down Index
18of 100

What to do

  • Check whether your product depends on Travis CI. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 1h 25m it lasted.

    Anything that failed between 2021-09-06 13:38 UTC and 2021-09-06 15:04 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. identified

    The main page at https://travis-ci.com is down. Your builds are still executed. We're reviewing the main site case, it may remain inactive for a full day or so. The API and https://app.travis-ci.com can be still accessed directly and you can run, view, and manage your builds as usual.

    provider

  2. resolved

    The main site https://travis-ci.com/ is back on field.

    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-893ac89cf9

Is Travis CI still down?

No, this incident was resolved 2021-09-06 15:04 UTC. For Travis CI's live state, see https://down.guide/travis-ci.

How long did it last?

1h 25m, from 2021-09-06 13:38 UTC to 2021-09-06 15:04 UTC, by the times Travis CI posted.

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.