All systems are operating normally at this time. The data returned by the Message List and Message Instance REST API resources may be slightly delayed for some customers. Processing on these delayed records is in progress and will complete shortly.
Posted Sep 26, 2016 - 17:20 PDT
Update
Twilio Engineering has deployed and verified a final fix for the earlier issue. HTTP 500 responses to Feedback API requests are no longer occurring, and the latency for HTTP GET requests for Message instance and list resources has returned to normal.
Posted Sep 26, 2016 - 13:54 PDT
Update
The Message Feedback REST API continues to return a low rate of HTTP 500 responses. Additionally, GET requests to Message instance resources for recently sent Messages may return an HTTP 404 response, and GET requests to the Messages list resource may not return the complete list of all recent Messages. Twilio Engineering continues to troubleshoot both issues.
Posted Sep 26, 2016 - 13:27 PDT
Update
The rate of HTTP 500 responses from the Message Feedback API has dropped significantly, however some HTTP 500 responses are still being returned. Some responses to Feedback API requests are also seeing higher than normal latency. Twilio Engineering continues to investigate both issues.
Posted Sep 26, 2016 - 13:04 PDT
Monitoring
We are seeing a decrease in the rate of HTTP 500 responses from the Message Feedback REST API due to a fix deployed by Twilio Engineering. We are continuing to monitor the issue.
Posted Sep 26, 2016 - 12:45 PDT
Investigating
Twilio’s Message Feedback REST API (https://www.twilio.com/docs/api/rest/message/feedback) is currently returning HTTP 500 responses to all requests, and the related feedback requests are not being recorded. Twilio engineering is investigating the issue and will post an update shortly.
Posted Sep 26, 2016 - 12:43 PDT
This incident affected: CARRIER NETWORK (SMS Short Code, North America) and PROGRAMMABLE MESSAGING (MMS, SMS).