Technologies/Tailscale/tailscale.node.up
TailscaleTailscaleMetric

tailscale.node.up

Node up status
Dimensions:None
Available on:PrometheusPrometheus (1)

Summary

Binary indicator (0 or 1) showing whether this specific node is currently operational and connected to the tailnet. Value of 1 indicates the node is up and functioning, while value of 0 signals the node is down or disconnected. Monitor to track individual node availability, detect outages, and validate successful startup after configuration changes or updates.

Interface Metrics (1)
PrometheusPrometheus
Indicates whether the Tailscale node is up and connected (1) or down (0)
Dimensions:None
Sources
tailscale_upgithub.com

Technical Annotations (33)

Configuration Parameters (1)
ExitNodeIDrecommended: device ID or auto:any
Forces clients to use specific exit node; outage risk if node fails
Error Signatures (4)
Tailscale issues detected - Daemon not activelog pattern
Tailscale issues detected - No IP assignedlog pattern
Warning: client versionlog pattern
!= tailscaled server versionlog pattern
CLI Commands (10)
tailscale statusdiagnostic
tailscale status --routesdiagnostic
tailscale pingdiagnostic
systemctl status tailscaleddiagnostic
systemctl is-active --quiet tailscaleddiagnostic
systemctl restart tailscaledremediation
systemctl enable tailscaledremediation
tailscale ip -4diagnostic
tailscale status --json | jq '.BackendState, .Self.DNSName, .Self.Online'diagnostic
tailscale ping homeserverdiagnostic
Technical References (18)
via fieldcomponentsubnet routerscomponentapp connectorscomponentexit nodecomponentaccess control policiesconceptexit nodescomponenttailscaledcomponentDERPprotocoltailnetconceptdevice approvalconceptExitNodeID policycomponentstderrconceptexit codeconcepthealthchecks.iocomponentts.net hostnamecomponentSynologycomponentLet's EncryptcomponentNAScomponent
Related Insights (17)
Inter-device communication failure within tailnetcritical
▸
Node appears offline due to outdated software or firmwarewarning
▸
Via field subnet router misconfiguration blocks traffic routingcritical
▸
App connector misconfiguration in via field blocks accesscritical
▸
Exit node performance issues or access restrictions prevent internet connectivitywarning
▸
Node health issues indicate connectivity or configuration problemswarning
▸
Tailscale daemon inactive prevents network connectivitycritical
▸
Tailscale IP assignment failure indicates connection problemcritical
▸
Tailscale disconnected state despite running daemonwarning
▸
Node missing from tailscale status indicates authorization or tailnet mismatchcritical
▸
Forced exit node offline causes complete internet outagecritical
▸
Tailscale version mismatch causes false down alerts in monitoringwarning
▸
Scheduled backup jobs over Tailscale fail when daemon becomes unresponsivewarning
▸
Certificate renewal requires remote access to home infrastructurewarning
▸
Tailscale daemon downtime disrupting connectivitycritical

When the Tailscale daemon stops running or crashes, the node loses all Tailscale network connectivity, becoming unreachable to peers and unable to reach other nodes. This represents complete loss of VPN functionality and requires immediate attention.

▸
Stale node presence indicating connectivity or coordination plane issueswarning

When tailscale.node.last_seen timestamp becomes stale (not updating for extended periods), it indicates the node is not successfully communicating with the Tailscale coordination server or peers. This can be caused by network partitions, firewall rules blocking control plane traffic, or coordination server issues.

▸
Node health warnings indicating degraded operational statewarning

When tailscale.node.health.messages reports warnings, the node is experiencing operational issues that may not cause immediate failure but indicate degraded state. These warnings can include DNS resolution problems, firewall traversal issues, or coordination server connectivity problems.

▸