Skip to main content
Tailscale logo

Is Tailscale Down?

No — Tailscale is up

Reachable from all 8 checked regions

Average response time: 237ms

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
261ms
Avg response, 30 days

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

30-day history

22-day clean streak
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
Jul 29: 100.00% uptime, 32 checks
Jul 30: 100.00% uptime, 32 checks
Jul 31: 100.00% uptime, 32 checks
Aug 1: 100.00% uptime, 32 checks
Aug 2: 100.00% uptime, 32 checks
Aug 3: 100.00% uptime, 24 checks
Aug 4: 100.00% uptime, 22 checks
Aug 5: 100.00% uptime, 31 checks
Aug 6: 100.00% uptime, 40 checks
Aug 7: 100.00% uptime, 32 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 37 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 40 checks
Aug 16: 100.00% uptime, 40 checks
Aug 17: 100.00% uptime, 32 checks
Aug 18: 100.00% uptime, 32 checks
Jul 20 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.

ewr
207ms
DNS 67ms TCP 6ms TLS 12ms TTFB 197ms
fra
141ms
DNS 11ms TCP 1ms TLS 9ms TTFB 129ms
gru
140ms
DNS 15ms TCP 3ms TLS 8ms TTFB 127ms
iad
311ms
DNS 112ms TCP 1ms TLS 8ms TTFB 284ms
jnb
569ms
DNS 6ms TCP 0ms TLS 75ms TTFB 531ms
lax
168ms
DNS 9ms TCP 0ms TLS 24ms TTFB 147ms
lhr
139ms
DNS 29ms TCP 1ms TLS 10ms TTFB 133ms
nrt
137ms
DNS 36ms TCP 1ms TLS 9ms TTFB 130ms
ord
298ms
DNS 104ms TCP 1ms TLS 25ms TTFB 283ms

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

Cloudflare
Cloudflare
Okta
Okta
1Password
1Password
Fly.io
Fly.io

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. 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 the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required