Skip to main content

Is TeamViewer Down?

No — TeamViewer is up

Reachable from all 8 checked regions

Average response time: 780ms

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
435ms
Avg response, 30 days

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

30-day history

9-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: 100.00% uptime, 16 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 32 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 23 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 32 checks
Jul 25 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
190ms
DNS 1ms TCP 2ms TLS 13ms TTFB 186ms
arn
304ms
DNS 0ms TCP 1ms TLS 12ms TTFB 296ms
bom
1206ms
DNS 1ms TCP 4ms TLS 14ms TTFB 1202ms
nrt
293ms
DNS 0ms TCP 1ms TLS 11ms TTFB 288ms
ord
1117ms
DNS 1ms TCP 2ms TLS 14ms TTFB 1113ms
sin
280ms
DNS 0ms TCP 2ms TLS 12ms TTFB 276ms
sjc
1788ms
DNS 0ms TCP 1ms TLS 11ms TTFB 1784ms
syd
398ms
DNS 0ms TCP 1ms TLS 10ms TTFB 393ms
yyz
957ms
DNS 0ms TCP 1ms TLS 9ms TTFB 953ms

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 all 18 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 — 8 of them answered the most recent check.
  • 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 the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required