TeamViewer outages and problems
In the past 24 hours, 2 user reports came in for TeamViewer. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.
The busiest 15-minute window had 1 report, about 9 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
What TeamViewer's status page says
Checking status.teamviewer.com…
TeamViewer in November 2026
- Problem reports in November
- 0
Monthly report for November 2026
What went wrong
What people said was wrong in recent problem reports for TeamViewer worldwide.
Share of 1 recent report that said what was wrong, from every country listed below.
TeamViewer reports around the world
In the last 24 hours, 9 problem reports about TeamViewer came in from 7 countries. Right now reports are at the usual level in every country.
- Outage now
- Problems now
- Normal
| Country | Now | Last hour | 24 hours |
|---|---|---|---|
| Italy | Normal | 1 | 1 |
| Brazil | Normal | 0 | 2 |
| Japan | Normal | 0 | 2 |
| The US numbers above | Normal | 0 | 1 |
| Germany | Normal | 0 | 1 |
| Austria | Normal | 0 | 1 |
| Poland | Normal | 0 | 1 |
| The Netherlands | Normal | 0 | 0 |
| India | Normal | 0 | 0 |
| Russia | Normal | 0 | 0 |
| The UK | Normal | 0 | 0 |
| Australia | Normal | 0 | 0 |
Each country's status compares its reports with the usual level there. 13 more countries had 0 reports in the last 24 hours. Map outlines: Natural Earth.
TeamViewer problem spikes, last 30 days
Since 8 October, TeamViewer had no outage spikes or periods of elevated reports.
- Sat 3 Oct: no data
- Sun 4 Oct: no data
- Mon 5 Oct: no data
- Tue 6 Oct: no data
- Wed 7 Oct: no data
- Thu 8 Oct: 1 report
- Fri 9 Oct: 0 reports
- Sat 10 Oct: 0 reports
- Sun 11 Oct: 0 reports
- Mon 12 Oct: 1 report
- Tue 13 Oct: 1 report
- Wed 14 Oct: 0 reports
- Thu 15 Oct: 2 reports
- Fri 16 Oct: 1 report
- Sat 17 Oct: 0 reports
- Sun 18 Oct: 0 reports
- Mon 19 Oct: 2 reports
- Tue 20 Oct: 0 reports
- Wed 21 Oct: no data
- Thu 22 Oct: 0 reports
- Fri 23 Oct: 1 report
- Sat 24 Oct: 0 reports
- Sun 25 Oct: 1 report
- Mon 26 Oct: 3 reports
- Tue 27 Oct: 7 reports
- Wed 28 Oct: 7 reports
- Thu 29 Oct: 24 reports
- Fri 30 Oct: 16 reports
- Sat 31 Oct: 2 reports
- Sun 1 Nov: 0 reports
By country
Each square is one day in the countries with the most reports: red when reports stayed at outage level for half an hour or more, amber when they stayed above the usual level for an hour or more, grey otherwise.
- Germany63
- The US50
- Brazil25
- Poland21
- The Netherlands15
- The UK13
- France10
- Mexico9
Country history starts on 28 October 2026. Days run from midnight to midnight, Central European time.
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 8 October 2026. Monthly reports for all services
How to fix TeamViewer not working
TeamViewer is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach teamviewer.com over your own connection, right now. Nothing is sent to us or stored.
Reopen TeamViewer and recheck the ID
Close and reopen the app from the tray or menu bar, then read the ID and password in the main window to the person who is connecting. If the password is hidden, check the current value under Extras > Options > Security before you use it.
Restart the TeamViewer service
On Windows, press Windows+R and run services.msc. Right-click the TeamViewer service, choose Restart, then reopen the app and try the connection again.
Allow TeamViewer through the firewall
In Windows Security, open Firewall & network protection, then Allow an app through firewall and tick Private and Public for the TeamViewer entries. If the connection still fails on a managed network, ask the admin to allow outbound TCP and UDP 5938; if that fails, allow TCP 443 as the fallback.
Repair the TeamViewer installation
Open Help > Check for Updates and install any update before you change the installation. If the app still fails, run the current full installer and choose Repair; if Repair does not fix it, choose Remove and install again.
While TeamViewer is down: what to use instead
- AnyDesk Use it for a quick remote desktop session when you need to control another computer or help someone troubleshoot.
- Chrome Remote Desktop Use it when both computers have Chrome and you want browser based access to a configured remote machine.
- Windows Remote Desktop Use it to connect to a Windows PC that already has remote access enabled and is reachable on its network.
- Splashtop Use it for remote access to a computer when you already have its app installed and configured.
Fix TeamViewer on Windows, Mac, Android and iPhone
TeamViewer on Windows
- Fix
- Restart the TeamViewer service in the Windows Services manager or relaunch the application as administrator. Also, ensure Windows Defender Firewall is not blocking TeamViewer's internet access.
- Check
- Check if the status indicator in the bottom-left corner of the TeamViewer app is green, indicating a successful connection. If it shows a red light or fails to generate a partner ID, the TeamViewer network may be down.
ping teamviewer.comTest whether TeamViewer's servers replynslookup teamviewer.comCheck that TeamViewer's DNS resolvestracert teamviewer.comTrace where the connection dropsipconfig /flushdnsClear the DNS cache, then reloadTeamViewer on Mac
- Fix
- Ensure TeamViewer has been granted Screen Recording and Accessibility permissions in macOS System Settings. If connection issues persist, force quit the app and restart it.
- Check
- Open the TeamViewer app and verify if the connection status indicator at the bottom is green. If it remains red or shows 'Ready to connect', TeamViewer might be experiencing a service outage.
ping -c 4 teamviewer.comTest whether TeamViewer's servers replynslookup teamviewer.comCheck that TeamViewer's DNS resolvestraceroute teamviewer.comTrace where the connection dropssudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reloadTeamViewer on Android
- Fix
- Clear the cache for the TeamViewer app in your Android Settings and ensure it has unrestricted background data access. If the issue persists, update or reinstall TeamViewer from the Google Play Store.
- Check
- Open the TeamViewer app on your Android device and check if it successfully generates your ID. If you receive a 'No connection to partner' or connection timeout error, TeamViewer servers might be offline.
TeamViewer on iPhone and iPad
- Fix
- Ensure that Local Network permission is enabled for TeamViewer in your iOS Settings, then restart the app. If it still fails, reinstall TeamViewer from the App Store.
- Check
- Open the TeamViewer app on your iOS device and check if your ID is displayed and the connection status is active. A persistent 'Connecting...' message or failure to retrieve your ID suggests a TeamViewer service disruption.
What happens when TeamViewer goes down
TeamViewer is remote access and support software that lets you control another computer and move files between devices; IT help desks and remote workers in the US use it to reach machines they cannot sit in front of. An outage interrupts those sessions, so a stalled connection or a login that will not complete can leave a support call or a work task stuck.
Sign-in tends to break first, so the app may sit on a loading screen or return a connection error before a session starts. Existing sessions can drop. New connections stall at the connecting stage even when both computers have working internet, and file transfer or remote printing fails with the session because each uses the same link. Trouble is often partial or regional: one sign-in route or relay can fail while another works, so two people in different places may get different results.
TeamViewer IP address, servers and network
- IPv4 addresses
- 104.16.62.16
Show all 2
- 104.16.63.16
- IPv6 addresses
- 2606:4700::6810:3e10
Show all 2
- 2606:4700::6810:3f10
- Network
- AS13335 · Cloudflare, Inc., registered in the United States
- Served through
- Cloudflare · our check was answered by its Frankfurt (FRA) data centre
- DNS hosted by
- its own name servers (teamviewer.com)
- HTTPS certificate
- Issued by Sectigo Limited, valid until 19 Apr 2027 (168 days)
- HTTP/3
- Supported
- Our check
- Answered in 155 ms
Checked from our server in Frankfurt, Germany, 3 days ago, for www.teamviewer.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
Checked from 11 places around the world
All 11 locations got an answer from www.teamviewer.com. Fastest from Milan (26 ms), slowest from Warsaw (139 ms). Every location connected through Cloudflare, Inc. (AS13335), using 2 different addresses.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up · HTTP 302 | 58 ms | 104.16.63.16 |
| ViennaAustria | Up · HTTP 302 | 59 ms | 104.16.62.16 |
| MilanItaly | Up · HTTP 302 | 26 ms | 104.16.63.16 |
| ParisFrance | Up · HTTP 302 | 49 ms | 104.16.62.16 |
| AmsterdamNetherlands | Up · HTTP 302 | 43 ms | 104.16.63.16 |
| MadridSpain | Up · HTTP 302 | 28 ms | 104.16.62.16 |
| WarsawPoland | Up · HTTP 302 | 139 ms | 104.16.62.16 |
| Los AngelesUSA | Up · HTTP 302 | 63 ms | 104.16.62.16 |
| São PauloBrazil | Up · HTTP 302 | 37 ms | 104.16.63.16 |
| SingaporeSingapore | Up · HTTP 302 | 52 ms | 104.16.63.16 |
| TokyoJapan | Up · HTTP 302 | 32 ms | 104.16.62.16 |
Checked with check-host.net from its servers in these cities 5 days ago, for www.teamviewer.com. Time is how long each server took to load the page.
TeamViewer FAQ
Is TeamViewer down right now?
Why does TeamViewer say commercial use suspected on a personal session?
Why can't I connect to a remote device that shows as online in my list?
Does a TeamViewer outage stop file transfer and remote control at the same time?
Why does TeamViewer ask me to confirm my account by email after I sign in?
How we track TeamViewer
The status on this page comes from user-submitted problem reports for TeamViewer, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for TeamViewer, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from TeamViewer's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.