# Funnel hostnames not resolving in public DNS

- Provider: [Tailscale](https://down.guide/providers/tailscale)
- Confidence: Confirmed
- Impact: Degraded
- lasted 2d
- started 2026-10-27 14:16 UTC
- id: DWN-9effa49c4f
- Official page: https://status.tailscale.com/incidents/01M5YVH12FKFH765E1J7PGW4B5

## Updates from Tailscale
### 2026-10-27 14:16 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 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-29 14:17 UTC: resolved
This incident has been resolved.

From the builder: does your app depend on Tailscale? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=tailscale) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Tailscale.

---
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://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-9effa49c4f), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.