Minor impactOngoingDevOps

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 has not been marked resolved yet.

Right now Tailscale is degraded. Live Tailscale status →

🔔 Get alerted when Tailscale has issuesFree · email alerts · no credit card
Oct 27, 2026, 14:16 UTC
started
—
resolved
ongoing
duration
Minor
impact
  1. 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

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Tailscale have incidents?

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

Tailscale incident on Oct 27, 2026: Funnel hostnames not resolving in public DNS · APIStatus.watch