rewindex

CompaniesDialpadIncidents

Dialpad: Partial WebRTC call outage

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.dialpad.com (opens in new tab)

Timeline of updates

  1. resolved

    Between 3:41PM and 4PM PST we experienced some registration issues with our WebRTC calls, causing some of the new calls from the Chrome app and Obi phones to fail during this time period. Calls in progress were not affected. Traffic was back to normal by 4PM.

From Dialpad’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.dialpad.com (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Dialpad, started 2015-05-13 01:23 UTC, resolved after 0 min, 1 update(s).

Title
Partial WebRTC call outage
Vendor
Dialpad
Date
URL
https://rewindex.com/company/dialpad/incidents/bx9j9xgdp08m

Dialpad profileRecent Dialpad incidentsAll outages on May 13, 2015Dialpad in May 2015MarkdownJSON