1What changed since the last material update?
This is the first record of the incident.
- First recorded by Spike · incident revision 1
| Field | Before | Now | |
|---|---|---|---|
| status | — | identified | changed |
| provider impact | — | minor | changed |
| services | — | SMS, Latin America + SMS, Latin America | changed |
| regions | — | Latin America + Latin America | changed |
| mitigation or recovery | — | the provider has identified the issue and is working on a fix From the provider's status term, not from a separate statement. | changed |
| cause | — | — Not stated by the provider in a structured field. | same |
2Who says so, and when?
| Claim | Value | Evidence |
|---|---|---|
| Incident status | identified | Provider statement Twilio · published 2026-11-18 03:18 UTC · incident revision 1 · source ↗ |
| Provider impact level | minor | Provider statement Twilio · published 2026-11-18 03:18 UTC · incident revision 1 · source ↗ |
| Services named | SMS, Latin America | Provider statement Twilio · published 2026-11-18 03:18 UTC · incident revision 1 · source ↗ |
| Regions named | Latin America | Provider statement Twilio · published 2026-11-18 03:18 UTC · incident revision 1 · source ↗ |
| Latest provider update | Twilio customers may be experiencing SMS delivery receipt delays from a subset of Twilio Long Codes to network subscribers on multiple networks in Chile. Our team has identified the cause, and is working to resolve the issue. Message delivery may succeed, but delivery receipts… | Provider statement Twilio · published 2026-11-18 03:18 UTC · incident revision 1 · source ↗ |
| Severity used for sorting | 1 | Spike inference SpikeTrendWatch · incident revision 1 |
Independent reporting and observable signals: none attached to this incident. Only the provider's own statements are shown. Public attention (for example a search spike) shows interest only. It is not evidence of cause or impact.
Open questions
- Cause: not stated by the provider in a structured field.
- Customer impact: not established. The provider reports its own systems; impact on a specific business needs that business's own evidence.
| Began (provider) | 2026-11-06 21:21 UTC |
| Published by Twilio | 2026-11-18 03:18 UTC |
| Observed and published by Spike | 2026-11-18 03:40 UTC |
| Delivered | per workspace, in its private view |
3Which business service should I check?
That depends on what your business runs on. See the private view in a synthetic demo. In Spike Pro (free beta), list the providers and services you depend on; your private view of this brief then shows which business service each revision touches, whether it is a direct match or a possible exposure, and why. Customer impact always needs your own evidence.
4What did we know then?
Revision 1 uses only what Spike had recorded by 2026-11-18 03:40 UTC: incident revisions 1. Later updates are excluded, so this view reads the same every time it is opened (content fingerprint df92800bf2b6b6df).
Known later, at brief revision 2 (2026-11-18 22:37 UTC): Status changed: identified → monitoring. Open revision 2
5Who received the correction?
No correction has been published for this incident.
Delivery outcomes are private to each workspace and appear in its own view of this brief.
Handoff summary
Plain text to paste into a ticket or shift handoff.
Schema spike.evidence-brief/1. A brief is built from Spike's append-only incident revisions; it adds no facts of its own beyond the labeled Spike inferences. Incident record · API contract · Open another brief