- Level
- confirmed
- Worst impact
- Partial outage
- 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 0m it lasted.
Anything that failed between 2022-05-17 06:21 UTC and 2022-05-17 03: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 1
- resolved
Some of the build requests they both triggered with API and Git push operations are not being processed. We are still investigating the root cause behind this issue.
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-23b2af6b26
Is Travis CI still down?
No, this incident was resolved 2022-05-17 03:00 UTC. For Travis CI's live state, see https://down.guide/travis-ci.
How long did it last?
0m, from 2022-05-17 06:21 UTC to 2022-05-17 03:00 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.