- Level
- confirmed
- Worst impact
- Major outage
- Components
- API
- Down Index
- 41of 100
What to do
Check whether you use Travis CI API. 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 36m it lasted.
Anything that failed between 2020-03-27 20:14 UTC and 2020-03-27 21:51 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
- investigating
We are investigating an outage on the .ORG API. We will provide updates based on our findings. Thank you
provider
- monitoring
We implemented a fix for the issue and are monitoring the results. Thank you
provider
- monitoring
We are continuing to monitor our infrastructure and one of our upstream providers, Google [1]. We will provide additional updates once these systems are fully functional. Thank you [1] https://status.cloud.google.com/incident/cloud-networking/20004
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-da6727347b
Is Travis CI still down?
No, this incident was resolved 2020-03-27 21:51 UTC. For Travis CI's live state, see https://down.guide/travis-ci.
How long did it last?
1h 36m, from 2020-03-27 20:14 UTC to 2020-03-27 21:51 UTC, by the times Travis CI posted.
What was affected?
Travis CI named API.
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.