outages.live
Live
TailscaleIncident · 2026-10-27 14:16 UTC

Funnel hostnames not resolving in public DNS

ResolvedOfficial update

This incident has been resolved.

The latest update from Tailscale.

State

Resolved

Started

5 d ago

2026-10-27 14:16 UTC

Lasted

2 days

until 2026-10-29 14:17 UTC

Worst impact

Degraded

Timeline

2 updates
Oct 27Oct 28Oct 28Oct 29Oct 29
DegradedUpdate postedDates in UTC

Investigating

2 days 100%

Updates

Times in UTC

As posted by Tailscale

Resolved2026-10-29 14:17 UTC

This incident has been resolved.

Investigating2026-10-27 14:16 UTC

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.

Tailscale in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

19

Days with an incident

22

Median duration

2 h 50 min

This incident

17× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

2 days
median 2 h 50 min
90 days agoToday

Other Tailscale incidents

All incidents

Tailscale·Coordination service issues

This incident has been resolved.

Resolvedresolved 1 d ago

Tailscale·Funnel hostnames not resolving in public DNS

This incident has been resolved.

Resolvedresolved 6 d ago

Tailscale·Admin Panel Login Issues

This incident has been resolved.

Resolvedresolved 24 d ago

Tailscale·Funnel performance degradation

This incident has been resolved.

Resolvedresolved 29 d ago

Tailscale·Coordination service issues

This incident has been resolved.

Resolvedresolved 31 d ago

Follow Tailscale

Your coding agent knows when Tailscale is down, and tells you when a failure is theirs, not yours. You can also get Tailscale incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "tailscale" and tell me if Tailscale has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=tailscale
Slack
/feed subscribe https://outages.cc/feed.xml?providers=tailscale

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane