Is Tailscale Down?

No — Tailscale is up

Tailscale's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 285 ms

Right now

The verdict is the worse of these two. How we decide

Tailscale's status page

status.tailscale.com · read 3 minutes ago · checked every 3 minutes

Operational

Tailscale's components, as its status page reports them
Component	Status
Admin console (console.tailscale.com)	Operational
API (api.tailscale.com)	Operational
Coordination service	Operational
DERP relay servers	Operational
Certificates	Operational
Mullvad exit nodes	Operational
Homepage and Documentation (tailscale.com)	Operational
Package server (pkgs.tailscale.com)	Operational
Funnel	Operational
Aperture	Operational
Tailscale Support	Operational
Portal	Operational

3 more, all operational · show all 15

All of Tailscale's components
Component	Status
Admin console (console.tailscale.com)	Operational
API (api.tailscale.com)	Operational
Coordination service	Operational
DERP relay servers	Operational
Certificates	Operational
Mullvad exit nodes	Operational
Homepage and Documentation (tailscale.com)	Operational
Package server (pkgs.tailscale.com)	Operational
Funnel	Operational
Aperture	Operational
Tailscale Support	Operational
Portal	Operational
Tunnel	Operational
Website	Operational
HTTP Socket	Operational

3 locations All operational

Open their status page

FlareWarden checks

tailscale.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 285 ms
Checked: 1 hour ago

By region

Ashburn reachable, 331 ms
Frankfurt reachable, 176 ms
Johannesburg reachable, 639 ms
London reachable, 152 ms
Los Angeles reachable, 228 ms
Newark reachable, 330 ms
São Paulo reachable, 230 ms
Tokyo reachable, 196 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	88 ms	3 ms	6 ms	321 ms
Frankfurt	10 ms	2 ms	7 ms	154 ms
Johannesburg	83 ms	1 ms	75 ms	599 ms
London	27 ms	3 ms	7 ms	141 ms
Los Angeles	24 ms	2 ms	24 ms	215 ms
Newark	63 ms	9 ms	12 ms	304 ms
São Paulo	81 ms	1 ms	6 ms	185 ms
Tokyo	60 ms	2 ms	9 ms	191 ms

We check that tailscale.com loads, not every feature behind it. Test it yourself

History

Incidents Tailscale reported

Since Oct 22, 15 days · from status.tailscale.com

Incidents: 4
Major or critical: 0
Median to resolve: 21h 23m

Funnel performance degradation
minor · Nov 5
lasted 1h 3m
Coordination service issues
minor · Oct 30
lasted 44m
Funnel hostnames not resolving in public DNS
minor · Oct 27
lasted 2d
Funnel hostnames not resolving in public DNS
minor · Oct 24
lasted 1d 17h

Tailscale website availability

Measured by FlareWarden · tailscale.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 309ms

Last 30 days

91-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of tailscale.com from multiple regions every 6 hours. Tailscale's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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 the verdict is the worse of what it reports and what our checks see: a major outage of Tailscale itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Tailscale goes down

We check Tailscale every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required