Twilio incident
Reassigned Number Package Degradation for Lookup V2 API
Twilio experienced a minor incident on April 14, 2026 affecting Lookup, lasting 28m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 14, 2026, 08:51 PM UTC
The reassigned number package is experiencing errors in the responses returned through the API. We expect to provide another update in 1 hour or as soon as more information becomes available
- investigating Apr 14, 2026, 08:51 PM UTC
The reassigned number package is experiencing errors in the responses returned through the API. We expect to provide another update in 1 hour or as soon as more information becomes available
- monitoring Apr 14, 2026, 09:11 PM UTC
We have started seeing recovery for the reassigned number package experiencing errors in the responses returned through the API. 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.
- resolved Apr 14, 2026, 09:19 PM UTC
The issue affecting intermittent errors for the reassigned number package in the responses returned through the API has been resolved and the service is functioning normally at this time.