Twilio: Invalid Special Characters Rendering for Japanese Invoices
Timeline of updates
- resolved
Our engineers have implemented a fix for the issue for invalid special characters rendering for Japanese invoices. 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 2023-12-12 13:18 UTC, resolved after 2 d, 1 update(s).
- Title
- Invalid Special Characters Rendering for Japanese Invoices
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/jqjt4t26j81p
Twilio profileRecent Twilio incidentsAll outages on December 12, 2023Twilio in December 2023MarkdownJSON