Twilio: Content Templates Encoded Incorrectly
Timeline of updates
- resolved
Content Templates created and submitted to WhatsApp were encoded incorrectly for approximately 24 hours between 2024-02-05 09:27:57 and 2024-02-06 10:27:18 PT. During this period of time customers may have experienced non-english characters including emojis and characters containing accents appearing as '?' in sent messages. The issue has now been resolved. Customers will need to re-create the templates created during this time.
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: none) posted by Twilio, started 2024-02-06 21:47 UTC, resolved after 56 min, 1 update(s).
- Title
- Content Templates Encoded Incorrectly
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/psmzrd31mmv5
Twilio profileRecent Twilio incidentsAll outages on February 6, 2024Twilio in February 2024MarkdownJSON