Technologies/Tailscale/tailscale.derp.home_connection
TailscaleTailscaleMetric

tailscale.derp.home_connection

Home DERP connection status
Dimensions:None
Available on:PrometheusPrometheus (1)DatadogDatadog (1)

Summary

Binary indicator (0 or 1) showing whether this node is connected to its designated home DERP relay server. The home DERP server is the primary relay for indirect connections when direct peer-to-peer fails. Value of 0 indicates disconnection from the home relay, potentially forcing connections through alternative DERP regions or causing connectivity failures. Value of 1 confirms relay availability for NAT traversal fallback.

Interface Metrics (2)
PrometheusPrometheus
Indicates whether the node is connected to its home DERP relay server (1) or not (0)
Dimensions:None
DatadogDatadog
Number of devices using their home DERP relay
Dimensions:None
Sources
tailscale_derp_home_connectiongithub.com
tailscale.relay.home_derpdocs.datadoghq.com

Technical Annotations (30)

Configuration Parameters (3)
OmitDefaultRegionsrecommended: false
Recommended to retain default DERP fallback for high availability
derpMap.regions.RegionIDrecommended: null
Setting to null disables the specified DERP region
--portrecommended: 41641
UDP port to open for direct connections through NAT
Error Signatures (3)
Tailscale issues detected - No IP assignedlog pattern
Tailscale could not connect to the 'Seattle' relay server. Your Internet connection might be down, or the server might be temporarily unavailable.log pattern
magicsock: ReSTUN("derp-map-update") ignored; stopped, no private keylog pattern
CLI Commands (8)
tailscale pingdiagnostic
tailscale ping --verbosediagnostic
tailscale statusdiagnostic
tailscale netcheckdiagnostic
tailscale ip -4diagnostic
curl https://controlplane.tailscale.com/derpmap/defaultdiagnostic
curl --silent https://controlplane.tailscale.com/derpmap/default | jq -r '.Regions[] | "\(.RegionID) \(.RegionName)"'diagnostic
tailscale ping <device-name>diagnostic
Technical References (16)
home DERP serverconceptcoordination servercomponentDERPprotocolNAT traversalconcepttailnetconceptSecurity ListcomponentUDP hole punchingconceptOmitDefaultRegionscomponenttailnet policy filefile pathRegionIDconcepthard NATconceptNAT gatewaycomponentTailscale Peer RelaycomponentDERP relay servercomponentmagicsockcomponenttailnet profileconcept
Related Insights (13)
DERP region outage triggers automatic failover to alternative regionsinfo
▸
Local or network firewall rules block Tailscale connectivitycritical
▸
DERP relay fallback degrades performance when direct connection failswarning
▸
Relayed connections reduce network performancewarning
▸
Tailscale IP assignment failure indicates connection problemcritical
▸
Inconsistent NAT behavior between local and external connectionsinfo
▸
OmitDefaultRegions=true leaves no DERP fallback if custom node failswarning
▸
Disabling DERP regions via policy file affects connection availabilitywarning
▸
Hard NAT prevents direct connections between deviceswarning
▸
Direct connection degradation during NAT traversal negotiationinfo
▸
Tailnet profile switch causes DERP relay connection failure and stalled connectionwarning
▸
DERP server IP address changes for multiple regionswarning
▸
DERP relay dependency indicating direct connectivity failurewarning

When peer connections are forced to route through DERP relay servers instead of establishing direct peer-to-peer connections, this indicates NAT traversal failures, firewall restrictions, or network configuration issues. DERP relays add latency and consume additional bandwidth, degrading performance and increasing infrastructure costs.

▸