Twilio: On Call Engineers are Investigating Latency and 500 Errors from the API
Timeline of updates
- resolved
We have fully investigated this issue with Latency and 500 Errors from the API that was triggered by our automated alert system, and it was determined that this is related to an ongoing incident. We'll consolidate the two into a single incident. Please refer to the following link: https://status.twilio.com/incidents/45rt7tk31xcj (opens in new tab)
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 2022-02-15 17:23 UTC, resolved after 18 min, 1 update(s).
- Title
- On Call Engineers are Investigating Latency and 500 Errors from the API
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/pcy4ym8bfm4f
Twilio profileRecent Twilio incidentsAll outages on February 15, 2022Twilio in February 2022MarkdownJSON