Provider
PlivoIncident detail
PHLO: Inbound call failures — sub-account numbers on main account PHLO apps
Resolved incidentMinor
Timeline window
to
Get alerted the next time Plivo breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update Plivo posted, oldest to newest, exactly as it appeared on their official status page.
Resolved
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).
Keep exploring
More from Plivo
Neighboring incidents on Plivo's timeline and the rest of their record on OutageDeck.