Última hora

This revision as JSON · Prints cleanly from your browser's print command.

1What changed since the last material update?

Compared with brief revision 1 (incident revision 1):

  • Status changed: identified → monitoring · incident revision 2
FieldBeforeNow
statusidentifiedmonitoringchanged
provider impactminorminorsame
servicesSMS, Latin AmericaSMS, Latin Americasame
regionsLatin AmericaLatin Americasame
mitigation or recoverythe provider has identified the issue and is working on a fixthe provider reports a fix in place and is monitoring
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?

ClaimValueEvidence
Incident statusmonitoringProvider statement Twilio · published 2026-11-18 22:36 UTC · incident revision 2 · fonte ↗
Provider impact levelminorProvider statement Twilio · published 2026-11-18 03:18 UTC · incident revision 1 · fonte ↗
Services namedSMS, Latin AmericaProvider statement Twilio · published 2026-11-18 03:18 UTC · incident revision 1 · fonte ↗
Regions namedLatin AmericaProvider statement Twilio · published 2026-11-18 03:18 UTC · incident revision 1 · fonte ↗
Latest provider updateWe have observed a recovery in SMS delivery receipts from a subset of Twilio Long Codes to network subscribers on multiple networks in Chile and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.Provider statement Twilio · published 2026-11-18 22:36 UTC · incident revision 2 · fonte ↗
Severity used for sorting1Spike inference SpikeTrendWatch · incident revision 2

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.

Conflict (incident revision 1): Twilio has not updated this open incident for 13 hours. Its status may be out of date.

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 Twilio2026-11-18 22:36 UTC
Observed and published by Spike2026-11-18 22:37 UTC
Deliveredper 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 2 uses only what Spike had recorded by 2026-11-18 22:37 UTC: incident revisions 1, 2. Later updates are excluded, so this view reads the same every time it is opened (content fingerprint 2221f14b1da9d8aa).

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