Tailscale service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Run a live reachability check for tailscale.com. Compare the regional responses with the problem you see in Tailscale.
Find Tailscale help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Tailscale control-plane access and an existing connection between devices can behave differently.
The checker above requests tailscale.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Tailscale action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse infrastructure checks.
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Existing peer connectivity and new sign-in/coordination can have different scopes.
Open the website in your browser and compare it with the result above.
Open Tailscale help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Client versions, device pair, connection type, tailnet context privately, error and time without auth keys.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Tailscale.
These are troubleshooting comparisons, not claims that Tailscale is currently experiencing a particular incident.
Compare an already connected peer with device sign-in or new-peer coordination and identify the affected tailnet.
Check Tailscale Status and device diagnostics; a blocked application port is not established by a website check.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Tailscale seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open tailscale.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Tailscale issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Tailscale support.
Run the tailscale.com check and compare its original timestamps and responses with your actual error. Tailscale control-plane access and an existing connection between devices can behave differently.
Use the community buttons on this page to share whether the service works for you. For help from Tailscale, use the official help/reporting resource linked above. Existing peer connectivity and new sign-in/coordination can have different scopes.
Compare an already connected peer with device sign-in or new-peer coordination and identify the affected tailnet. Check Tailscale Status and device diagnostics; a blocked application port is not established by a website check.
Client versions, device pair, connection type, tailnet context privately, error and time without auth keys.