Elevated PAM API latency and error rates
The Tailscale PAM API had elevated latency and error rates. Tailscale reports that the incident is resolved. It lasted 25 minutes.
State
Resolved
Started
Lasted
25 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
17 min 68%
Monitoring
8 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 are investigating elevated errors and latency increases with the Tailscale PAM API. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.
Tailscale in the last 90 days
Full historyIncidents in 90 days
15
Days with an incident
20
Median duration
1 h 3 min
This incident
61% shorter than the median
Other Tailscale incidents
All incidentsTailscale·DERP relay connection issues
Tailscale DERP relay servers in the NYC (1g) region had degraded connectivity. Tailscale deployed a fix and monitored the result. The incident is resolved and lasted 24 minutes.
Tailscale·DERP connection issues
Tailscale DERP servers in the NYC region (Region 1) had degraded connectivity. Tailscale rolled out a fix and monitored the result. The incident is resolved and lasted 18 minutes.
Tailscale·Funnel performance degradation
Tailscale Funnel had performance degradation and intermittent failures when users created new Funnel nodes and generated new TLS certificates. Tailscale reports that this incident is resolved. It lasted 63 minutes.
Tailscale·Coordination service issues
This incident has been resolved.
Tailscale·Funnel hostnames not resolving in public DNS
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.live/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.live/feed.xml?providers=tailscale/feed subscribe https://outages.live/feed.xml?providers=tailscaleFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane