← Back to Twilio History
minor✓ Resolved
Reassigned Number Package Degradation for Lookup V2 API
Status
resolved
Duration
29 minutes
Updates
3
Coverage
0 articles
INCIDENT TIMELINE
✓ ResolvedTue, Apr 14, 2026, 09:20 PM
This incident has been resolved.
monitoringTue, Apr 14, 2026, 09:11 PM
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.
investigatingTue, Apr 14, 2026, 08:51 PM
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
investigatingTue, Apr 14, 2026, 08:51 PM
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
📊 TECHNICAL DETAILS
Internal ID
b5c43e68-68e9-4073-ba0f-aa66a1e59000
External ID
y4bd7y66vkj9
🕐 Started
Tue, Apr 14, 2026, 08:51 PM
🔄 Last Updated
Tue, Apr 14, 2026, 09:20 PM
✓ Resolved
Tue, Apr 14, 2026, 09:20 PM
MINOR
Impact Level
29 minutes
Total Duration
3
Status Updates
Affected Components
Lookup
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed