Twilio: Elevated API Latency and 500s for Voice and Messaging
Timeline of updates
- resolved
Between 11:55 am and 2:05 pm PDT today, July 17th, we experienced intermittent increases in API latency and 500s for API requests across Programmable Voice and Messaging. The errors primarily occurred during two separate impact windows. The first window started at 11:55 am and continued to 12:38 pm PDT while the second window was from 1:54 pm to 2:05 pm PDT. Affected requests experienced either high latency or failed with 500 HTTP error responses. The situation has since been resolved and all systems are functioning 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 2019-07-17 22:57 UTC, resolved after 0 min, 1 update(s).
- Title
- Elevated API Latency and 500s for Voice and Messaging
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/zskqrywyz2g5
Twilio profileRecent Twilio incidentsAll outages on July 17, 2019Twilio in July 2019MarkdownJSON