Skip to content

Outage tracker / Travis CI / In the US

Is Travis CI down in the US?

Vendor reports no incidentWhat Travis CI reports

Travis CI reports no incident on its status page.

As of the last successful poll, 2026-11-07 01:39 UTC.

Travis CI's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingin the US, measured from Ashburn and San Jose

All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Travis CI at Nov 7, 2026, 1:45 AM UTC.

Over the last 24 hours we completed 251 checks from Ashburn and San Jose and 243 answered cleanly, 96.81% availability.

Of the 2 other regions we check Travis CI from, all 2 read checks passing right now.

Email me when Travis CI reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Travis CI's own statement from its status page, with our regional reading beside it.

What our Ashburn and San Jose probes measured

AshburnChecks passing141 checks in 24h, 97.16%
San JoseChecks passing110 checks in 24h, 96.36%

Last checked Nov 7, 2026, 1:45 AM UTC.

Travis CI from Ashburn and San Jose over the last 30 days

Over the last 30 days, Travis CI answered our Ashburn probe in 911 ms on average, and 1 check in 20 took longer than 1,358 ms.

Over the last 30 days, Travis CI answered our San Jose probe in 1,125 ms on average, and 1 check in 20 took longer than 1,505 ms.

Ranked by average response time across the 4 cities we check Travis CI from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 865 ms and Tokyo slowest at 1,978 ms.

From Ashburn and San Jose we ran 1,123 checks of Travis CI in 6 days, and 1,077 answered cleanly: 95.90% availability.

6 of the 6 days had at least one failed check. The weakest was Nov 7 (UTC), at 93.75% across 16 checks.

In Ashburn local time (EST), Travis CI was slowest around 2 PM, at 1,627 ms on average over the last 14 days, and quickest around 9 PM, at 637 ms.

Day (UTC)ChecksAvailabilityAverage response
Sat, Nov 71693.75%887 ms
Fri, Nov 625296.42%1,101 ms
Thu, Nov 525195.21%948 ms
Wed, Nov 425296.82%944 ms
Tue, Nov 324894.75%1,010 ms
Mon, Nov 210497.11%1,057 ms

Travis CI outages measured from the US

Our Ashburn and San Jose probes measured no confirmed Travis CI outage in the last 90 days.

How the other regions read right now

Of the 2 other regions we check Travis CI from, all 2 read checks passing right now.

Probe cityRight nowLast 24h
FrankfurtChecks passing95.95% of 99 checks
TokyoChecks passing84.74% of 59 checks

Other countries we check Travis CI from

How we measured this

The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Travis CI's public endpoints. They are not user reports, and they are not Travis CI's own status page.

See Travis CI's full check readings, the 90-day history by region, or the outage tracker methodology.

The US readings here are taken from that country and show the time of the last one, but Travis CI has not yet accumulated enough continuous history for us to publish this page to search engines.

Check your own site from Ashburn

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter