The issue affecting call failures from a subset of Twilio's phone numbers to Dishwireless in US has been resolved, and the service is functioning normally at this time.
Posted Feb 13, 2026 - 10:20 PST
Monitoring
We have started seeing recovery in call failures from a subset of Twilio's phone numbers to Dishwireless in US. We will continue to monitor to ensure a full recovery. We expect to provide another update in 2 hours or as soon as more information becomes available.
Posted Feb 13, 2026 - 08:30 PST
Identified
The issue causing call failures from a subset of Twilio's phone numbers to Dishwireless in US has been identified. We are actively working with our carrier partner to resolve the issue. We expect to provide another update in 1 hour or as soon as more information becomes available.
Posted Feb 13, 2026 - 07:41 PST
Update
We continue to experience call failures from a subset of Twilio's phone numbers to Dishwireless in US. Our engineers are working with our carrier partner to resolve the issue. We expect to provide another update in 8 hours or as soon as more information becomes available.
Posted Feb 13, 2026 - 01:16 PST
Update
We continue to experience call failures from a subset of Twilio's phone numbers to Dishwireless in US. Our engineers are working with our carrier partner to resolve the issue. We expect to provide another update in 4 hours or as soon as more information becomes available.
Posted Feb 12, 2026 - 21:26 PST
Update
We continue to experience call failures from a subset of Twilio's phone numbers to Dishwireless in US. Our engineers are working with our carrier partner to resolve the issue. We expect to provide another update in 2 hours or as soon as more information becomes available.
Posted Feb 12, 2026 - 19:16 PST
Investigating
We are experiencing call failures from a subset of Twilio's phone numbers to Dishwireless in US. Our engineers are working with our carrier partner to resolve the issue. We expect to provide another update in 1 hour or as soon as more information becomes available.
Posted Feb 12, 2026 - 18:16 PST
This incident affected: CARRIER NETWORK (Voice, North America).