Skip to main content
Tailscale logo

Is Tailscale Down?

No — Tailscale is up

Reachable from all 8 checked regions

Average response time: 230ms

Last checked · 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
225ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 1 day measured so far. A dash means we have no measurement for that window.

30-day history

Jun 29: no data
Jun 30: no data
Jul 1: no data
Jul 2: no data
Jul 3: no data
Jul 4: no data
Jul 5: no data
Jul 6: no data
Jul 7: no data
Jul 8: no data
Jul 9: no data
Jul 10: no data
Jul 11: no data
Jul 12: no data
Jul 13: no data
Jul 14: no data
Jul 15: no data
Jul 16: no data
Jul 17: no data
Jul 18: no data
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: 100.00% uptime, 16 checks
Jun 29 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
120ms
DNS 0ms TCP 1ms TLS 25ms TTFB 107ms
arn
226ms
DNS 0ms TCP 0ms TLS 75ms TTFB 179ms
lhr
167ms
DNS 5ms TCP 1ms TLS 50ms TTFB 142ms
nrt
87ms
DNS 1ms TCP 1ms TLS 10ms TTFB 81ms
ord
216ms
DNS 0ms TCP 1ms TLS 66ms TTFB 174ms
sin
620ms
DNS 0ms TCP 0ms TLS 207ms TTFB 415ms
sjc
230ms
DNS 0ms TCP 0ms TLS 61ms TTFB 154ms
syd
143ms
DNS 45ms TCP 0ms TLS 7ms TTFB 140ms
yyz
202ms
DNS 0ms TCP 0ms TLS 64ms TTFB 162ms

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 all 18 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 — 8 of them answered the most recent check.
  • 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, and let it override us in both directions.

Get alerted when Tailscale goes down

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

Start Free Monitoring
Free plan available No credit card required