Twilio incident
Degraded Experience on S/S, CNAM and VI for Select Phone Numbers
Twilio experienced a minor incident on August 31, 2026 affecting PHONE NUMBERS, lasting 7h 6m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 31, 2026, 07:37 PM UTC
Our monitoring systems have detected a potential issue. Our engineers have been alerted and are investigating. We will provide an update when we have more details.
- investigating Aug 31, 2026, 08:28 PM UTC
We are continuing to investigate this issue.
- identified Aug 31, 2026, 08:28 PM UTC
After monitoring for some time, we started seeing a degradation of the service. Some phone numbers on sub-accounts might witness degraded experience on S/S, CNAM and Voice Integrity. Our engineers are working to resolve the issue. We expect to provide another update in 1 hour or as soon as more information becomes available.
- identified Aug 31, 2026, 09:28 PM UTC
After monitoring for some time, we started seeing a degradation of the service. Some phone numbers on sub-accounts might witness degraded experience on S/S, CNAM and Voice Integrity. Our engineers are working to resolve the issue. We expect to provide another update in 2 hours or as soon as more information becomes available.
- identified Aug 31, 2026, 11:28 PM UTC
After monitoring for some time, we started seeing a degradation of the service. Some phone numbers on sub-accounts might witness degraded experience on S/S, CNAM and Voice Integrity. Our engineers are working to resolve the issue. We expect to provide another update in 4 hours or as soon as more information becomes available.
- resolved Sep 01, 2026, 02:43 AM UTC
The issue affecting S/S, CNAM, and Voice Integrity for phone numbers on sub-accounts has been successfully resolved. We have monitored the systems and confirmed that all services have returned to normal operation. We apologize for any inconvenience this may have caused and appreciate your patience.