Dialpad: Call routing issue during version transition
Timeline of updates
- resolved
Between Dec-14 00:18 UTC and 00:34 UTC, up to 25% of inbound and outbound calls may have failed to connect. An incompatibility between backend server versions caused calls which were partially processed by each version to fail. Retries had a random chance to encounter the same error with a peak probability of 25% during the deployment.
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: minor) posted by Dialpad, started 2023-12-15 00:18 UTC, resolved after 0 min, 1 update(s).
- Title
- Call routing issue during version transition
- Vendor
- Dialpad
- Date
- URL
- https://rewindex.com/company/dialpad/incidents/jgrjss49s8hn
Dialpad profileRecent Dialpad incidentsAll outages on December 15, 2023Dialpad in December 2023MarkdownJSON