Coordination service issues
This incident has been resolved.
The latest update from Tailscale.
State
Resolved
Started
1 d ago
2026-10-30 23:56 UTC
Lasted
44 min
until 2026-10-31 00:40 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
30 min 68%
Monitoring
14 min 32%
Updates
Times in UTCAs posted by Tailscale
This incident has been resolved.
A fix has been deployed and we are monitoring for any further problems.
We're continuing to investigate, and are seeing that some Aperture instances are facing issues.
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 historyIncidents in 90 days
19
Days with an incident
22
Median duration
2 h 50 min
This incident
74% shorter than the median
Other Tailscale incidents
All incidentsTailscale·Funnel hostnames not resolving in public DNS
This incident has been resolved.
Tailscale·Funnel hostnames not resolving in public DNS
This incident has been resolved.
Tailscale·Admin Panel Login Issues
This incident has been resolved.
Tailscale·Funnel performance degradation
This incident has been resolved.
Tailscale·Coordination service issues
This incident has been resolved.
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.
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.
https://outages.cc/feed.xml?providers=tailscale/feed subscribe https://outages.cc/feed.xml?providers=tailscaleFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane