Edge & Security
Tailscale SLA credit guide
What Tailscale's own document actually says about uptime — a 99.9% target it aims at rather than a level it commits to — and the tiered service credit it nonetheless pays for a month that falls short: the credit tiers, the filing deadline, how to file, and a calculator to estimate your credit.
What SLA credit does Tailscale pay when it misses?
When Tailscale (SLA — Silver/Gold support packages via Order Form) falls below the 99.9% monthly uptime target it states, Tailscale's published SLA pays a service credit worth 5%–10% of the affected service's monthly spend — larger the further uptime fell — claimable within 30 days of the end of the affected billing month. It's a credit toward a future invoice, not a cash refund.
Uptime target — not a commitment
99.9%
Filing window
30 days
counted from the end of the affected billing month
Services with SLA data
1
Credit calculator
SLA target is 99.9% — enter what you actually observed.
Enter your monthly spend above to see the dollar credit for a 5% tier.
Estimate only, from the vendor’s published tiers — the final credit is set by the vendor against your actual invoice and their SLA definitions.
Credit tiers by service
| Measured uptime | Credit |
|---|---|
| 90% to 99.89% | 5% of spend |
| below 90% | 10% of spend |
A VERIFIED ENTERPRISE PAYER WITH A TARGET (NOT GUARANTEE) COMMITMENT, READ FIRST-HAND ON 2026-10-03. Source: the "Tailscale Service Level Agreement" at tailscale.com/sla, Last updated 2026-06-02, read in full. THE FIGURE IS A TARGET, NOT A COMMITMENT (§2.1): "Tailscale will make commercially reasonable efforts to maintain at least 99.9% Uptime." That is an EFFORT standard — the same basis as Webflow §2.1 — so no surface may call the 99.9% a commitment, even though the 99.9% figure IS printed on the public page. Uptime is the percentage of total possible minutes the core systems (tailscale.com website + Documentation, admin console, API, coordination server, DERP relay servers, package server) are operational and available each calendar month: (Total minutes in a month − Downtime minutes) / total minutes in a month > 99.9%. THE CREDIT CHART (§4.1), Silver/Gold (99.9% commitment), as a percentage of monthly Fees: 99.9% or greater → No Service Credit; 90.00% - 99.89% → 5%; Under 90.00% → 10%. ⚠️ THE (99.89%, 99.9%) GAP: the table pays 5% up to 99.89% inclusive and nothing at 99.9%-or-greater, so a month strictly between 99.89% and 99.9% is a shortfall the table prices at nothing — reproduced faithfully (maxUptimeInclusive + a declared creditTierGaps entry) rather than smoothed over, the vercel pattern. ⚠️ A PLATINUM SIBLING TABLE EXISTS AND IS DELIBERATELY NOT CARRIED: §4.1 also states a Platinum variant (99.99% commitment): 99.99%+ → none; 90.00% - 99.989% → 5%; <90.00% → 10%. Silver/Gold is carried as the wildcard; Platinum is recorded here as the sibling table Ontracko does NOT select (the AWS second-table disclosure discipline) — do not invent a second profile for it, and if a customer holds Platinum the bands shift to 99.99%/99.989%. THE WINDOW (§4.2): "Customers must request Service Credits within thirty (30) days after the end of the impacted month by contacting Support" — month-end anchored, see DEADLINE_BASIS.tailscale. THE CAP (§4.3): credits are "capped at a maximum of the applicable monthly Fees" (creditCapPercent 100), are non-transferable, non-refundable, have no cash value, are applied to the next invoice, and unused credits expire on termination; all outstanding undisputed invoices must be paid up. THE SERVICE CREDIT IS THE SOLE AND EXCLUSIVE REMEDY (§1). ⚠️ SCOPE IS PAID-SUPPORT-PACKAGE / ORDER-FORM ONLY: the SLA is "included for all customers that purchase a Silver or Gold support package pursuant to an Order Form with Tailscale" (support packages: Silver, Gold and Platinum, by tier), so SELF-SERVE AND PERSONAL PLANS GET NO SLA — the Zapier/DocuSign enterprise/order-form scope. ⚠️ DOWNTIME IS REGIONAL (§4.1): a customer may be eligible in their region while others are not; Ontracko already region-matches. EXCLUSIONS (§5): end-of-maintenance/EOL versions; integrations/third-party services; pre-release/staging/sandbox/Research; unsupported ancillary apps; devices behind subnet routers; external network/equipment problems outside Tailscale's reasonable control; suspended accounts; self-hosted coordination servers and self-compiled OSS; client software on unsupported hardware/software; use not per the Agreement/Documentation and client modifications; device hardware/abuse defects; force majeure. Routine maintenance (§2.2.1, ≥48h notice where it may materially disrupt) and emergency maintenance (§2.2.2) are excluded from Downtime.
How to file a Tailscale SLA credit claim
Portal: Tailscale Support ↗
- ⚠️ CHECK THE SCOPE FIRST — THIS SLA IS PAID-SUPPORT-PACKAGE / ORDER-FORM ONLY. Its preamble includes the SLA "for all customers that purchase a Silver or Gold support package pursuant to an Order Form with Tailscale" (support packages run Silver, Gold and Platinum by tier). A self-serve or Personal plan has NO SLA and no service credit to claim — confirm the account is on a Silver/Gold/Platinum support package under an Order Form before filing.
- WHAT THE 99.9% ACTUALLY IS — A TARGET, NOT A GUARANTEE. §2.1: "Tailscale will make commercially reasonable efforts to maintain at least 99.9% Uptime." That is an effort standard, so the 99.9% is a level Tailscale works toward rather than one it promises; a shortfall is not a hard breach of a guarantee. Uptime is measured per CALENDAR MONTH across the core systems — the tailscale.com website and Documentation, the admin console, the API, the coordination server, the DERP relay servers and the package server: (total minutes in the month − Downtime) / total minutes > 99.9%.
- THE CREDIT TABLE (§4.1), Silver/Gold, as a percentage of that month's Fees: 99.9% or greater → no credit; 90.00% to 99.89% → 5%; under 90.00% → 10%. Ontracko indexes this table on the month's measured uptime, and 99.89% pays 5% because the table writes that boundary as inclusive.
- ⚠️ THE GAP THE TABLE PRICES AT NOTHING: a month that lands STRICTLY between 99.89% and 99.9% is below the 99.9% figure Tailscale aims at — a shortfall — but the Silver/Gold table assigns it no percentage. Name that interval when you discuss the month; do not quote a zero as though the table addressed it, and do not read 5% into it either. It is an unpriced interval in Tailscale's own document.
- ⏰ FILE WITHIN 30 DAYS AFTER THE END OF THE IMPACTED MONTH, by contacting Support (§4.2). The window runs from month-end, not from the incident — put the date in the calendar the moment the month closes.
- THE CAP AND HOW IT SETTLES (§4.3): credits are capped at the applicable monthly Fees, are applied to the next invoice, carry no cash value and are non-refundable and non-transferable, and any unused credit expires on termination. The service credit is the sole and exclusive remedy (§1).
- ⚠️ ELIGIBILITY BAR: all outstanding undisputed invoices must be paid up before a credit is issued — settle the account first.
- REGIONAL DOWNTIME (§4.1): Downtime is assessed by region, so a customer may be eligible in their region while others are not. Identify the affected Cloud-Provider Region and the core system(s) involved alongside the month.
- ⚠️ THE PLATINUM VARIANT: if the account holds a Platinum support package the commitment is 99.99% and the bands shift — 99.99%+ → none; 90.00% to 99.989% → 5%; under 90.00% → 10%. Read your own support package before applying the Silver/Gold bands above.
- Strip out the exclusions before totalling (§5): end-of-maintenance/EOL versions; integrations and third-party services; pre-release/staging/sandbox/Research features; unsupported ancillary apps; devices behind subnet routers; external network or equipment problems outside Tailscale's reasonable control; suspended accounts; self-hosted coordination servers and self-compiled OSS; client software on unsupported hardware/software; use not per the Agreement/Documentation and client modifications; device hardware/abuse defects; and force majeure. Routine maintenance (§2.2.1, ≥48h notice where it may materially disrupt) and emergency maintenance (§2.2.2) are excluded from Downtime.
Evidence you’ll need
- •Calendar month of the shortfall
- •Affected core system(s) (website/Documentation, admin console, API, coordination server, DERP relay servers, package server) and Cloud-Provider Region
Common exclusions
- •End-of-maintenance / end-of-life versions of the Services
- •Integrations and third-party services
- •Pre-release, staging, sandbox or Research features
- •Unsupported ancillary applications
- •Devices behind subnet routers
- •External network or equipment problems outside Tailscale's reasonable control
- •Suspended accounts
- •Self-hosted coordination servers and self-compiled open-source software
- •Client software running on unsupported hardware or software
- •Use not in accordance with the Agreement or Documentation, and Customer modifications
- •Device hardware or abuse defects
- •Force majeure
- •Routine maintenance (§2.2.1, at least 48 hours' notice where it may materially disrupt) and emergency maintenance (§2.2.2), both excluded from Downtime
Frequently asked
What is Tailscale's SLA uptime commitment?
Tailscale does not publish a commitment — it publishes a TARGET. Tailscale (SLA — Silver/Gold support packages via Order Form) states a 99.9% monthly uptime target: a level Tailscale says it aims at, not one it guarantees. Unlike most targets, though, Tailscale's own document pays a service credit when it is missed, in tiers by the measured uptime, so a shortfall is not without a remedy — it is simply not the breach of a guaranteed percentage. The figure is Tailscale's own — it is transcribed from Tailscale's own document and this page does not suppress it — but Tailscale frames it as a level it aims at rather than one it guarantees, so there is no committed percentage to hold Tailscale to. If Tailscale has promised you a binding availability level, it lives in your own Order Form or negotiated agreement rather than on any public page.
How much credit can I claim if Tailscale misses its SLA?
Credits are tiered by measured uptime, from 5% up to 10% of the monthly service spend for the affected service, depending on how far below 99.9% availability fell. One caution: Tailscale's own published table leaves one uptime range below the commitment with no credit percentage at all — strictly between 99.89% and 99.9%. A month that lands there is still a breach, but the table sets no credit for it, so Ontracko states no percentage for that month rather than a zero; take it up with Tailscale directly, citing its own table.
What is the deadline to file a Tailscale SLA credit claim?
Claims are generally due within 30 days of the end of the affected billing month (verify the exact clause in Tailscale's SLA before filing).
Does Ontracko file Tailscale SLA credit claims for me?
Ontracko monitors Tailscale for free, detects SLA breaches automatically, and assembles the complete claim package (evidence + credit math + claim text). You file it; Ontracko charges 8% only on credits that are actually recovered.
Let Ontracko file it for you
Connect Tailscale and Ontracko monitors the SLA, catches every breach, and drafts the claim with the evidence attached. Free — 8% only on recovered credits.