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

Issues answering calls on Google Chrome and MS Edge using the external notification

Reported by Dialpad · Communication & Messaging · source last read just now

Official source (opens in a new tab)
Vendor start
Apr 11, 2025, 21:13 UTC
Vendor's clock
Resolved
Apr 14, 2025, 18:36 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
2 d 21 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

  • Dialpad reports degraded: "Issues answering calls on Google Chrome and MS Edge using the external notification".[E1, E2]
  • The vendor marked it resolved at 2025-04-14 18:36 UTC.[E3, E7]

Affected products and regions

  • Components: Application.[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-14 18:36 UTC · summary s1, evidence 76a7f0821542014b

Evidence (7)
  1. E1Dialpad reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Issues answering calls on Google Chrome and MS Edge using the external notification". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-04-11 21:13 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Application. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2025-04-14 18:36 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Application

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

Potential relevance

Dialpad 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. Apr 11, 2025, 21:13 UTCVendor-reported startVendor time
  2. Apr 14, 2025, 18:36 UTCVendor-reported resolutionVendor time

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