CheckUpstream does not yet run an independent probe against Tailscale, so no availability figure is published for it — only Tailscale's own disclosure record below. 8 incidents were recorded in the past 12 months; the most recent resolved 3 days ago after 3 hours. Status signals are polled from Tailscale's official Atlassian Statuspage status page, alongside independent probes and community reports.
Independent measurement how this is computed
Not measured
We run no independent probe against Tailscale yet, so we publish no availability figure for it. What follows is Tailscale's own disclosure record, which is a different thing.
Vendor disclosed: 7 incidents · 23 of 30 days with none posted · 17h 22m of declared impact
Fewer incidents in the last 30 days than 15% of 232 tracked services.
Share of each window with no impact declared by Tailscale
7d
99.481%
30d
97.587%
90d
99.090%
180d
99.545%
1y
99.776%
Downtime like this can be refundable
If you're a paying Tailscale customer, outages in these windows may count against Tailscale's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Tailscale entitlement →Does Tailscale actually matter to you?
A Tailscale outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 7 incidents Tailscale published and resolved in the last 30 days, measured between their own start and resolution times. It describes how long Tailscale takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 28, 14:16 UTC · resolved in 2h 54m · Resolved
Aug 24, 17:14 UTC · resolved in 1h 35m · Resolved
Aug 20, 00:58 UTC · resolved in 1h 42m · Resolved
Aug 19, 05:53 UTC · resolved in 3h 7m · Resolved
Live Tailscale status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/tailscale)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Tailscale is currently Operational. CheckUpstream tracks Tailscale in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is Tailscale down" view? See the Tailscale Live status page.
Aug 17, 20:27 UTC · resolved in 52m · Resolved
Aug 10, 16:10 UTC · resolved in 2h 19m · Resolved
Aug 3, 07:01 UTC · resolved in 18h 28m · Resolved
Aug 1, 11:49 UTC · resolved in 7h 35m · Resolved
Tailscale's last resolved incident started 3 days ago and lasted 2h 54m (degraded performance).
We don't publish one. CheckUpstream runs no independent probe against Tailscale yet, and the only other figure available would be derived from Tailscale's own incident posts — which measures how much a vendor discloses rather than how available it was. Vendors that post often score worse than vendors that stay quiet, so the number would be backwards.
Sign up to CheckUpstream and add Tailscale to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Tailscale's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.