AnyDesk Outage History

30 incidents recorded over the last 365 days, 20 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded AnyDesk Incident

AnyDesk incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 13, 2026my.anydesk II API DegradedThis incident has been resolved.25 minResolved
Jul 13, 2026Outage - my.anydesk IIThis incident has been resolved.3h 20mResolved
Jun 28, 2026Scheduled Maintenance my.anydesk IIThe scheduled maintenance has been completed.2h 0mScheduled
Jun 27, 2026Scheduled Maintenance my.anydesk IIThe scheduled maintenance has been completed.2h 0mScheduled
Jun 27, 2026Major outage - my.anydesk IIWe can confirm the issue is properly fixed, as we did not see any issues during our extended monitoring period. We again apologise for any inconvenience caused during this time.27h 30mResolved
Jun 16, 2026REST API OutageThis incident has been resolved.2h 22mResolved
May 31, 2026Global Network MaintenanceThe scheduled maintenance has been completed.8h 0mScheduled
May 30, 2026Global Network maintenanceThe scheduled maintenance has been completed.8h 0mScheduled
May 22, 2026Service Degradation - macOS Custom Client BuildsThis incident has been resolved.25 minResolved
May 4, 2026MacOS custom builds impactedThis incident has been resolved.4h 32mResolved
Apr 28, 2026Partial outage - Taiwan and Hong KongThis incident has been resolved. Customers in Taiwan and Hong Kong are now routed back to their original zone.189h 30mResolved
Apr 25, 2026Global Network maintenanceThe scheduled maintenance has been completed.8h 0mScheduled
Apr 18, 2026Service degradation - IndiaThis incident has been resolved.14h 52mResolved
Mar 16, 2026Major outage - AnyDesk NetworkThis incident has been resolved.49 minResolved
Mar 13, 2026Scheduled maintenance - my.anydesk I / my.anydesk IIThe scheduled maintenance has been completed.2h 0mScheduled
Feb 27, 2026Service Degradation - Custom Client BuildsThis incident has been resolved.124h 52mResolved
Feb 25, 2026Service Degradation - South AmericaThis incident has been resolved.52h 11mResolved
Feb 3, 2026Service degradation - Eastern Europe, Western AsiaThis incident has been resolved.6h 11mResolved
Jan 22, 2026Service DegradationThis incident has been resolved.4h 51mResolved
Dec 22, 2025Service Degradation - my.anydesk IIThis incident has been resolved.1h 7mResolved
Dec 4, 2025Customer portal general maintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Dec 2, 2025Shop general maintenanceThe scheduled maintenance has been completed.1h 30mScheduled
Dec 1, 2025Service Degradation - my.anydesk IIThis incident has been resolved.11h 8mResolved
Nov 24, 2025Service Degradation - my.anydesk IIThis incident has been resolved.2h 58mResolved
Nov 24, 2025Website general maintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Nov 21, 2025Outage - my.anydesk IIThis incident has been resolved.1h 54mResolved
Nov 19, 2025Major outage - my.anydesk IIThis incident has been resolved.1h 5mResolved
Nov 18, 2025Service DegradationThis incident has been resolved.2h 26mResolved
Nov 17, 2025Outage - Online shopThis incident has been resolved.7h 59mResolved
Nov 5, 2025Web Pages - Scheduled maintenanceThe scheduled maintenance has been completed.2h 0mScheduled

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next AnyDesk incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This AnyDesk Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before AnyDesk acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single AnyDesk outage in this window ran 7d 21h, against a mean recovery of 16h 32m. If you depend on AnyDesk in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.