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

- Provider: [Plivo](https://down.guide/plivo)
- Level: confirmed
- Impact: Operational
- lasted 0m
- started 2026-04-08 06:30 UTC
- us
- id: DWN-9c2a414d9d
- Official page: https://stspg.io/qs6x0d85l836

## Updates from Plivo
### 2026-04-08 06:30 UTC: 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).

From the builder: does your app depend on Plivo? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=plivo) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Plivo.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-9c2a414d9d), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.