Skip to main content
Tailscale

Funnel hostnames not resolving in public DNS

Degraded Lasted 2d · started · Tailscale's page

Level
confirmed
Worst impact
Degraded
Down Index
23of 100

What to do

  • Check whether your product depends on Tailscale. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 2d it lasted.

    Anything that failed between 2026-10-27 14:16 UTC and 2026-10-29 14:17 UTC may need a replay.
  • Subscribe to Tailscale's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=tailscale works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Tailscale 2

  1. 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.

    provider

  2. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-9effa49c4f

Is Tailscale still down?

No, this incident was resolved 2026-10-29 14:17 UTC. For Tailscale's live state, see https://down.guide/tailscale.

How long did it last?

2d, from 2026-10-27 14:16 UTC to 2026-10-29 14:17 UTC, by the times Tailscale posted.

What caused it?

Tailscale hasn't published a root cause. If it does, it shows here.

Where does this come from?

Tailscale's official status page, https://status.tailscale.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.