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

Some customers may be experiencing issues receiving text messages

Reported by Dialpad · Communication & Messaging · source last read 4 min ago

Official source (opens in a new tab)
Vendor start
Jun 26, 2025, 20:51 UTC
Vendor's clock
Resolved
Jun 26, 2025, 21:37 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
47 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

  • Dialpad reports degraded: "Some customers may be experiencing issues receiving text messages".[E1, E2]
  • The vendor marked it resolved at 2025-06-26 21:37 UTC.[E3, E7]

Affected products and regions

  • Components: Carrier Networks: Messaging.[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-06-26 21:37 UTC · summary s1, evidence fd4cc1608a828232

Evidence (7)
  1. E1Dialpad reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Some customers may be experiencing issues receiving text messages". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-06-26 20:51 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Carrier Networks: Messaging. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2025-06-26 21:37 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Carrier Networks: Messaging

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

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. Jun 26, 2025, 20:51 UTCVendor-reported startVendor time
  2. Jun 26, 2025, 21:37 UTCVendor-reported resolutionVendor time

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