outages.live
Live
TailscaleIncident ·

DERP relay connection issues

ResolvedOfficial update
0

Tailscale DERP relay servers in the NYC (1g) region had degraded connectivity. Tailscale deployed a fix and monitored the result. The incident is resolved and lasted 24 minutes.

State

Resolved

Started

Lasted

24 min

Worst impact

Degraded

Timeline

3 updates
00:4200:4800:5401:0001:06
DegradedUpdate postedTimes in UTC

Investigating

6 min 25%

Monitoring

18 min 75%

Updates

Times in UTC

As posted by Tailscale

Resolved

The service is still healthy and this incident has been resolved.

Monitoring

A fix has been deployed and we are monitoring for any further problems.

Investigating

We are investigating a problem with DERP relay servers in the **NYC (1g)** region. Clients making use of these DERP servers may have degraded connectivity.

Tailscale in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

17

Days with an incident

22

Median duration

1 h 52 min

This incident

79% shorter than the median

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

2 days
median 1 h 52 min
90 days agoToday

Other Tailscale incidents

All incidents

Tailscale·DERP connection issues

Tailscale DERP servers in the NYC region (Region 1) had degraded connectivity. Tailscale rolled out a fix and monitored the result. The incident is resolved and lasted 18 minutes.

Resolved

Tailscale·Funnel performance degradation

Tailscale Funnel had performance degradation and intermittent failures when users created new Funnel nodes and generated new TLS certificates. Tailscale reports that this incident is resolved. It lasted 63 minutes.

Resolved

Tailscale·Coordination service issues

This incident has been resolved.

Resolved

Tailscale·Funnel hostnames not resolving in public DNS

This incident has been resolved.

Resolved

Tailscale·Funnel hostnames not resolving in public DNS

This incident has been resolved.

Resolved

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.live/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.live/feed.xml?providers=tailscale
Slack
/feed subscribe https://outages.live/feed.xml?providers=tailscale

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane