Dialpad: Twitter messaging disruption
Timeline of updates
- resolved
Over the past few months, Twitter has changed their apis, access plans, and rate limits used for channel integration with public and private messages for Twitter applications without notification. These changes have caused previous access methods and the delivery model for the Dialpad Twitter channel to stop functioning. To address the situation, we will be migrating our existing Twitter channel to a new Twitter channel that supports the new access apis and rate limits. The migration will require extensive changes; thus, the Dialpad Twitter channel will be offline until the updates are completed. We expect to have the new Twitter channel available in about 3 months' time. We will provide more detailed release information and channel functionality details as they become available.
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-06-13 09:29 UTC, resolved after 8 d, 1 update(s).
- Title
- Twitter messaging disruption
- Vendor
- Dialpad
- Date
- URL
- https://rewindex.com/company/dialpad/incidents/rw8cwv75dsb2
Dialpad profileRecent Dialpad incidentsAll outages on June 13, 2023Dialpad in June 2023MarkdownJSON