TeamViewer status history
Current state: operational — “All Systems Operational” per https://status.teamviewer.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do TeamViewer incidents last?
From 26 incidents with a vendor-posted start and resolve time. Longest on record: DEX Platform licensing service. Affected environments are unable to retrieve licensing information, — 5.0 days (2026-06-27 17:46 UTC). Excluded, never estimated: 2 scheduled maintenance. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (28)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-10 11:00 UTC | DEX Solutions 26.9 Upgrade | US East 1 | maintenance | maintenance | 25 h 29 min (approx.) |
| 2026-09-08 12:00 UTC | DEX Solutions 26.9 Upgrade | CA Central 1 | maintenance | maintenance | 24 h 30 min (approx.) |
| 2026-09-01 14:30 UTC | WestUS2 - Intermittent Login Issues | resolved | major | 0 min |
| 2026-08-27 09:37 UTC | Major outage of TeamViewer services | resolved | critical | 3 min |
| 2026-08-17 14:52 UTC | Partial DNS Outage | resolved | minor | 7 h 39 min |
| 2026-07-17 13:12 UTC | DEX PLATFORM. Inventory Software pages not loading | resolved | major | 3 d 6 h |
| 2026-06-27 17:46 UTC | DEX Platform licensing service. Affected environments are unable to retrieve licensing information, | resolved | critical | 4 d 23 h |
| 2026-06-22 13:37 UTC | Login issues | resolved | minor | 23 min |
| 2026-06-10 07:32 UTC | Community outage | resolved | critical | 58 min |
| 2026-06-10 06:41 UTC | Degraded Performance - Custom modules | resolved | minor | 1 h 11 min |
| 2026-04-28 05:46 UTC | Degraded Performance - Managed devices | resolved | minor | 1 h 32 min |
| 2026-04-23 06:20 UTC | DEX Connectivity issue - UK South 1 | resolved | critical | 1 h 29 min |
| 2026-04-17 08:53 UTC | Managed devices | resolved | major | 1 h 03 min |
| 2026-04-13 09:35 UTC | Managed devices | resolved | critical | 50 min |
| 2026-03-25 11:50 UTC | Issue with TeamViewer license validation | resolved | minor | 43 min |
| 2026-03-10 09:09 UTC | High load on TeamViewer Services | resolved | critical | 40 min |
| 2026-03-03 16:01 UTC | DEX Client Connectivity issues with West Europe 1 | resolved | minor | 3 h 12 min |
| 2026-02-13 11:37 UTC | TeamViewer services - degraded performance | resolved | minor | 1 h 35 min |
| 2026-01-27 10:12 UTC | Potential delay when sending product e-mails | resolved | minor | 32 min |
| 2025-12-10 08:59 UTC | Device groups are not loading | resolved | major | 2 h 44 min |
| 2025-12-09 09:55 UTC | Device groups are not loading | resolved | major | 52 min |
| 2025-12-05 08:55 UTC | TeamViewer Ticketsystem and Community not reachable | resolved | critical | 40 min |
| 2025-12-04 10:16 UTC | Device groups not loading | resolved | major | 1 h 02 min |
| 2025-11-19 20:26 UTC | Management Console (MCO) not loading | resolved | critical | 3 d 23 h |
| 2025-11-17 16:12 UTC | TFA for connections - push notifications incident | resolved | major | 2 h 04 min |
| 2025-11-05 09:45 UTC | Partnerlist Issue | resolved | major | 23 min |
| 2025-10-30 14:46 UTC | License activation issue | resolved | major | 22 min |
| 2025-10-29 16:05 UTC | Web.teamviewer.com unavailable | resolved | major | 3 h 37 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch TeamViewer with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"teamviewer"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}