Twilio incident
Increase in 502 HTTP Responses for REST API and Console
Twilio experienced a minor incident on September 1, 2026 affecting REST API, lasting 1h 47m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 01, 2026, 04:24 PM UTC
Our monitoring systems have detected a potential issue with Increase in 502 HTTP responses for various Edge Config managed ingresses. Our engineers have been alerted and are investigating. We will provide an update when we have more details.
- investigating Sep 01, 2026, 04:44 PM UTC
Our engineers have identified and issue where Customers may experience 502 Errors when accesing Console or making REST API Calls and are investigating. We expect to provide another update in 1 hour or as soon as more information becomes available.
- investigating Sep 01, 2026, 05:15 PM UTC
Our engineers have identified and issue where Customers may experience 502 Errors when accessing Console or making REST API Calls and are investigating. We expect to provide another update in 1 hour or as soon as more information becomes available.
- monitoring Sep 01, 2026, 05:40 PM UTC
Increase in 502 HTTP responses for various Edge Config managed ingresses are now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.
- resolved Sep 01, 2026, 06:11 PM UTC
Increase in 502 HTTP responses for various Edge Config managed ingresses has been resolved and is operating normally at this time.