Twilio: Special characters being incorrectly formatted in outbound SMS to Verizon Network in US
Timeline of updates
- resolved
This root cause of this issue has been identified by our carrier partner, and the expected time of resolution is Thursday into Friday over night PDT. We will continue to work with our carrier partner on their fix implementation and test verification. Please reach out to support@twilio.com if you have any concerns and questions.
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-04-14 12:59 UTC, resolved after 26 min, 1 update(s).
- Title
- Special characters being incorrectly formatted in outbound SMS to Verizon Network in US
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/rdl0wjrcv85b
Twilio profileRecent Twilio incidentsAll outages on April 14, 2020Twilio in April 2020MarkdownJSON