Scheduled maintenance
Twilio Services
Issues related to Twilio’s Software
External Connectivity
Issues found outside of Twilio’s Network
Zipwhip Gateway
Issues related to Zipwhip's Services
System Metrics
Elevated Error Rates and Latency in Studio Call & Message Handling
Incident
Report for Twilio
Resolved
Starting Friday 9/24 from 7:00am PST through Monday 9/27 1:00am PST, we experienced elevated error rates in processing Voice and Messaging webhook events and REST API requests for Studio executions. We are no longer experiencing these issues. This incident has been resolved.
Update
We are observing recovery related to the increased error rates and latency in processing Voice and Messaging webhook events and REST API requests for Studio Executions. We will continue monitoring the service to ensure a full recovery. We will provide another update in 30 minutes or as soon as more information becomes available.
Update
We are observing recovery related to the increased error rates and latency in processing Voice and Messaging webhook events and REST API requests for Studio Executions. We will continue monitoring the service to ensure a full recovery. We will provide another update in 30 minutes or as soon as more information becomes available.
Monitoring
We are observing recovery related to the increased error rates and latency in processing Voice and Messaging webhook events and REST API requests for Studio Executions. We will continue monitoring the service to ensure a full recovery. We will provide another update in 30 minutes or as soon as more information becomes available.
Update
Our engineers continue to work on provisioning additional capacity to resolve the increased error rates and latency in processing Voice and Messaging webhook events and REST API requests for Studio Executions. We anticipate the situation stays unchanged over the weekend, and we will provide another update in 24 hours or as soon as more information becomes available.
Update
Our engineers continue to work on provisioning additional capacity to resolve the increased error rates and latency in processing Voice and Messaging webhook events and REST API requests for Studio Executions. We anticipate the situation stays unchanged over the weekend, and we will provide another update in 24 hours or as soon as more information becomes available.
Update
Our engineers continue to work on provisioning additional capacity to resolve the increased error rates and latency in processing Voice and Messaging webhook events and REST API requests for Studio Executions. We anticipate the situation stays unchanged over the weekend, and we will provide another update in 24 hours or as soon as more information becomes available.
Identified
Our engineers have identified a capacity problem causing increased error rates and latency in processing Voice and Messaging webhook events and REST API requests for Studio Executions, and are working to provision additional capacity. We expect to provide another update in 8 hours or as soon as more information becomes available.
Update
Studio service degradation is causing increased error rates and latency in processing Voice and Messaging webhook events and REST API requests for Executions. Our engineers are working to resolve the issue. We will provide another update in 4 hours or as soon as more information becomes available.
Update
Studio service degradation is causing increased error rates and latency in processing Voice and Messaging webhook events and REST API requests for Executions. Our engineers are working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available.
Update
Studio service degradation is causing increased error rates and latency in processing Voice and Messaging webhook events and REST API requests for Executions. Our engineers are working to resolve the issue. We will provide an update in 1 hour or as soon as more information becomes available.
Investigating
Our monitoring systems have detected a potential issue with Studio. Our engineering team has been alerted and is actively investigating. We will update as soon as we have more information.
This incident affected: SERVERLESS (Studio).