Is Tailscale Down?

No — Tailscale is up

Reachable from all 8 checked regions

Average response time: 275ms

Last checked 3 hours ago · checks run every 6 hours

Official status page: https://status.tailscale.com

Tailscale uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

254ms

Avg response, 30 days

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

30-day history

55-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.

lax

288ms

DNS 94ms TCP 1ms TLS 22ms TTFB 273ms

lhr

202ms

DNS 19ms TCP 2ms TLS 9ms TTFB 190ms

nrt

274ms

DNS 118ms TCP 2ms TLS 10ms TTFB 222ms

ord

272ms

DNS 5ms TCP 1ms TLS 23ms TTFB 256ms

sin

187ms

DNS 76ms TCP 1ms TLS 10ms TTFB 179ms

sjc

245ms

DNS 57ms TCP 1ms TLS 7ms TTFB 235ms

syd

392ms

DNS 16ms TCP 1ms TLS 7ms TTFB 385ms

yyz

343ms

DNS 41ms TCP 11ms TLS 33ms TTFB 306ms

What Tailscale does

Tailscale builds a private mesh network between a company's machines using WireGuard, with a coordination service that distributes keys and routes and relay servers for connections that cannot go direct. Teams reach production servers and internal tools through it, so an incident can cut off administrative access exactly when it is needed.

What an outage looks like

New devices fail to join the network and existing ones cannot re-authenticate when their key expires. Connections that were already established often keep working, because traffic flows peer to peer rather than through Tailscale. Connections depending on relays degrade or drop. The admin console and API return errors, blocking access changes and device approvals.

What to do about it

Check status.tailscale.com, which lists the Coordination service, DERP relay servers, the admin console, the API and Certificates as separate components. Existing peer-to-peer connections usually survive a coordination outage, so avoid logging out, restarting the client, or rebooting machines: re-authentication needs the service that is currently down and is what actually removes your access.

Is it down for everyone, or just you?

If this page says Tailscale 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

Tailscale outage FAQ

Will I lose access to my servers if Tailscale goes down?

Usually not immediately. Tailscale sends traffic directly between machines, so tunnels already established keep carrying traffic during a coordination outage. What fails is anything needing the control plane: adding a device, re-authenticating an expired key, or changing access rules. Avoid restarting the client, since reconnecting requires the service that is unavailable.

Why did my connection drop when others stayed up?

Connections that cannot establish a direct path fall back to DERP relay servers, which Tailscale operates and reports as their own component. If your path depends on a relay, a relay incident drops it while colleagues on direct peer-to-peer connections notice nothing. Network topology, not account state, explains most of these uneven experiences.

What happens when a node key expires during an outage?

The device drops off the network and cannot rejoin until the coordination service returns, because re-authentication runs through it. This is the scenario that turns a mild incident into a lockout. Disabling key expiry on critical infrastructure, or keeping a separate emergency access path, is worth arranging before you need it rather than during.

Should I have a break-glass path that does not use Tailscale?

For anything you must reach during an incident, yes. A console through your cloud provider, a bastion on a public address with strong authentication, or physical access all serve. Tailscale becoming the sole route to production means a control plane incident and a production incident can arrive together, which is the situation worth designing out.

Does a Tailscale outage expose my network?

No. Traffic is encrypted end to end with WireGuard between your own machines, and a coordination outage means keys and routes are not being distributed rather than that anything is opened up. The failure mode is losing connectivity and the ability to change configuration, not losing the protection the network provides.

How we measure this

We request Tailscale's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 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 Tailscale 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 Tailscale 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