Tailscale Outage History

Tailscale experienced a brief outage of its Coordination server, which disrupted login and admin console access for users worldwide. The outage began at 6:42 AM UTC and was resolved by 7:03 AM UTC, lasting about 21 minutes. StatusGator detected early user reports starting at Jun 30, 2025 6:31 AM UTC, roughly 11 minutes before the provider acknowledged the problem.

The official updates show the Coordination server moving from up to down at 06:42 UTC and returning to up at 07:03 UTC, with the incident requiring two status updates from Tailscale. User reports came from many regions, indicating a globally distributed impact including login failures and admin console access issues, with some mentions of DNS resolution problems.

Tailscale reported a partial outage affecting sign-in with Apple accounts for a small number of users accessing the Admin Console (login.tailscale.com). Users attempting to sign in with Apple IDs may have encountered authentication failures.

The incident began at 10:33 AM UTC with an initial investigation, and the Admin Console was listed as impacted. A subsequent update at 12:28 PM UTC indicated the issue was resolved and the Admin Console returned to normal operation. In total, two official status updates were published during the incident.

Overall impact was limited to Apple-based sign-in for the Admin Console; no broader service disruption reported. The incident duration was approximately 1 hour 55 minutes.

Tailscale experienced degraded performance in the Nuremberg DERP region with partial unavailability of DERP relay servers. Users relying on that DERP for routing may have seen slower connections or intermittent issues during the incident. The outage began at 1:27 PM UTC and was resolved by 3:03 PM UTC, lasting approximately 1 hour 36 minutes. The service published two status updates during the incident, noting that the Nuremberg DERP region was partially unavailable while the root cause was investigated, and subsequently returned to normal once the problem was resolved.

An outage affected Tailscale services, impacting API (api.tailscale.com), the coordination server, and the Admin console (login.tailscale.com). Users attempting API calls, authentication, or dashboard access could experience errors during the incident. The outage began on 7:18 PM UTC and lasted about 45 minutes, with services restored by 8:03 PM UTC.

Two official status updates were posted as the incident progressed, noting the affected components and restoration. The outage affected three core components and was observed by user reports beginning around 7:00 PM UTC UTC, indicating widespread impact before resolution. All services returned to normal after the incident.

The Tailscale admin site experienced a brief outage affecting the admin console for approximately five minutes. The incident began at 7:11 PM UTC and was resolved by 7:16 PM UTC. StatusGator detected the issue at Jun 2, 2025 7:11 PM UTC. A handful of user reports originated around 7:00 PM UTC, describing the admin site not loading or being unavailable, with some posts indicating backend or cookie-related errors. The problem appeared to be short-lived, with access restored by the end of the window; the incident did not trigger published updates on Tailscale's status page during the event.

The Tailscale authentication service experienced a brief disruption, preventing users from logging in across multiple regions. The outage began at May 23, 2025 6:28 PM UTC and was resolved by May 23, 2025 6:39 PM UTC, lasting about 11 minutes. User reports from Minnesota, Singapore, Vancouver, Washington DC, Paris, Austria and Denmark indicate a global impact. StatusGator detected the issue via an Early Warning Signal before any official acknowledgment from Tailscale. The provider did not publish status updates during the incident on their status page.

StatusGator detected a login page outage for Tailscale starting at May 22, 2025 7:54 PM UTC and lasting until 10:18 PM UTC. The problem blocked users from loading the login page and signing in, affecting access to the dashboard and resources across multiple regions for about 2 hours and 24 minutes. User reports spanned North America and Europe and described timeouts, inability to connect, or sign-in failures, indicating a broad impact on authentication and day-to-day use.

StatusGator observed the issue before any official acknowledgment. There were no official status updates documented in the provided data. The incident drew a sizable volume of user reports through the evening, signaling widespread disruption to sign-in and access to Tailscale services. The outage affected the authentication flow rather than the entire service, preventing users from signing in to manage their networks.

An incident at Tailscale began at 5:03 PM UTC with degraded performance on the control server, impacting the API (api.tailscale.com) and the coordination server. This caused slower API responses and intermittent coordination issues for users relying on Tailscale services. At 5:38 PM UTC, the Admin console (login.tailscale.com) also entered a degraded state, signaling broader impact on management tasks. The incident lasted about 1 hour and 5 minutes, with all components returning to normal by 6:08 PM UTC. The provider issued three official status updates as the issue progressed.

Tailscale reported degraded connectivity in the Madrid DERP region due to a power outage in the Iberian Peninsula. The Madrid DERP relay servers were affected, causing connectivity issues for users relying on DERP routing in that area.

The outage began on Apr 28, 2025 4:28 PM UTC and was resolved by Apr 29, 2025 1:43 PM UTC, lasting about 21 hours and 15 minutes. The incident saw two official status updates, with the Madrid DERP region transitioning from up to degraded (warn) and back to up as power and connectivity were restored.

An outage affecting the Tailscale package server pkgs.tailscale.com caused increased latency and timeouts for downloads, impacting users attempting to fetch packages. The incident began at Apr 23, 2025 1:28 PM UTC with the package server listed as degraded (warn) and was resolved at Apr 23, 2025 2:22 PM UTC when the service returned to normal. The issue lasted roughly 54 minutes and involved the package server component. The provider posted two status updates during the incident describing the degradation and subsequent recovery.