All services / Developer tools
Tailscale
- Current assessment
- Operational (provider)
- Confidence
- Medium confidence
- Scope
- Provider-wide
- Last verified
- Nov 18, 10:26 PM UTC
- Sources
- 1 source: Official
Official incident history
- ResolvedStarted: · Duration: 25 min
Tailscale: API, increased latency
Provider's original title: Elevated PAM API latency and error rates
Provider updates (3)
- Investigating “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.”
- Monitoring “A fix has been deployed and we are monitoring for any further problems.”
- Resolved “This incident has been resolved.”
- Started: · Duration: 24 minResolved
Provider updates (3)
- Investigating “We are investigating a problem with DERP relay servers in the **NYC (1g)** region. Clients making use of these DERP servers may have degraded connectivity.”
- Monitoring “A fix has been deployed and we are monitoring for any further problems.”
- Resolved “The service is still healthy and this incident has been resolved.”
- Started: · Duration: 18 minResolved
Provider updates (2)
- Monitoring “We have identified a problem with DERP servers in the **NYC** region (Region 1) and have rolled out a fix. Clients making use of these DERPs may have degraded connectivity.”
- Resolved “This incident has been resolved.”
- ResolvedStarted: · Duration: 63 min
Tailscale: degraded performance
Provider's original title: Funnel performance degradation
Provider updates (2)
- Investigating “We’re investigating an issue causing intermittent failures when creating new Tailscale Funnel nodes and generating new TLS certificates.”
- Resolved “This incident has been resolved.”
- Started: · Duration: 44 minResolved
Provider updates (3)
- 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.”
- Monitoring “A fix has been deployed and we are monitoring for any further problems.”
- Resolved “This incident has been resolved.”
- Started: · Duration: 2881 minResolved
Provider updates (2)
- Investigating “We are currently investigating reports of Funnel hostnames not resolving publicly. Affected devices show Funnel as enabled and have valid HTTPS certificates, but public DNS lookups for the device's ts.net name return no address, and external access does not work. In some cases the records appear after a delay. Connectivity from within the tailnet, including MagicDNS and Serve, is not affected.”
- Resolved “This incident has been resolved.”
- Started: · Duration: 2504 minResolved
Provider updates (3)
- Investigating “We are currently investigating reports of Funnel hostnames not resolving publicly. Affected devices show Funnel as enabled and have valid HTTPS certificates, but public DNS lookups for the device's [ts.net](http://ts.net) name return no address, and external access does not work. In some cases the records appear after a delay. Connectivity from within the tailnet, including MagicDNS and Serve,…”
- Monitoring “We have rolled out a configuration change, and are now seeing public Funnel DNS records created normally. We will continue to monitor to ensure DNS records remain stable.”
- Resolved “This incident has been resolved.”
- Started: · Duration: 6 minResolved
Provider updates (2)
- 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.”
- Resolved “This incident has been resolved.”
- ResolvedStarted: · Duration: 175 min
Tailscale: degraded performance
Provider's original title: Funnel performance degradation
Provider updates (3)
- Investigating “We are investigating reports of issues with Funnel, including a degradation in performance and timeouts for users in some locations.”
- Monitoring “A fix has been deployed and we are monitoring for any further problems.”
- Resolved “This incident has been resolved.”
- Started: · Duration: 44 minResolved
Provider updates (3)
- 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.”
- Monitoring “A fix has been deployed and we are monitoring for any further problems.”
- Resolved “This incident has been resolved.”
- ResolvedStarted: · Duration: 133 min
Tailscale: outage or errors
Provider's original title: Iru (formerly Kandji) device posture integration failure
Provider updates (2)
- 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.”
- Resolved “This incident has been resolved.”
- Started: · Duration: 29 minResolved
Provider updates (2)
- Monitoring “SCIM groups not being updated for secondary tailnets. A fix has been deployed and we are monitoring for any further problems.”
- Resolved “This incident has been resolved.”
- Started: · Duration: 211 minResolved
Provider updates (4)
- Investigating “We are investigating reports of issues with Funnel, including connection errors for some users.”
- Identified “We have identified the problem and are rolling out a fix.”
- Monitoring “A fix has been deployed and we are monitoring for any further problems.”
- Resolved “This incident has been resolved.”
- Started: · Duration: 170 minResolved
Provider updates (4)
- 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.”
- Identified “We have identified the problem and are rolling out a fix.”
- Monitoring “A fix has been deployed and we are monitoring for any further problems.”
- Resolved “This incident has been resolved.”
- Started: · Duration: 87 minResolved
Provider updates (3)
- 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.”
- Monitoring “The issue has been isolated and we are monitoring for any further problems.”
- Resolved “This incident has been resolved.”
- Started: · Duration: 144 minResolved
Provider updates (4)
- 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.”
- Identified “We have identified the problem and are rolling out a fix.”
- Monitoring “A fix has been deployed and we are monitoring for any further problems.”
- Resolved “This incident has been resolved.”
- Started: · Duration: 209 minResolved
Provider updates (4)
- Investigating “We are investigating an issue causing problems with connections from browser-based Tailscale clients, including Tailscale SSH via the Tailscale console.”
- Identified “We have identified the problem and are rolling out a fix.”
- Monitoring “A fix has been deployed and we are monitoring for any further problems.”
- Resolved “This incident has been resolved.”
- Started: · Duration: 112 minResolved
Provider updates (5)
- 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. ”
- Monitoring “A fix has been deployed and we are monitoring for any further problems.”
- Identified “We have identified the problem and are rolling out a fix.”
- Monitoring “A fix has been deployed and we are monitoring for any further problems.”
- Resolved “This incident has been resolved.”
- Started: · Duration: 511 minResolved
Provider updates (10)
- 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 currently exposed by Serve or Funnel will remain unaffected as long as the current certificates stay valid.”
- Identified “We have identified the problem and are rolling out a fix.”
- Monitoring “A fix has been deployed and we are monitoring for any further problems.”
- Resolved “This incident has been resolved.”
- 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 Funnel will remain unaffected as long as the current certificates stay valid.”
- Identified “We have identified the problem and are rolling out a fix.”
- Monitoring “A fix has been deployed and we are monitoring for any further problems.”
- 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 currently exposed by Serve or Funnel will remain unaffected as long as the current certificates stay valid.”
- Monitoring “We have identified the problem, and a fix has been deployed. We are monitoring for any further problems.”
- Resolved “There have been no further problems, and the incident has been resolved.”
- ResolvedStarted: · Duration: 40 min
Tailscale: sign-in, outage or errors
Provider's original title: Login attempts failing
Provider updates (4)
- Investigating “We are aware of unresponsive logins for some users. We are investigating the cause.”
- Identified “We have identified the problem and are rolling out a fix.”
- Monitoring “A fix has been deployed and we are monitoring for any further problems.”
- Resolved “This incident has been resolved.”
What the provider published about this service, with the provider's own updates (wording quoted as published).
Evidence
- Official
- Tailscale Status ↗ ·
All Systems Operational· Nov 18, 10:26 PM UTC
Why this assessment
- Provider reports no active incident.
Rule set assess-1. The same evidence always gives the same result.
Evidence and freshness
Each source separately: who says it, when it was last observed, and whether it is recent enough to be used.
| Source | Last observed | Age | Used in assessment |
|---|---|---|---|
| Official | 2 min ago | Yes, recent |
Technical details
Affected components (provider)
The provider lists no degraded components.