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

What to do

• Check whether you use Plivo in us. 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 0m it lasted.

  Anything that failed between 2026-04-08 06:30 UTC and 2026-04-08 06:30 UTC may need a replay.

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

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

Updates from Plivo 1

1. resolvedApr 8, 2026, 6:30 AM 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).

   provider

Corrections

None so far.

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