Plivo incident

PHLO: Inbound call failures — sub-account numbers on main account PHLO apps

Notice Resolved View vendor source →
Started
Apr 08, 2026, 06:30 AM UTC
Resolved
Apr 08, 2026, 06:30 AM UTC
Duration
Detected by Pingoru
Apr 08, 2026, 06:30 AM UTC

Update timeline

  1. resolved Apr 08, 2026, 04:36 PM UTC

    Dear Valued Customer, We observed some inbound calls to PHLO applications were not being processed successfully. This affected a specific configuration where a phone number rented to a sub-account was attached to a PHLO application owned by the parent account. A recent deployment introduced a change in the request authentication flow that did not account for this configuration. The issue has been identified and fixed. Customers using phone numbers and PHLOs directly under their main account were not impacted. If you have any questions or need further assistance, please don't hesitate to contact Plivo Support through our Support Portal(https://support.plivo.com/hc/en-us).

Looking to track Plivo downtime and outages?

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

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

5 free monitors · No credit card required