Minor impactOngoingDevOps

Tailscale incident: Funnel hostnames not resolving in public DNS

Tailscale reported this minor-impact incident on its official status page on Oct 24, 2026, 17:23 UTC. It has not been marked resolved yet.

Right now Tailscale is operational. Live Tailscale status →

🔔 Get alerted when Tailscale has issuesFree · email alerts · no credit card
Oct 24, 2026, 17:23 UTC
started
—
resolved
ongoing
duration
Minor
impact
  1. monitoringOct 24, 2026, 19:52 UTC

    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.

  2. investigatingOct 24, 2026, 17:23 UTC

    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, is not affected.

What APIStatus.watch saw

  • Oct 24, 2026, 17:23 UTCoperational → degraded
  • Oct 24, 2026, 19:53 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Tailscale have incidents?

Tailscale reported 15 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 2h 37m. See Tailscale's uptime and incident history