Is Travis CI Down?

No — Travis CI is up

Travis CI's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 573 ms

Right now

The verdict is the worse of these two. How we decide

Travis CI's status page

traviscistatus.com · read 2 minutes ago · checked every 3 minutes

Operational

Travis CI's components, as its status page reports them
Component	Status
Log Processing	Operational
User Sync	Operational
Notifications	Operational
API	Operational
Web App	Operational
Google Cloud Platform Google Compute Engine	Operational
GitHub API Requests	Operational
GitHub Issues, PRs, Dashboard, Projects	Operational
Assembla API and Merge Requests	Operational
GitLab API and Pull Requests	Operational
GitHub	Operational
DNSimple Name Servers	Operational

9 more, all operational · show all 21

All of Travis CI's components
Component	Status
Background Processing
Log Processing	Operational
User Sync	Operational
Notifications	Operational
API	Operational
Web App	Operational
Google Cloud Platform Google Compute Engine	Operational
GitHub API Requests	Operational
GitHub Issues, PRs, Dashboard, Projects	Operational
Assembla API and Merge Requests	Operational
GitLab API and Pull Requests	Operational
Third Party Services
GitHub	Operational
DNSimple Name Servers	Operational
Pusher Pusher REST API	Operational
Pusher WebSocket client API	Operational
Pusher Presence channels	Operational
Pusher Webhooks	Operational
PagerDuty Notification Delivery	Operational
npm, Inc. Registry Reads	Operational
Assembla	Operational
Builds Processing
Linux and Windows Builds	Operational
IBM Z Builds	Operational

1 location All operational

Open their status page

FlareWarden checks

travis-ci.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 573 ms
Checked: 5 hours ago

By region

Ashburn reachable, 110 ms
Chicago reachable, 225 ms
Johannesburg reachable, 990 ms
London reachable, 471 ms
Los Angeles reachable, 467 ms
San Jose reachable, 405 ms
Singapore reachable, 1157 ms
Tokyo reachable, 764 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	29 ms	1 ms	13 ms	107 ms
Chicago	39 ms	15 ms	22 ms	184 ms
Johannesburg	19 ms	1 ms	8 ms	986 ms
London	50 ms	4 ms	15 ms	461 ms
Los Angeles	148 ms	2 ms	9 ms	460 ms
San Jose	81 ms	3 ms	8 ms	396 ms
Singapore	117 ms	2 ms	23 ms	1152 ms
Tokyo	78 ms	1 ms	8 ms	758 ms

We check that travis-ci.com loads, not every feature behind it. Test it yourself

History

Incidents Travis CI reported

Since Oct 22, 15 days · from traviscistatus.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Travis CI website availability

Measured by FlareWarden · travis-ci.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 520ms

Last 30 days

73-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of travis-ci.com from multiple regions every 6 hours. Travis CI's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 73 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 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 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Travis CI itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Travis CI goes down

We check Travis CI every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required