Tailscale Outage History

Tailscale experienced a brief degradation of the Certificates component, likely affecting certificate validation and related services for a short period. The issue began at 2:38 PM UTC and was resolved by 2:58 PM UTC, resulting in about a 20 minute outage window. The problem appeared confined to the Certificates component and did not indicate a broader platform disruption. End users may have noticed intermittent certificate-related failures during this interval.

The Tailscale status page published two updates documenting the degradation and the subsequent restoration. The incident was relatively short with limited impact but notable enough to be acknowledged by the status page.

The Nuremberg (NUE) DERP region was unavailable between 10:00 AM UTC and 10:30 AM UTC, causing degraded relaying performance for traffic routed through adjacent regions and impacting DERP relay servers. The impact was regional to NUE with cross-region load increases in surrounding DERP nodes. Two official status updates were issued during the incident: the first at Mar 20, 2025 11:28 AM UTC moving from up to warn, and the second at Mar 20, 2025 12:38 PM UTC returning to up, with full recovery by Mar 20, 2025 12:38 PM UTC.

On Mar 19, 2025 8:13 PM UTC, Tailscale reported degraded intra-region packet relaying in the Helsinki DERP region. A subset of Helsinki DERP nodes were failing to relay packets within the region, and those nodes were taken out of service while investigators worked. The Admin Console (login.tailscale.com) appeared degraded during the incident. The outage began at Mar 19, 2025 8:13 PM UTC and was resolved by Mar 19, 2025 8:38 PM UTC, lasting approximately 25 minutes. The provider issued 2 status updates during the event.

Geographic impact was localized to the Helsinki DERP region, with no broader regions reported affected in the updates.

Tailscale reported a brief impairment in the Admin Console (login.tailscale.com) that prevented some users from sharing their machines with others, limiting collaborative access. The issue was under investigation and described as a temporary degradation of sharing functionality.

The incident began at 3:48 PM UTC and was resolved by 5:08 PM UTC, lasting roughly 1 hour and 20 minutes. The provider issued 2 status updates during the incident, communicating the investigation and eventual restoration of sharing capabilities. The Admin Console returned to normal after services were restored.

The outage began on 12:13 PM UTC and was resolved by 12:38 PM UTC. It affected the log upload path and API endpoints that query logs, causing log uploads to fail. A mitigation was deployed to restore functionality, and the api.tailscale.com component returned to normal after the underlying issue was addressed. The incident appeared limited in scope, impacting log ingestion and log-querying functionality and was resolved in about 25 minutes.

An outage affected the Tailscale package server, pkgs.tailscale.com, during a brief maintenance restart. During the restart, some queries to the package server may have been interrupted or timed out. The incident started at Mar 4, 2025 1:12 AM UTC and was resolved by Mar 4, 2025 1:20 AM UTC, lasting about 8 minutes.

The provider issued 2 status updates during the incident, describing the maintenance restart and later confirming the package server was back to normal. The impact was limited to the package server, with no broader components affected.

Tailscale reported degraded performance in its DERP relay network, affecting the Nuremberg and Ashburn regions where relays were partially unreachable. This caused slower relaying and intermittent connectivity for users relying on those DERP nodes. The issue began at Feb 25, 2025 11:58 PM UTC and lasted for about 1 hour and 25 minutes before resolving by Feb 26, 2025 1:23 AM UTC. The incident included two official status updates during its course, describing the degradation and subsequent restoration of normal DERP relay operation.

The incident began on Feb 18, 2025 4:47 PM UTC when the Coordination server entered a degraded state, impacting coordination-related functionality and causing tailscale.com to be slow or fail to load for some users. User reports around that time described site access issues and dropped connections.

On Feb 20, 2025 12:38 PM UTC the package server pkgs.tailscale.com experienced increased latency and timeouts affecting downloads, with the Coordination server also showing instability before recovering. The provider issued four status updates documenting investigation progress and subsequent recovery across two components: Coordination server and Package server (pkgs.tailscale.com). The outage lasted roughly 44 hours and 51 minutes, with services restored by Feb 20, 2025 1:38 PM UTC.

An outage hit Tailscale's control plane, taking down login and inter-service communication. The Admin Console (login.tailscale.com), API (api.tailscale.com), and Coordination server were affected, causing login failures and impaired connectivity for many users. StatusGator detected an Early Warning Signal at Feb 13, 2025 6:11 PM UTC indicating connectivity issues before the official acknowledgment, which came at Feb 13, 2025 6:28 PM UTC. The Early Warning Signal lasted until Feb 13, 2025 6:30 PM UTC, providing about 17 minutes of lead time.

Official updates showed the issue persisted from Feb 13, 2025 6:28 PM UTC, with three status updates during the incident. On Feb 13, 2025 6:46 PM UTC the underlying cause was identified and a fix began deployment. The service began returning to normal by Feb 13, 2025 7:33 PM UTC, with Admin Console, API, and Coordination server transitioning to up. The outage lasted roughly 1 hour and 5 minutes, with a notable surge in user reports around 6:15 PM UTC indicating broad impact.

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.