SMS Outgoing Traffic Impacted

The effects of this incident have completely passed through the system and all traffic is operating normally. This incident has been resolved. In addition to the previously described expected error codes of Validity Period Expired (30036) and Twilio Internal Error (30500), a large portion of affected messages were finalized to a Failed status (note Failed not Undelivered) with error code 30008 (Unknown Error).

We continue monitoring remaining queued messages. Overall, the system has reached a normal steady state; Now, most messages are sending without any additional queueing delay. However, individual customers may see messages remaining in queues due to large numbers of messages enqueued during this incident. We expect any messages delayed during this incident to have fully propagated through to a final status over the course of the next several hours. Note that we expect that some messages will eventually timeout and fail due to Validity Period Expired (error code 30036), others may eventually fail due to a Twilio Internal Error (error code 30500).
We will provide an update in 8 hours or as soon as more information becomes available.

We continue monitoring remaining queued messages. Overall, the system has reached a normal steady state; Now, most messages are sending without any additional queueing delay. However, individual customers may see messages remaining in queues due to large numbers of messages enqueued during this incident. We expect any messages delayed during this incident to have fully propagated through to a final status over the course of the next several hours. Note that we expect that some messages will eventually timeout and fail due to Validity Period Expired (error code 30036), others may eventually fail due to a Twilio Internal Error (error code 30500).
We will provide an update in 8 hours or as soon as more information becomes available.

We continue monitoring remaining queued messages. Overall, the system has reached a normal steady state; Now, most messages are sending without any additional queueing delay. However, individual customers may see messages remaining in queues due to large numbers of messages enqueued during this incident. We expect any messages delayed during this incident to have fully propagated through to a final status over the course of the next several hours. Note that we expect that some messages will eventually timeout and fail due to Validity Period Expired (error code 30036), others may eventually fail due to a Twilio Internal Error (error code 30500).
We will provide an update in 2 hours or as soon as more information becomes available.

We are continuing to monitor remaining queued messages. Overall, the system has reached a normal steady state; Now, most messages are sending without any additional queueing delay. However, individual customers may see messages remaining in queues due to large numbers of messages enqueued during this incident. We expect any messages delayed during this incident to have fully propagated through to a final status over the course of the next several hours. Note that we expect that some messages will eventually timeout and fail due to Validity Period Expired (error code 30036), others may eventually fail due to a Twilio Internal Error (error code 30500).
We will provide an update in 1 hour or as soon as more information becomes available.

We are continuing to monitor remaining queued messages. Overall, the system has reached a normal steady state; Now, most messages are sending without any additional queueing delay. However, individual customers may see messages remaining in queues due to large numbers of messages enqueued during this incident. We expect any messages delayed during this incident to have fully propagated through to a final status over the course of the next several hours. Note that we expect that some messages will eventually timeout and fail due to Validity Period Expired (error code 30036), others may eventually fail due to a Twilio Internal Error (error code 30500).
We will provide an update in 1 hour or as soon as more information becomes available

We are continuing to monitor remaining queued messages. Overall, the system has reached a normal steady state; Now, most messages are sending without any additional queueing delay. However, individual customers may see messages remaining in queues due to large numbers of messages enqueued during this incident. We expect any messages delayed during this incident to have fully propagated through to a final status over the course of the next several hours. Note that we expect that some messages will eventually timeout and fail due to Validity Period Expired (error code 30036), others may eventually fail due to a Twilio Internal Error (error code 30500). We'll provide an update in 1 hour or as soon as more information becomes available.

We are continuing our investigation and have discovered Conversations is affected by this issue.

We continue observing an improvement on SMS outgoing traffic. Our engineers are still monitoring the issue. We will provide another update in 2 hours or as soon as more information is available.

We continue observing an improvement on SMS outgoing traffic. Our engineers are monitoring the issue. We will provide another update in 1/2 hour or as soon as more information is available.

We are observing an improvement on SMS outgoing traffic. Our engineers are monitoring the issue. We will provide another update in 1/2 hour or as soon as more information is available.

We have identified the primary cause, taken remediating action and are beginning to see recovery from this incident with queued messages beginning to be sent. We expect to provide another update in 1 hour or as soon as more information becomes available.

We are investigating the issue with our Engineers. All outbound SMS traffic is being queued internally and not sent out to providers. We expect to provide another update in 30 minutes or as soon as more information becomes available.