On Call Engineers are Investigating an issue with Flex
The issue affecting Flex has been resolved and the service is operating normally at this time.
The issue affecting Flex has been resolved and the service is operating normally at this time.
We have fully investigated the Flex issue triggered by our automated alert, and it was determined that there is no noticeable customer impact. All systems are operational.
We have fully investigated the Call Failures to a subset of Twilio's Phone numbers in Brazil issue, and it was determined that the impact was limited to a small set of customers, who have been contacted individually to address any concerns. All systems are operational.
Twilio Programmable Messaging was degraded for 23 hours between Jan 13th 2025, 2:20AM PST until Jan 14th 2025, 1:26AM PST. During this period of time customers may have experienced a small number of messages sent were not properly updated to a finalized status (FAILED or DELIVERY_UNKNOWN). Consequently, callbacks and EventStream events for these status updates were not triggered. Messages sent after January 14 are unaffected. The issue has now been resolved.
We are no longer experiencing SMS delivery delays when sending messages to Tigo in Chad. This incident has been resolved.
We are no longer experiencing SMS delivery delays when sending messages to MTS Network in Belarus. This incident has been resolved.
We are no longer experiencing issues with AccSec - US API Errors. This incident has been resolved.
We are no longer experiencing SMS delivery delays and failures to network in India from a subset of Twilio Shortcodes. This incident has been resolved.
We are no longer experiencing issue with SMS Delivery Delays To Claro Network In Dominican Republic. This incident has been resolved.
On January 17, 2025, at 5:11 PM PST, Twilio executed a bulk suspension involving 16,702 subaccounts, mistakenly including some active customer parent accounts. This error disrupted SMS and Voice services for those affected. Initial ad hoc reactivations began within 12-18 hours, but complete restoration took 39 hours, concluding on January 20 at 8:01 AM PST. The issue has now been resolved.