Tailscale Funnel hostnames failed to resolve in public DNS for approximately 42 hours, preventing external access to affected devices despite Funnel appearing enabled with valid HTTPS certificates. Internal tailnet connectivity via MagicDNS and Serve remained unaffected throughout. The issue was resolved by a configuration change that restored normal creation of public Funnel DNS records.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
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.
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.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with