This incident has been resolved.

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.