Tailscale reported "Coordination service issues" on its status page at 2026-08-20 00:58 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-20 00:58 UTC and ended at 2026-08-20 03:22 UTC. It lasted 2 h 24 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-20 00:58 UTC

Coordination service issues

ResolvedOfficial update

This incident has been resolved.

The latest update from Tailscale.

State

Resolved

Started

73 d ago

2026-08-20 00:58 UTC

Lasted

2 h 24 min

until 2026-08-20 03:22 UTC

Worst impact

Partial outage

Timeline

4 updates

00:5801:3402:1002:4603:22

Partial outageUpdate postedTimes in UTC

Investigating

55 min 38%

Identified

45 min 32%

Monitoring

44 min 30%

Updates

Times in UTC

As posted by Tailscale

Resolved2026-08-20 03:22 UTC

This incident has been resolved.

Monitoring2026-08-20 02:38 UTC

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

Identified2026-08-20 01:53 UTC

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

Investigating2026-08-20 00:58 UTC

We are investigating a problem causing an elevated rate of errors in our coordination service, and are working to understand the full impact of the problem.

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

15% shorter than 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