View Evidence Brief What changed, who says so and when, and what was known at each revision.
Four clocks
| Began (provider) | Mon, 02 Nov 2026 05:41:31 GMT |
| Latest update published (provider) | Wed, 18 Nov 2026 14:25:45 GMT |
| Seen by Spike | Wed, 18 Nov 2026 14:26:25 GMT |
| Delivered | Per customer, in each Spike Pro workspace's delivery receipts. |
What the provider states
| Claim | Value | Evidence |
|---|---|---|
| service status | identified | Direct: Twilio status page · source ↗ |
| affected services | Voice, APAC | Direct: Twilio status page · source ↗ |
| affected regions | APAC | Direct: Twilio status page · source ↗ |
| Cause | Twilio has not stated a cause in a structured field. Read the provider's updates. | |
| Customer impact | Depends on what you run. Spike Pro matches this incident to the services a workspace lists. | |
Revisions, newest first
- Revision 2 · New provider update
Published by Twilio 2026-11-18 14:25 UTC · seen by Spike 1 min laterTwilio said: “Twilio customers may be experiencing voice call failures from a subset of Twilio Philippines Phone Numbers to network subscribers on multiple networks in the Philippines. Our team has identified the cause, and is working to resolve the issue. We will provide another update in…”
- Revision 1 · First recorded by Spike
Published by Twilio 2026-11-17 14:25 UTC · seen by Spike 795 min laterTwilio said: “Twilio customers may be experiencing voice call failures from a subset of Twilio Philippines Phone Numbers to network subscribers on multiple networks in the Philippines. Our team has identified the cause, and is working to resolve the issue. We will provide another update in…”