Twilio: Retroactive Incident - Issues with encoded Special Characters in email From headers
Timeline of updates
- resolved
Starting on July 16th 2026, to July 31st 2026, customers may have encountered errors when sending emails via SMTP with encoded special characters in the From header. Our engineers noticed the issue and apply a fix to correct it. There is no data loss. The issue has been resolved, and all impacted services are operating normally.
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 2026-08-05 18:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Retroactive Incident - Issues with encoded Special Characters in email From headers
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/4jlgrdh3r800
Twilio profileRecent Twilio incidentsAll outages on August 5, 2026Twilio in August 2026MarkdownJSON