Vendor reports: major outageResolved · vendor status “resolved”Official status API

CloudLink Daemon Service Disruption for MCX/MiCC

Reported by Mitel · Communication & Messaging · source last read 2 min ago

Official source (opens in a new tab)
Vendor start
Mar 24, 2026, 09:23 UTC
Vendor's clock
Resolved
Mar 25, 2026, 11:30 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
1 d 2 h
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

  • Mitel reports major outage: "CloudLink Daemon Service Disruption for MCX/MiCC".[E1, E2]
  • The vendor marked it resolved at 2026-03-25 11:30 UTC.[E3, E7]

Affected products and regions

  • Components: Tunnel.[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: 2026-03-25 11:30 UTC · summary s1, evidence ab4f473cb5e53971

Evidence (7)
  1. E1Mitel reports major outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "CloudLink Daemon Service Disruption for MCX/MiCC". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-03-24 09:23 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Tunnel. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-03-25 11:30 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Tunnel

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Mitel 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 24, 2026, 09:23 UTCVendor-reported startVendor time
  2. Mar 25, 2026, 11:30 UTCVendor-reported resolutionVendor time

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