Dialpad: Call Failures
Timeline of updates
- resolved
Between 4:14 PM and 4:28 PM PDT, we experienced some high latency in Google Cloud that resulted in some calls not being connected. We are looking into the cause and the extent of the impact of this issue"
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 2018-10-12 00:20 UTC, resolved after 0 min, 1 update(s).
- Title
- Call Failures
- Vendor
- Dialpad
- Date
- URL
- https://rewindex.com/company/dialpad/incidents/2dy76ln7rvw8
Dialpad profileRecent Dialpad incidentsAll outages on October 12, 2018Dialpad in October 2018MarkdownJSON