- Level
- confirmed
- Worst impact
- Degraded
- Components
- GitHub Issues, PRs, Dashboard, Projects
- Down Index
- 23of 100
What to do
Check whether you use Travis CI GitHub Issues, PRs, Dashboard, Projects. 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 6h 27m it lasted.
Anything that failed between 2023-11-16 10:30 UTC and 2023-11-16 16:56 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
Issues with branch/tag based builds reported since Nov-9 have been confirmed to be on Travis CI side. We have identified the reason and confirmed it's due to GitHub push event handling on Travis CI side. Working on the fix. Build infrastructure is fully operational
provider
- monitoring
A fix for handling GitHub push events was implemented and we are monitoring the system now.
provider
- resolved
Incident 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-d92c331937
Is Travis CI still down?
No, this incident was resolved 2023-11-16 16:56 UTC. For Travis CI's live state, see https://down.guide/travis-ci.
How long did it last?
6h 27m, from 2023-11-16 10:30 UTC to 2023-11-16 16:56 UTC, by the times Travis CI posted.
What was affected?
Travis CI named GitHub Issues, PRs, Dashboard, Projects.
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.