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 23:52:38 GMT |
| Latest update published (provider) | Wed, 18 Nov 2026 00:44:18 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 | resolved | Direct: Twilio status page · source ↗ |
| affected services | MMS, SMS, RCS Messaging, Programmable Messaging API | 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 00:44 UTC · seen by Spike 171 min later (first read of this status page)Twilio said: “We have monitored and resolved the issue with the Programmable Messaging API. All services are now operating normally at this time.”