Vendor reports: operationalResolved · vendor status “resolved”Official status API

Major outage - My.AnyDesk II Customer Portal

Reported by AnyDesk · Productivity & Collaboration · source last read just now

Official source (opens in a new tab)
Vendor start
Mar 11, 2024, 00:00 UTC
Vendor's clock
Resolved
Mar 11, 2024, 01:01 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
1 h 1 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • AnyDesk reports operational: "Major outage - My.AnyDesk II Customer Portal".[E1, E2]
  • The vendor marked it resolved at 2024-03-11 01:01 UTC.[E3, E7]

Affected products and regions

  • Components: Customer Portal.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2024-03-11 01:01 UTC · summary s1, evidence ce82b563e9eb3f71

Evidence (7)
  1. E1AnyDesk reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Major outage - My.AnyDesk II Customer Portal". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2024-03-11 00:00 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Customer Portal. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2024-03-11 01:01 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Customer Portal

The vendor's feed gives no region for this incident. It is not assumed to be global.

Potential relevance

AnyDesk is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Mar 11, 2024, 00:00 UTCVendor-reported startVendor time
  2. Mar 11, 2024, 01:01 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.