Twilio: Elevated HTTP 500 Errors Affecting Messaging and Messaging Reliant Products
Timeline of updates
- resolved
For eight minutes between 6 August 2020 4:00 PM PDT to 6 August 2020 4:08 PM PDT new message requests to Twilio's Messaging API returned HTTP 500 errors for some outbound messages. Outbound messages which were already in queue at this time may have been delayed for this duration, but were not dropped. A small portion of inbound messages to Twilio during this time may have been delayed or marked as Failed, but are present within logs. This would be the case for all message channels available including; SMS, MMS, WhatsApp, and Facebook Messenger. Twilio products which rely on messages also experienced this incident including Flex, Proxy, and Studio. The issue has now been 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 2020-08-06 23:57 UTC, resolved after 0 min, 1 update(s).
- Title
- Elevated HTTP 500 Errors Affecting Messaging and Messaging Reliant Products
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/70c859khkkbt
Twilio profileRecent Twilio incidentsAll outages on August 6, 2020Twilio in August 2020MarkdownJSON