Tailscale Outage History

An outage affected the Tailscale homepage and documentation site (tailscale.com) starting at 9:13 PM UTC and lasting about 10 minutes, with access restored by 9:23 PM UTC. The disruption likely prevented users from loading the main site and documentation pages during that window, though the broader Tailscale service remained unaffected. The incident was confined to the tailscale.com surface. The Tailscale status page showed the Homepage and Documentation component transitioning from up to down and back to up, with two official status updates issued over the course of the incident.

The Tailscale package server pkgs.tailscale.com experienced increased latency and timeouts, causing download delays for some users. The incident began at 12:37 PM UTC and was resolved by 1:18 PM UTC, lasting about 41 minutes. The issue was isolated to the Package server component, with no broader impact on other Tailscale services.

Two official updates were posted: an initial warning about degraded downloads, followed by a resolution indicating the service had returned to normal.

Tailscale experienced an incident where configuration updates propagated more slowly than usual, impacting a subset of tailnets. Changes to tailnet membership (such as new nodes joining) were delayed by up to about a minute, which in turn caused login and startup issues for some users. The outage began at Jan 13, 2025 3:43 PM UTC and lasted for roughly 7 hours and 45 minutes, concluding with the Coordination server returning to normal. User reports surfaced around 9:30 PM UTC, describing problems like cannot login and startup hangs, with mentions of errors such as

Tailscale experienced degraded performance due to elevated configuration propagation latency, affecting some tailnets. Changes to tailnet membership, such as new nodes joining, propagated with a delay of up to one minute, causing intermittent delays for users updating their tailnets. The Coordination server was the affected component during this event.

Timeline and recovery: The incident began at 3:32 PM UTC when Tailscale flagged the degraded latency, and it was resolved by 4:54 PM UTC as services returned to normal. The provider issued two official status updates during the incident, describing the latency issue and subsequent mitigation steps. Earlier communications noted mitigations implemented in December 2024, including an extended service restart to perform data storage maintenance in a bid to improve latency.