Minor impactResolvedDevOps

Tailscale incident: Funnel hostnames not resolving in public DNS

Tailscale reported this minor-impact incident on its official status page on Oct 27, 2026, 14:16 UTC. It was resolved after 2d.

Right now Tailscale is operational. Live Tailscale status →

🔔 Get alerted when Tailscale has issuesFree · email alerts · no credit card
Oct 27, 2026, 14:16 UTC
started
Oct 29, 2026, 14:17 UTC
resolved
2d
duration
Minor
impact
  1. resolvedOct 29, 2026, 14:17 UTC

    This incident has been resolved.

  2. investigatingOct 27, 2026, 14:16 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 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 27, 2026, 14:19 UTCoperational → degraded
  • Oct 29, 2026, 14:19 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 24m. See Tailscale's uptime and incident history