# Funnel hostnames not resolving in public DNS

- Provider: [Tailscale](https://down.guide/tailscale)
- Level: confirmed
- Impact: Degraded
- lasted 1d 17h
- started 2026-10-24 17:23 UTC
- id: DWN-c162f462c8
- Official page: https://status.tailscale.com/incidents/01M5QF0RTE57V3E47CK2HQREK0

## Updates from Tailscale
### 2026-10-24 17:23 UTC: 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\](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.

### 2026-10-24 19:52 UTC: monitoring
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.

### 2026-10-26 11:07 UTC: resolved
This incident has been resolved.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).