- Level
- confirmed
- Worst impact
- Operational
What to do
Check whether your product depends on Travis CI. 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 11h 23m it lasted.
Anything that failed between 2019-11-19 08:13 UTC and 2019-11-19 19:36 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
- investigating
We are investigating an issue with IBM Z builds.
provider
- monitoring
We are seeing builds on IBM Z starting normally. A fix for both .com and .org has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved.
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-2493e058d1
Is Travis CI still down?
No, this incident was resolved 2019-11-19 19:36 UTC. For Travis CI's live state, see https://down.guide/providers/travis-ci.
How long did it last?
11h 23m, from 2019-11-19 08:13 UTC to 2019-11-19 19:36 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.