- Level
- confirmed
- Worst impact
- Degraded
- Components
- API, GitHub, Linux and Windows Builds
- Down Index
- 21of 100
What to do
Check whether you use Travis CI API, GitHub, Linux and Windows Builds. 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 19m it lasted.
Anything that failed between 2020-03-24 13:41 UTC and 2020-03-24 15: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
- identified
The issue related to queued builds and build statuses is still partially down. We have investigated the issue and currently working on the components to up again.
provider
- resolved
Thank you for your patience and understanding. This incident has been resolved by taking another look and tests about builds statuses and build trigger mechanism. The solution was deployed at 14:00 PM UTC.
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-cbca2fcb58
Is Travis CI still down?
No, this incident was resolved 2020-03-24 15:00 UTC. For Travis CI's live state, see https://down.guide/travis-ci.
How long did it last?
1h 19m, from 2020-03-24 13:41 UTC to 2020-03-24 15:00 UTC, by the times Travis CI posted.
What was affected?
Travis CI named API, GitHub, 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.