">
sevanalysis

Tailscale

Infrastructure. Source: Tailscale status page.

Incidents, last 90 days
18
Median to mitigation
1h 23m
Median to resolution
2h 18m
p95 to resolution
2d 11h
Naming an upstream provider
0%
With a postmortem on the status page
0%

What failed, last 90 days

The text does not say enough to tell8
Login, tokens, certificates or credentials failed6
A provider or third-party service this vendor depends on failed1
A code release introduced the failure1
Network, DNS, routing or connectivity failure1
Data delayed, stale, lost or corrupted, or needing replay after recovery1

Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.

Incidents per month

Hatched months are before the recorded history starts.

All recorded incidents

Admin Panel Login Issues minor 2026-10-08 15:51 UTC 6m

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    We are investigating a problem causing an elevated rate of errors involving logging into the admin panel and are working to understand the full impact of the problem.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Funnel performance degradation minor 2026-10-02 21:05 UTC 2h 55m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are investigating reports of issues with Funnel, including a degradation in performance and timeouts for users in some locations.

  2. monitoring

    A fix has been deployed and we are monitoring for any further problems.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Coordination service issues minor 2026-10-01 13:12 UTC 44m

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    We are investigating a problem affecting some tailnets that is causing some users to encounter a 500 error when attempting to sign in. We are working to understand the full impact of the problem.

  2. monitoring

    A fix has been deployed and we are monitoring for any further problems.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Iru (formerly Kandji) device posture integration failure none 2026-09-16 06:43 UTC 2h 13m

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

  1. identified

    We are aware of an issue affecting the Iru (formerly Kandji) device posture integration. Users may experience failures following the removal of a feature by Iru on 14th September. Our team is currently working on a fix to mitigate these failures for affected tailnets.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

SCIM groups not being updated for secondary tailnets in multi tailnet organizations none 2026-09-01 23:10 UTC 29m

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. monitoring

    SCIM groups not being updated for secondary tailnets. A fix has been deployed and we are monitoring for any further problems.

  2. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Funnel connectivity issues major 2026-09-01 12:47 UTC 3h 31m

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are investigating reports of issues with Funnel, including connection errors for some users.

  2. identified

    We have identified the problem and are rolling out a fix.

  3. monitoring

    A fix has been deployed and we are monitoring for any further problems.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Google user and group sync issues minor 2026-08-28 14:16 UTC 2h 50m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are investigating a problem we're seeing with Google user and group sync, and are working to understand the full impact of the problem.

  2. identified

    We have identified the problem and are rolling out a fix.

  3. monitoring

    A fix has been deployed and we are monitoring for any further problems.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Coordination service issues minor 2026-08-24 17:14 UTC 1h 27m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    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.

  2. monitoring

    The issue has been isolated and we are monitoring for any further problems.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Coordination service issues major 2026-08-20 00:58 UTC 2h 24m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    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.

  2. identified

    We have identified the problem and are rolling out a fix.

  3. monitoring

    A fix has been deployed and we are monitoring for any further problems.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Issues with browser-based Tailscale clients minor 2026-08-19 05:53 UTC 3h 29m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are investigating an issue causing problems with connections from browser-based Tailscale clients, including Tailscale SSH via the Tailscale console.

  2. identified

    We have identified the problem and are rolling out a fix.

  3. monitoring

    A fix has been deployed and we are monitoring for any further problems.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Coordination service performance issues minor 2026-08-17 20:27 UTC 1h 52m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are aware of reports of the coordination service responding slowly and affecting some users, and we are investigating the scope of the issue.

  2. monitoring

    A fix has been deployed and we are monitoring for any further problems.

  3. identified

    We have identified the problem and are rolling out a fix.

  4. monitoring

    A fix has been deployed and we are monitoring for any further problems.

  5. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Login attempts failing minor 2026-08-12 22:06 UTC 40m

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    We are aware of unresponsive logins for some users. We are investigating the cause.

  2. identified

    We have identified the problem and are rolling out a fix.

  3. monitoring

    A fix has been deployed and we are monitoring for any further problems.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Certificate creation issues minor 2026-08-10 16:10 UTC 8h 31m

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    We are investigating a problem which is causing problems with issuing new certificates for MagicDNS hostnames. This problem affects manual certificate issuance and the deployment of new services through Tailscale Serve or Tailscale Funnel. Existing certificates and services...

  2. identified

    We have identified the problem and are rolling out a fix.

  3. monitoring

    A fix has been deployed and we are monitoring for any further problems.

  4. resolved

    This incident has been resolved.

  5. investigating

    We are investigating problems with issuing new certificates for MagicDNS hostnames. This problem affects manual certificate issuance and the deployment of new services through Tailscale Serve or Tailscale Funnel. Existing certificates and services currently exposed by Serve or...

  6. identified

    We have identified the problem and are rolling out a fix.

  7. monitoring

    A fix has been deployed and we are monitoring for any further problems.

  8. investigating

    We are investigating a problem which is causing problems with issuing new certificates for MagicDNS hostnames. This problem affects manual certificate issuance and the deployment of new services through Tailscale Serve or Tailscale Funnel. Existing certificates and services...

  9. monitoring

    We have identified the problem, and a fix has been deployed. We are monitoring for any further problems.

  10. resolved

    There have been no further problems, and the incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Certificate creation issues minor 2026-08-03 08:39 UTC 7h 44m

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    We are investigating a problem which is causing problems with issuing new certificates for MagicDNS hostnames. This problem affects manual certificate issuance and the deployment of new services through Tailscale Serve and Funnel. Existing certificates and services currently...

  2. investigating

    Our engineers have identified that this incident also affects creation of new Funnel and Serve domains. Existing Funnel and Serve domains remain unaffected.

  3. monitoring

    A fix has been deployed and we are monitoring for any further problems.

  4. investigating

    During our monitoring of this fix, we have noticed an increase in the error rate, which our engineers are investigating further.

  5. monitoring

    A fix has been deployed and we are monitoring for any further problems.

  6. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Coordination server issues minor 2026-08-03 07:01 UTC 4h 24m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    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.

  2. monitoring

    A fix has been deployed and we are monitoring for any further problems.

  3. resolved

    The service is still healthy and this incident has been resolved.

  4. investigating

    We are investigating a problem causing an elevated rate of errors in our coordination service,

  5. monitoring

    A fix has been deployed and we are monitoring for any further problems.

  6. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Log streaming performance issues none 2026-08-01 10:00 UTC 2d 11h

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    We are investigating an issue with tailnet log streaming availability.

  2. identified

    Log streaming has been restored, but some users may still see delayed log delivery.

  3. monitoring

    Log streaming remains operational, and we are monitoring. Some users may still see delayed log delivery to streaming endpoints, however live logs remain available via API and Admin Console.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Some users are experiencing Error 500 messages when trying to sign in minor 2026-07-31 17:17 UTC 28m

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    We are investigating a problem where some users are encountering an Error 500 message when trying to sign in to Tailscale.

  2. monitoring

    A fix has been deployed and we are monitoring for any further problems.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Aperture is unavailable for self-serve users none 2026-07-25 10:54 UTC 1h 40m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are aware of reports of Aperture being unavailable for self-serve users, and we're investigating this issue.

  2. identified

    We have identified the problem, and we're working on rolling out a fix.

  3. monitoring

    A fix has been deployed and we are monitoring for any further problems.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Service advertisement issues minor 2026-07-22 21:22 UTC 58m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are investigating reports of issues with advertising services through the CLI and Admin Console

  2. identified

    We have identified the problem and are rolling out a fix.

  3. monitoring

    A fix has been deployed and we are monitoring for any further problems.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Control D Integration Issues minor 2026-07-21 13:43 UTC 2h 41m

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are aware of an issue affecting ControlD profile selection and device attribution, and are investigating the scope of the issue

  2. identified

    We have identified the problem and are rolling out a fix.

  3. identified

    We have identified the problem and are rolling out a fix.

  4. monitoring

    A fix has been deployed and we are monitoring for any further problems.

  5. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Login Attempts Failing minor 2026-07-20 22:29 UTC 20m

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are aware of unresponsive logins for some users. We are investigating the cause.

  2. identified

    We have identified the problem and are rolling out a fix.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Coordination server issues minor 2026-07-16 14:38 UTC 4h 4m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    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.

  2. monitoring

    A fix has been deployed and we are monitoring for any further problems.

  3. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Admin console and pkgs.tailscale.com are unavailable critical 2026-07-16 08:13 UTC 4h 51m

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

  1. investigating

    We are aware of reports of the admin console and [pkgs.tailscale.com](http://pkgs.tailscale.com "pkgs.tailscale.com") not being available for users, and we are investigating the scope of the issue.

  2. identified

    We have identified that Amazon Cloudfront is experiencing issues: [https://health.aws.amazon.com/health/status](https://health.aws.amazon.com/health/status "https://health.aws.amazon.com/health/status"), and is the cause of the 504 errors seen on the admin console and...

  3. monitoring

    The admin console and [pkgs.tailscale.com](http://pkgs.tailscale.com "pkgs.tailscale.com") are now both operational. We are monitoring the situation for any further degradation in service.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Billing page in the admin console unexpectedly refreshing minor 2026-07-14 08:42 UTC 4h 1m

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are investigating an issue preventing some users from upgrading their plans in the Billing section of the admin console. The billing wizard may unexpectedly refresh after billing details are entered, preventing the upgrade from completing

  2. identified

    We have identified the cause of the issue affecting plan upgrades for some users in the Billing section of the admin console and are working on a fix

  3. monitoring

    We have deployed a fix for the issue causing the billing wizard to unexpectedly refresh during plan upgrades. We are now monitoring to confirm the issue is fully resolved.

  4. resolved

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Tailscale's status page.

Coordination server issues minor 2026-07-08 09:50 UTC 36m

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. investigating

    We are investigating a problem causing an elevated rate of authentication errors, and are working to understand the full impact of the problem.

  2. resolved

    This incident has been resolved. The authentication failures were due to a service becoming unreachable, and we have worked to restore the service. Approximately 1 in 10 requests between 08:40 and 10:00 UTC were affected, and the issue in this period was intermittent.

Excerpts are shortened. Read the full incident on Tailscale's status page.