Vendor Status Watch

← all vendors

TeamViewer status history

Current state: operational — “All Systems Operational” per https://status.teamviewer.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

5incidents, last 30 days
8incidents, last 90 days
28incidents on record
Incidents per week, last 12 weeks:

How long do TeamViewer incidents last?

62 minmedian incident duration26 measured
7.7 h90th percentile1 in 10 ran longer
60 minmedian, major/critical only18 incidents

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)

StartedIncidentStatusImpactDuration
2026-09-10 11:00 UTCDEX Solutions 26.9 Upgrade | US East 1maintenancemaintenance25 h 29 min (approx.)
2026-09-08 12:00 UTCDEX Solutions 26.9 Upgrade | CA Central 1maintenancemaintenance24 h 30 min (approx.)
2026-09-01 14:30 UTCWestUS2 - Intermittent Login Issuesresolvedmajor0 min
2026-08-27 09:37 UTCMajor outage of TeamViewer servicesresolvedcritical3 min
2026-08-17 14:52 UTCPartial DNS Outageresolvedminor7 h 39 min
2026-07-17 13:12 UTCDEX PLATFORM. Inventory Software pages not loadingresolvedmajor3 d 6 h
2026-06-27 17:46 UTCDEX Platform licensing service. Affected environments are unable to retrieve licensing information,resolvedcritical4 d 23 h
2026-06-22 13:37 UTCLogin issuesresolvedminor23 min
2026-06-10 07:32 UTCCommunity outageresolvedcritical58 min
2026-06-10 06:41 UTCDegraded Performance - Custom modulesresolvedminor1 h 11 min
2026-04-28 05:46 UTCDegraded Performance - Managed devicesresolvedminor1 h 32 min
2026-04-23 06:20 UTCDEX Connectivity issue - UK South 1resolvedcritical1 h 29 min
2026-04-17 08:53 UTCManaged devicesresolvedmajor1 h 03 min
2026-04-13 09:35 UTCManaged devicesresolvedcritical50 min
2026-03-25 11:50 UTCIssue with TeamViewer license validationresolvedminor43 min
2026-03-10 09:09 UTCHigh load on TeamViewer Servicesresolvedcritical40 min
2026-03-03 16:01 UTCDEX Client Connectivity issues with West Europe 1resolvedminor3 h 12 min
2026-02-13 11:37 UTCTeamViewer services - degraded performanceresolvedminor1 h 35 min
2026-01-27 10:12 UTCPotential delay when sending product e-mailsresolvedminor32 min
2025-12-10 08:59 UTCDevice groups are not loadingresolvedmajor2 h 44 min
2025-12-09 09:55 UTCDevice groups are not loadingresolvedmajor52 min
2025-12-05 08:55 UTCTeamViewer Ticketsystem and Community not reachableresolvedcritical40 min
2025-12-04 10:16 UTCDevice groups not loadingresolvedmajor1 h 02 min
2025-11-19 20:26 UTCManagement Console (MCO) not loadingresolvedcritical3 d 23 h
2025-11-17 16:12 UTCTFA for connections - push notifications incidentresolvedmajor2 h 04 min
2025-11-05 09:45 UTCPartnerlist Issueresolvedmajor23 min
2025-10-30 14:46 UTCLicense activation issueresolvedmajor22 min
2025-10-29 16:05 UTCWeb.teamviewer.com unavailableresolvedmajor3 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
}