Tailscale reported "Issues with browser-based Tailscale clients" on its status page at 2026-08-19 05:53 UTC.

Tailscale did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-08-19 05:53 UTC and ended at 2026-08-19 09:22 UTC. It lasted 3 h 29 min.

How do I get alerts for Tailscale?

Subscribe to the Tailscale live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Tailscale. outages.live reads it every few minutes and keeps every update.

TailscaleIncident · 2026-08-19 05:53 UTC

Issues with browser-based Tailscale clients

ResolvedOfficial update

This incident has been resolved.

The latest update from Tailscale.

State

Resolved

Started

74 d ago

2026-08-19 05:53 UTC

Lasted

3 h 29 min

until 2026-08-19 09:22 UTC

Worst impact

Degraded

Timeline

4 updates

05:5306:4507:3708:3009:22

DegradedUpdate postedTimes in UTC

Investigating

43 min 21%

Identified

2 h 18 min 66%

Monitoring

28 min 13%

Updates

Times in UTC

As posted by Tailscale

Resolved2026-08-19 09:22 UTC

This incident has been resolved.

Monitoring2026-08-19 08:54 UTC

A fix has been deployed and we are monitoring for any further problems.

Identified2026-08-19 06:36 UTC

We have identified the problem and are rolling out a fix.

Investigating2026-08-19 05:53 UTC

We are investigating an issue causing problems with connections from browser-based Tailscale clients, including Tailscale SSH via the Tailscale console.

Tailscale in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

2 h 50 min

This incident

1.2× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

2 days

median 2 h 50 min

90 days agoToday

Other Tailscale incidents

All incidents

Tailscale·Coordination service issues

This incident has been resolved.

Resolvedresolved 1 d ago

Tailscale·Funnel hostnames not resolving in public DNS

This incident has been resolved.

Resolvedresolved 3 d ago

Tailscale·Funnel hostnames not resolving in public DNS

This incident has been resolved.

Resolvedresolved 6 d ago

Tailscale·Admin Panel Login Issues

This incident has been resolved.

Resolvedresolved 24 d ago

Tailscale·Funnel performance degradation

This incident has been resolved.

Resolvedresolved 29 d ago

Follow Tailscale

Your coding agent knows when Tailscale is down, and tells you when a failure is theirs, not yours. You can also get Tailscale incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "tailscale" and tell me if Tailscale has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.cc/feed.xml?providers=tailscale

Slack

/feed subscribe https://outages.cc/feed.xml?providers=tailscale

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane