- Level
- confirmed
- Worst impact
- Degraded
- Components
- Linux and Windows Builds
- Down Index
- 19of 100
What to do
Check whether you use Travis CI 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 21m it lasted.
Anything that failed between 2019-07-08 21:26 UTC and 2019-07-08 22:47 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 4
- identified
We have received reports of delayed posting of Github Statuses. We are working to clear the backlog of such that should have been sent out.
provider
- identified
We have cleared the back logs, and most status have now been posted. If your GitHub Apps is not posting statuses, please try disabling and re-enabling the repository, and restarting (parts of) the affected builds.
provider
- monitoring
A fix 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-60c3281df8
Is Travis CI still down?
No, this incident was resolved 2019-07-08 22:47 UTC. For Travis CI's live state, see https://down.guide/providers/travis-ci.
How long did it last?
1h 21m, from 2019-07-08 21:26 UTC to 2019-07-08 22:47 UTC, by the times Travis CI posted.
What was affected?
Travis CI named 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.