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
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 13, 2026 | my.anydesk II API DegradedThis incident has been resolved. | 25 min | Resolved |
| Jul 13, 2026 | Outage - my.anydesk IIThis incident has been resolved. | 3h 20m | Resolved |
| Jun 28, 2026 | Scheduled Maintenance my.anydesk IIThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jun 27, 2026 | Scheduled Maintenance my.anydesk IIThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jun 27, 2026 | Major 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 30m | Resolved |
| Jun 16, 2026 | REST API OutageThis incident has been resolved. | 2h 22m | Resolved |
| May 31, 2026 | Global Network MaintenanceThe scheduled maintenance has been completed. | 8h 0m | Scheduled |
| May 30, 2026 | Global Network maintenanceThe scheduled maintenance has been completed. | 8h 0m | Scheduled |
| May 22, 2026 | Service Degradation - macOS Custom Client BuildsThis incident has been resolved. | 25 min | Resolved |
| May 4, 2026 | MacOS custom builds impactedThis incident has been resolved. | 4h 32m | Resolved |
| Apr 28, 2026 | Partial outage - Taiwan and Hong KongThis incident has been resolved. Customers in Taiwan and Hong Kong are now routed back to their original zone. | 189h 30m | Resolved |
| Apr 25, 2026 | Global Network maintenanceThe scheduled maintenance has been completed. | 8h 0m | Scheduled |
| Apr 18, 2026 | Service degradation - IndiaThis incident has been resolved. | 14h 52m | Resolved |
| Mar 16, 2026 | Major outage - AnyDesk NetworkThis incident has been resolved. | 49 min | Resolved |
| Mar 13, 2026 | Scheduled maintenance - my.anydesk I / my.anydesk IIThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Feb 27, 2026 | Service Degradation - Custom Client BuildsThis incident has been resolved. | 124h 52m | Resolved |
| Feb 25, 2026 | Service Degradation - South AmericaThis incident has been resolved. | 52h 11m | Resolved |
| Feb 3, 2026 | Service degradation - Eastern Europe, Western AsiaThis incident has been resolved. | 6h 11m | Resolved |
| Jan 22, 2026 | Service DegradationThis incident has been resolved. | 4h 51m | Resolved |
| Dec 22, 2025 | Service Degradation - my.anydesk IIThis incident has been resolved. | 1h 7m | Resolved |
| Dec 4, 2025 | Customer portal general maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Dec 2, 2025 | Shop general maintenanceThe scheduled maintenance has been completed. | 1h 30m | Scheduled |
| Dec 1, 2025 | Service Degradation - my.anydesk IIThis incident has been resolved. | 11h 8m | Resolved |
| Nov 24, 2025 | Service Degradation - my.anydesk IIThis incident has been resolved. | 2h 58m | Resolved |
| Nov 24, 2025 | Website general maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Nov 21, 2025 | Outage - my.anydesk IIThis incident has been resolved. | 1h 54m | Resolved |
| Nov 19, 2025 | Major outage - my.anydesk IIThis incident has been resolved. | 1h 5m | Resolved |
| Nov 18, 2025 | Service DegradationThis incident has been resolved. | 2h 26m | Resolved |
| Nov 17, 2025 | Outage - Online shopThis incident has been resolved. | 7h 59m | Resolved |
| Nov 5, 2025 | Web Pages - Scheduled maintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
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.