Travis CI is up
Answered with HTTP 200 in 391 ms (good) — checked 0s ago.
Result is 0s old (cached for 60 seconds). Refresh · or run a full diagnostic on travis-ci.com.
It works here but not for you?
Our server reached Travis CI normally, so the outage is not global. Work through these in order:
- Hard-refresh the page (Ctrl+F5, or Cmd+Shift+R on a Mac) to bypass your browser cache.
- Try mobile data instead of Wi-Fi. If it loads, your broadband or router is the problem.
- Change your DNS resolver to 1.1.1.1 or 8.8.8.8 — ISP resolvers do sometimes hold broken records.
- Disable a VPN or ad-blocker temporarily; both can block a service entirely.
- Check your account — a suspended or region-blocked account looks exactly like an outage.
About this check
- Checked from
- London, United Kingdom
- Method
- Live HTTPS request + ICMP ping
- Address
- travis-ci.com
- Resolved IP
- 172.67.75.36
- Server
- cloudflare
- Redirects
- 1
- Last checked
- 07:24:02 UTC
We report only what our own request returned. We do not count user reports, so a single angry tweet cannot make this page say "down".
Is Travis CI down for everyone or just me?
That is the only question worth answering when a site stops loading, and it has a simple test: check it from a machine that shares none of your network. This page does exactly that — the request comes from our server in London, using its own DNS resolver and its own route to the internet. If travis-ci.com answers us, it is up, and whatever is stopping you sits between your device and the wider network.
Local causes are more common than real outages. A stale DNS entry, a router that needs a restart, an ISP resolver holding a bad record, a VPN exit node the service blocks, an ad-blocker rule, or simply a cached error page in your browser: each one produces a site that is "down" for exactly one person.
What a failed check actually means
When a check fails we name the stage that failed rather than saying "down", because the fixes are entirely different. DNS failure means the name could not be turned into an address — an expired domain or a broken nameserver change. Connection refused means the machine answered but nothing is listening: the web server process has stopped. Timeout means packets vanished — a firewall, a routing problem, or a server too loaded to accept connections. TLS error means the site is running but its certificate is expired or mismatched, and every browser will refuse it.
Other developer & infrastructure services
Check the live status of similar services:
Track Travis CI automatically
Free monitoring checks every 5 minutes and emails you when the status changes.