- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 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 6d it lasted.
Anything that failed between 2024-08-23 13:58 UTC and 2024-08-29 14:23 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 have identified an issue that is preventing s390x and ppc64le jobs from running correctly. We’re actively working to address this problem.
provider
- identified
Bionic and Focal builds should work now, fix deployed.
provider
- resolved
This incident has been resolved for Bionic and Focal builds. We're working on Jammy builds that should be fixed soon, updates will be posted to our changelog page.
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-fa313d1cf5
Is Travis CI still down?
No, this incident was resolved 2024-08-29 14:23 UTC. For Travis CI's live state, see https://down.guide/travis-ci.
How long did it last?
6d, from 2024-08-23 13:58 UTC to 2024-08-29 14:23 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.