rewindex

CompaniesTailscaleIncidents

Tailscale: Funnel hostnames not resolving in public DNS

MinorStatus: resolvededitedStarted Resolved (2 d)2 updatesstatus.tailscale.com (opens in new tab)

Affected components: Funnel

Timeline of updates

  1. investigatingEdited

    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.

  2. resolved

    This incident has been resolved.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on status.tailscale.com (opens in new tab).

Cite this

Status incident (vendor impact label: minor) posted by Tailscale, started 2026-10-27 14:16 UTC, resolved after 2 d, 2 update(s); edited after publishing.

Title
Funnel hostnames not resolving in public DNS
Vendor
Tailscale
Date
URL
https://rewindex.com/company/tailscale/incidents/01M5YVH12FKFH765E1J7PGW4B5

Tailscale profileRecent Tailscale incidentsAll outages on October 27, 2026Tailscale in October 2026MarkdownJSON