Skip to main content
TeamViewer logo

Is TeamViewer Down?

No — TeamViewer is up

Reachable from all 8 checked regions

Average response time: 660ms

Last checked · checks run every 6 hours

Official status page: https://status.teamviewer.com

TeamViewer uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
601ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 60 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

60-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 30 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 31 checks
Sep 30: 100.00% uptime, 29 checks
Oct 1: 100.00% uptime, 32 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
337ms
DNS 0ms TCP 1ms TLS 9ms TTFB 336ms
lhr
321ms
DNS 1ms TCP 2ms TLS 17ms TTFB 321ms
nrt
867ms
DNS 0ms TCP 1ms TLS 10ms TTFB 867ms
ord
457ms
DNS 0ms TCP 1ms TLS 10ms TTFB 457ms
sin
689ms
DNS 0ms TCP 1ms TLS 9ms TTFB 689ms
sjc
670ms
DNS 0ms TCP 2ms TLS 11ms TTFB 670ms
syd
1486ms
DNS 0ms TCP 0ms TLS 9ms TTFB 1486ms
yyz
460ms
DNS 0ms TCP 1ms TLS 11ms TTFB 458ms

What TeamViewer does

TeamViewer connects a technician to a remote machine across the internet without a VPN, which is how many IT teams and managed service providers reach staff laptops and unattended servers. The platform has grown well past screen sharing: the same account covers Remote Management, Monitoring and Asset Management, Backup, Endpoint Protection and a Management Console, so one incident can touch several tools at once.

What an outage looks like

Clients sit at the message Not ready. Please check your connection and never receive an ID, so no session can be started or accepted. Established sessions drop and will not reconnect. The Management Console fails to sign in, which blocks unattended access lists and user management. API calls from integrations and scripted deployments fail, and Remote Management functions such as Backup and Endpoint Protection report separately.

What to do about it

Check status.teamviewer.com, which tracks the Management Console, API, IoT, Remote Management, Monitoring and Asset Management, Backup, Endpoint Protection, the Website and the Customer Portal as separate components with 90-day uptime for each. Before concluding it is an outage, confirm outbound port 5938 is open, which TeamViewer documents as its connection requirement and which produces the same error when a firewall blocks it.

Is it down for everyone, or just you?

If this page says TeamViewer is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

TeamViewer outage FAQ

Does Not ready. Please check your connection mean TeamViewer is down?
Usually not. TeamViewer's own troubleshooting for that message lists a broken internet connection and a firewall blocking outbound port 5938 before it mentions service disruption, and the local causes are far more common. Test whether other sites load, then check status.teamviewer.com and the per-region measurements here. If our regions all pass, the fault is almost certainly between your machine and the internet.
Is TeamViewer down for everyone or just me?
The per-region measurements on this page answer the geographic half of the question, and status.teamviewer.com answers the component half. Because TeamViewer separates the Management Console from the session infrastructure, a console that will not load while existing sessions keep running is a normal partial failure rather than a contradiction, and it points at a specific component rather than a total outage.
Do unattended servers stay reachable during a TeamViewer outage?
Not if the fault is in the connection infrastructure, because unattended access uses the same path as an attended session. The machines themselves are unaffected and keep running. This is the case for keeping a second route to critical servers, whether that is SSH, RDP over a VPN or out-of-band management, since a remote access tool is a single point of failure by design.
Do TeamViewer Backup and Endpoint Protection stop during an outage?
They can fail independently. TeamViewer lists Backup, Endpoint Protection, Monitoring and Asset Management and the DEX Platform as separate components, each with its own 90-day uptime figure, so remote sessions can be unavailable while backups continue, or the reverse. Check the specific component rather than reading a red banner as meaning every part of the account is affected.

How we measure this

  • We request TeamViewer's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where TeamViewer publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when TeamViewer goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required