rewindex

ChangesTwilioPotential Issue with Realtime Transcriptions and Deepgram

Twilio: Incident silently edited: Potential Issue with Realtime Transcriptions and Deepgram

Silent editNormal progress (typesafe/jev-1.13-20260917, 95%)Changed status.twilio.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Twilio removed; blue is what they added. Muted text is unchanged context.

ChangedUpdateinvestigating#1
Before: …provide an update when we have more details. nothing here details.…
After: …provide an update when we have more details. Customers are recommended to move to Google as a temporary workaround until we have additional details.…

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

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. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

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

History of this incident

Thursday, October 22

1 rewrite, 2 incident changes

Cite this

Incident silently edited: Potential Issue with Realtime Transcriptions and Deepgram on Twilio’s status page, changed 2026-10-22 16:53 UTC (change 1 of 3).

Title
Incident silently edited: Potential Issue with Realtime Transcriptions and Deepgram
Vendor
Twilio
Date
URL
https://rewindex.com/change/r9d98eee440e527

All Twilio changesTwilio profileMarkdownJSON