Is Travis CI Down?

No — Travis CI is up

Reachable from all 7 checked regions

Average response time: 603ms

Last checked 1 hour ago · checks run every 6 hours

Official status page: https://www.traviscistatus.com

Travis CI uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

476ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 27 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

27-day clean streak

Aug 22 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

1144ms

DNS 32ms TCP 2ms TLS 11ms TTFB 1029ms

arn

573ms

DNS 93ms TCP 1ms TLS 12ms TTFB 566ms

nrt

810ms

DNS 122ms TCP 1ms TLS 11ms TTFB 803ms

ord

255ms

DNS 67ms TCP 1ms TLS 11ms TTFB 180ms

sin

1045ms

DNS 16ms TCP 2ms TLS 13ms TTFB 1038ms

sjc

216ms

DNS 30ms TCP 2ms TLS 12ms TTFB 203ms

yyz

184ms

DNS 30ms TCP 2ms TLS 7ms TTFB 158ms

What Travis CI does

Travis CI runs automated builds and deployments from a .travis.yml file kept in the repository. It tests across Linux, macOS and Windows and on amd64, arm64, ppc64le and s390x processors, which is why open-source projects with wide platform support have long relied on it. Builds are triggered by repository activity, so it sits between a commit and whatever that commit was meant to release.

What an outage looks like

Pushes and pull requests stop producing builds, or builds queue and never start. Jobs finish but their logs never appear, since log processing is a separate stage. The web app fails to load build history, and status checks stay pending on pull requests, which blocks merges. Deployment steps at the end of a passing build do not fire, so a green build ships nothing.

What to do about it

Read www.traviscistatus.com, which separates Builds Processing, Linux and Windows Builds, IBM Z Builds, Log Processing, Background Processing, User Sync, the API and the Web App. It also reports third party dependencies, including GitHub, the npm registry, Pusher, DNSimple and AWS ec2-us-east-1. Check that section first: a stalled build is often an upstream fault rather than Travis, and re-running it will not help.

Is it down for everyone, or just you?

If this page says Travis CI is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Travis CI outage FAQ

Is it Travis CI or GitHub that is broken?

The Travis status page answers this directly, which is unusual. Alongside its own components it reports third party services including GitHub API Requests, GitHub Issues and Pull Requests, the npm registry, Assembla, GitLab and Google Compute Engine. If a build is stuck fetching code or installing packages, check those rows before assuming Travis is at fault, because the fix and the wait are different.

Why are my pull request checks stuck as pending?

Because the check is reported back to the repository host once a build finishes, and a build that never started or never reported leaves the check hanging. This blocks merges even though nothing is wrong with the code. Builds Processing, Notifications and the API are separate components on the status page, and any of them failing can leave checks pending.

Do my builds still run if only the web app is down?

Often yes. Web App is listed as a separate component from Builds Processing, so the interface can be unreachable while builds continue to run and deployments continue to fire. The reverse also happens: the site loads and shows history while new builds do not start. Read the specific component rather than the overall banner at the top.

Does an outage affect builds on all architectures?

Not necessarily. Travis reports Linux and Windows Builds and IBM Z Builds as separate components, so a failure can be limited to one build environment. Projects that test across amd64, arm64, ppc64le and s390x may see part of the matrix fail while the rest passes, which looks like a flaky test rather than an infrastructure incident.

How we measure this

We request Travis CI's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 7 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Travis CI publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Travis CI goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required