View Evidence Brief What changed, who says so and when, and what was known at each revision.
Four clocks
| Began (provider) | Tue, 17 Nov 2026 16:06:00 GMT |
| Latest update published (provider) | Wed, 18 Nov 2026 03:18:54 GMT |
| Seen by Spike | Wed, 18 Nov 2026 03:35: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, Latin America | Direct: Twilio status page · source ↗ |
| affected regions | Brazil, Latin America | 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 1 · First recorded by Spike
Published by Twilio 2026-11-18 03:18 UTC · seen by Spike 17 min later (first read of this status page)Twilio said: “Twilio customers may be experiencing voice call audio quality degradation, post dial delay, and silent and one-way audio between Twilio and network subscribers on multiple networks in Brazil. Our team has identified the cause, and is working to resolve the issue. We will…”