Vendor Status Watch

← all vendors

Tailscale status history

Current state: operational — “All Systems Operational” per https://status.tailscale.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

8incidents, last 30 days
24incidents, last 90 days
26incidents on record
Incidents per week, last 12 weeks:
Get Tailscale alerts in your Slack — free templateRSS for Tailscale

How long do Tailscale incidents last?

2.3 hmedian incident duration26 measured
4.8 h90th percentile1 in 10 ran longer
3.8 hmedian, major/critical only4 incidents

From 26 incidents with a vendor-posted start and resolve time. Longest on record: Log streaming performance issues — 2.5 days (2026-08-01 10:00 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (26)

StartedIncidentStatusImpactDuration
2026-09-16 06:43 UTCIru (formerly Kandji) device posture integration failureresolvednone2 h 12 min
2026-09-01 23:10 UTCSCIM groups not being updated for secondary tailnets in multi tailnet organizationsresolvednone28 min
2026-09-01 12:47 UTCFunnel connectivity issuesresolvedmajor3 h 31 min
2026-08-28 14:16 UTCGoogle user and group sync issuesresolvedminor2 h 50 min
2026-08-24 17:14 UTCCoordination service issuesresolvedminor1 h 27 min
2026-08-20 00:58 UTCCoordination service issuesresolvedmajor2 h 24 min
2026-08-19 05:53 UTCIssues with browser-based Tailscale clientsresolvedminor3 h 28 min
2026-08-17 20:27 UTCCoordination service performance issuesresolvedminor1 h 52 min
2026-08-12 22:06 UTCLogin attempts failingresolvedminor39 min
2026-08-10 16:10 UTCCertificate creation issuesresolvedminor8 h 31 min
2026-08-03 08:39 UTCCertificate creation issuesresolvedminor7 h 44 min
2026-08-03 07:01 UTCCoordination server issuesresolvedminor4 h 24 min
2026-08-01 10:00 UTCLog streaming performance issuesresolvednone2 d 11 h
2026-07-31 17:17 UTCSome users are experiencing Error 500 messages when trying to sign inresolvedminor27 min
2026-07-25 10:54 UTCAperture is unavailable for self-serve usersresolvednone1 h 40 min
2026-07-22 21:22 UTCService advertisement issuesresolvedminor57 min
2026-07-21 13:43 UTCControl D Integration Issuesresolvedminor2 h 41 min
2026-07-20 22:29 UTCLogin Attempts Failingresolvedminor19 min
2026-07-16 14:38 UTCCoordination server issuesresolvedminor4 h 04 min
2026-07-16 08:13 UTCAdmin console and pkgs.tailscale.com are unavailableresolvedcritical4 h 51 min
2026-07-14 08:42 UTCBilling page in the admin console unexpectedly refreshingresolvedminor4 h 01 min
2026-07-08 09:50 UTCCoordination server issuesresolvedminor35 min
2026-07-01 15:55 UTCIssue with approving devicesresolvedminor1 h 42 min
2026-06-23 14:11 UTCDERP performance degradedresolvedminor1 h 35 min
2026-06-16 13:53 UTCTailscale blog issuesresolvedminor31 min
2026-06-12 20:29 UTCCertificate creation issuesresolvedcritical4 h 01 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Tailscale with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "tailscale"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}