Twilio incident

Reassigned Number Package Degradation for Lookup V2 API

Minor Resolved View vendor source →
Started
Apr 14, 2026, 08:51 PM UTC
Resolved
Apr 14, 2026, 09:19 PM UTC
Duration
28m
Detected by Pingoru
Apr 14, 2026, 08:51 PM UTC

Affected components

Lookup

Update timeline

  1. 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

  2. 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

  3. 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.

  4. 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.

Looking to track Twilio downtime and outages?

Pingoru polls Twilio's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Twilio reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Twilio alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Twilio for free

5 free monitors · No credit card required