Reassigned Number Package Degradation for Lookup V2 API

What to do

• Check whether you use Twilio Lookup. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 28m it lasted.

  Anything that failed between 2026-04-14 20:51 UTC and 2026-04-14 21:19 UTC may need a replay.

• Subscribe to Twilio's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=twilio works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Twilio 4

1. investigatingApr 14, 2026, 8: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

   provider

2. investigatingApr 14, 2026, 8: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

   provider

3. monitoringApr 14, 2026, 9: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.

   provider

4. resolvedApr 14, 2026, 9: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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.