Twilio: Character encoding issues on inbound SMS from Verizon handsets to Twilio
Timeline of updates
- resolved
We are observing full recovery on the character encoding issues for inbound SMS to Twilio numbers from Verizon Handsets. This incident is now resolved.
From Twilio’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.twilio.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Twilio, started 2020-08-04 16:43 UTC, resolved after 1.2 h, 1 update(s).
- Title
- Character encoding issues on inbound SMS from Verizon handsets to Twilio
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/d4v7c400bhs6
Twilio profileRecent Twilio incidentsAll outages on August 4, 2020Twilio in August 2020MarkdownJSON