- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 27of 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 49m it lasted.
Anything that failed between 2020-03-22 16:23 UTC and 2020-03-22 17:12 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
- identified
We have identified an issue with a portion of Mac infrastructure which prevents builds from running correctly. We are working on mitigating the impact of this problem. Affected jobs would indicate "An error occurred while generating the build script." in the logs.
provider
- monitoring
We have removed the affected hardware out of the executor pool. Requests should work as expected at this time.
provider
- resolved
The Mac build capacity has been brought back to normal.
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-02bbe29476
Is Travis CI still down?
No, this incident was resolved 2020-03-22 17:12 UTC. For Travis CI's live state, see https://down.guide/travis-ci.
How long did it last?
49m, from 2020-03-22 16:23 UTC to 2020-03-22 17:12 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.