Live

Tailscale

Tailscale is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

16

Days with an incident

22

Median duration

2 h 18 min

Longest incident

2 days

Components

18
Admin console (console.tailscale.com) Operational
90 days agoNo incidentsToday
API (api.tailscale.com) Operational
90 days agoNo incidentsToday
Coordination service Operational
90 days agoNo incidentsToday
DERP relay servers Operational
90 days agoNo incidentsToday
Certificates Operational
90 days agoNo incidentsToday
Mullvad exit nodes Operational
90 days agoNo incidentsToday
Homepage and Documentation (tailscale.com) Operational
90 days agoNo incidentsToday
Package server (pkgs.tailscale.com) Operational
90 days agoNo incidentsToday
Funnel Operational
90 days agoNo incidentsToday
Aperture Operational
90 days agoNo incidentsToday
Tailscale Support Operational
90 days agoNo incidentsToday
API (US) Operational
90 days agoNo incidentsToday
API (EU) Operational
90 days agoNo incidentsToday
Portal Operational
90 days agoNo incidentsToday
Tunnel Operational
90 days agoNo incidentsToday
Tunnel (EU) Operational
90 days agoNo incidentsToday
Website Operational
90 days agoNo incidentsToday
HTTP Socket Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Follow Tailscale

Your coding agent knows when Tailscale is down, and tells you when a failure is theirs, not yours. You can also get Tailscale incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "tailscale" and tell me if Tailscale has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=tailscale
Slack
/feed subscribe https://outages.live/feed.xml?providers=tailscale

Go from tracking outages to fixing production issues with Polylane.

Try Polylane