Live / Twilio / Incident
Twilio: Voice Call Failures from a Subset of Twilio Philippines Phone Numbers to Multiple Networks in Philippines
Twilio · twilio.comMinor incidentidentified2026-11-15 14:24 UTC
Public — what happened
Summary
Twilio said some customers may be having voice calls fail when placed from a subset of its Philippines phone numbers to people on several networks in the Philippines. The problem was first reported on 2026-11-02 at 05:41 UTC, and within a minute Twilio said it had identified the cause and was working on a fix. On 2026-11-04 it reported a recovery and said it was monitoring, but on 2026-11-05 it again reported call failures, and its updates through 2026-11-12 still described the issue as unresolved.
Affected
Voice, APAC
Timeline
- Started — 2026-11-02 05:41 UTC
- Investigating — 2026-11-02 05:41 UTC
- Identified — 2026-11-02 05:42 UTC (6 updates)
- Monitoring — 2026-11-04 06:08 UTC (4 updates)
- Identified — 2026-11-05 06:57 UTC (15 updates)
- Ongoing at last check.
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Twilio against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Twilio: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Twilio report →
More from Twilio
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.