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

[Kustomer Voice] - Call Issues

Reported by Kustomer · Customer Support · source last read 3 min ago

Official source (opens in a new tab)
Vendor start
Mar 31, 2025, 17:33 UTC
Vendor's clock
Resolved
Apr 1, 2025, 01:43 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
8 h 10 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

  • Kustomer reports degraded: "[Kustomer Voice] - Call Issues".[E1, E2]
  • The vendor marked it resolved at 2025-04-01 01:43 UTC.[E3, E7]

Affected products and regions

  • Components: Kustomer Voice.[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: 2025-04-01 01:43 UTC · summary s1, evidence c40648f5fdac2571

Evidence (7)
  1. E1Kustomer reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "[Kustomer Voice] - Call Issues". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-03-31 17:33 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Kustomer Voice. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2025-04-01 01:43 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Kustomer Voice

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

Potential relevance

Kustomer 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 31, 2025, 17:33 UTCVendor-reported startVendor time
  2. Apr 1, 2025, 01:43 UTCVendor-reported resolutionVendor time

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