CHYP.ai · ORBIT // Cloudy_Day Security Suite

OUTAGE DISSECTOR · CASE FILE · Vendor incident

SMS Delivery Receipt Delays from Twilio to Telekom Srbija Serbia

Twilio identified M3.2 Squall since Nov 22, 2:10 PM PT

Twilio reported “SMS Delivery Receipt Delays from Twilio to Telekom Srbija Serbia” starting Nov 22, 2:10 PM PT.

  • 40mDurationand counting
  • 6Systems namedfrom the source
  • 1Places named1 on the map
  • 0Dependentscatalogued, inferred
  • 3/4Evidence kindsindependent families
  • 11Updatesofficial revisions

1Scrub the outage

full window
Severityofficial state Nov 22, 11 AMNov 22, 11 AMNov 22, 12 PMNov 22, 1 PMNov 22, 2 PMNov 22, 2 PM Official statusNov 22, 2:10 PM PT · Incident opened: SMS Delivery Receipt Delays from Twilio to Telekom Srbija SerbiaNetwork & routingNov 22, 2:48 PM PT · Twilio: SMS Delivery Delays from Twilio to Telekom Srbija SerbiaNov 22, 11:11 AM PT · Twilio: Gateway API (Lookup API) Failure Increase in CanadaNov 22, 2:48 PM PT · Twilio: 1 component degraded performance · EUEarly signalsnothing in this windowNews & chatternothing in this windowCoincidence (KEV)nothing in this window ▼ startnow ▼

Drag or press Play to replay what was public at each moment. Each dot links to its evidence. Lanes are kept separate on purpose.

What happened

Twilio reported “SMS Delivery Receipt Delays from Twilio to Telekom Srbija Serbia” starting Nov 22, 2:10 PM PT.

What broke

Voice, APAC, MMS, APAC, SMS, Europe, Lookup Line Type Intelligence [Legacy API] and 2 more.

Who was hit

Hit: 1 named location (Serbia). No catalogued services depend on Twilio.

How it recovered

Still open after 40m.

2Blast radius

Amazon Web Services · OperationalAmazon Web Serv…Twilio0 dependents

Center: Twilio. Inner ring: what it runs on. Outer ring: catalogued services that run on it, coloured by their official status right now. Dependencies are inferred from public information.

3Blast map

Serbia · SMS Delivery Receipt Delays from Twilio…
  1. Serbia

Places come from names in the public text (cities, PoP codes, countries, regions). Approximate.

4Failure-mode fingerprint

RetriesControl planeConfig pushCascadeCapacity
  • Control-plane coupling“api”
  • Retry amplificationno sign
  • Config propagationno sign
  • Dependency cascadeno sign
  • Capacity exhaustionno sign

Automated keyword read of the public updates. A hypothesis to test, never a root cause.

5Evidence matrix

Official statusOfficial status · Nov 22, 8:10 AM PT: 0 itemsOfficial status · Nov 22, 8:27 AM PT: 0 itemsOfficial status · Nov 22, 8:43 AM PT: 0 itemsOfficial status · Nov 22, 9:00 AM PT: 0 itemsOfficial status · Nov 22, 9:17 AM PT: 0 itemsOfficial status · Nov 22, 9:33 AM PT: 0 itemsOfficial status · Nov 22, 9:50 AM PT: 0 itemsOfficial status · Nov 22, 10:07 AM PT: 0 itemsOfficial status · Nov 22, 10:23 AM PT: 0 itemsOfficial status · Nov 22, 10:40 AM PT: 0 itemsOfficial status · Nov 22, 10:57 AM PT: 0 itemsOfficial status · Nov 22, 11:13 AM PT: 0 itemsOfficial status · Nov 22, 11:30 AM PT: 0 itemsOfficial status · Nov 22, 11:47 AM PT: 0 itemsOfficial status · Nov 22, 12:03 PM PT: 0 itemsOfficial status · Nov 22, 12:20 PM PT: 0 itemsOfficial status · Nov 22, 12:37 PM PT: 0 itemsOfficial status · Nov 22, 12:53 PM PT: 0 itemsOfficial status · Nov 22, 1:10 PM PT: 0 itemsOfficial status · Nov 22, 1:27 PM PT: 0 itemsOfficial status · Nov 22, 1:43 PM PT: 0 itemsOfficial status · Nov 22, 2:00 PM PT: 1 itemOfficial status · Nov 22, 2:17 PM PT: 0 itemsOfficial status · Nov 22, 2:33 PM PT: 0 itemsNetwork & routingNetwork & routing · Nov 22, 8:10 AM PT: 0 itemsNetwork & routing · Nov 22, 8:27 AM PT: 0 itemsNetwork & routing · Nov 22, 8:43 AM PT: 0 itemsNetwork & routing · Nov 22, 9:00 AM PT: 0 itemsNetwork & routing · Nov 22, 9:17 AM PT: 0 itemsNetwork & routing · Nov 22, 9:33 AM PT: 0 itemsNetwork & routing · Nov 22, 9:50 AM PT: 0 itemsNetwork & routing · Nov 22, 10:07 AM PT: 0 itemsNetwork & routing · Nov 22, 10:23 AM PT: 0 itemsNetwork & routing · Nov 22, 10:40 AM PT: 0 itemsNetwork & routing · Nov 22, 10:57 AM PT: 1 itemNetwork & routing · Nov 22, 11:13 AM PT: 0 itemsNetwork & routing · Nov 22, 11:30 AM PT: 0 itemsNetwork & routing · Nov 22, 11:47 AM PT: 0 itemsNetwork & routing · Nov 22, 12:03 PM PT: 0 itemsNetwork & routing · Nov 22, 12:20 PM PT: 0 itemsNetwork & routing · Nov 22, 12:37 PM PT: 0 itemsNetwork & routing · Nov 22, 12:53 PM PT: 0 itemsNetwork & routing · Nov 22, 1:10 PM PT: 0 itemsNetwork & routing · Nov 22, 1:27 PM PT: 0 itemsNetwork & routing · Nov 22, 1:43 PM PT: 0 itemsNetwork & routing · Nov 22, 2:00 PM PT: 0 itemsNetwork & routing · Nov 22, 2:17 PM PT: 0 itemsNetwork & routing · Nov 22, 2:33 PM PT: 2 itemsEarly signalsEarly signals · Nov 22, 8:10 AM PT: 0 itemsEarly signals · Nov 22, 8:27 AM PT: 0 itemsEarly signals · Nov 22, 8:43 AM PT: 0 itemsEarly signals · Nov 22, 9:00 AM PT: 0 itemsEarly signals · Nov 22, 9:17 AM PT: 0 itemsEarly signals · Nov 22, 9:33 AM PT: 0 itemsEarly signals · Nov 22, 9:50 AM PT: 0 itemsEarly signals · Nov 22, 10:07 AM PT: 0 itemsEarly signals · Nov 22, 10:23 AM PT: 0 itemsEarly signals · Nov 22, 10:40 AM PT: 0 itemsEarly signals · Nov 22, 10:57 AM PT: 0 itemsEarly signals · Nov 22, 11:13 AM PT: 0 itemsEarly signals · Nov 22, 11:30 AM PT: 0 itemsEarly signals · Nov 22, 11:47 AM PT: 0 itemsEarly signals · Nov 22, 12:03 PM PT: 0 itemsEarly signals · Nov 22, 12:20 PM PT: 0 itemsEarly signals · Nov 22, 12:37 PM PT: 0 itemsEarly signals · Nov 22, 12:53 PM PT: 0 itemsEarly signals · Nov 22, 1:10 PM PT: 0 itemsEarly signals · Nov 22, 1:27 PM PT: 0 itemsEarly signals · Nov 22, 1:43 PM PT: 0 itemsEarly signals · Nov 22, 2:00 PM PT: 0 itemsEarly signals · Nov 22, 2:17 PM PT: 0 itemsEarly signals · Nov 22, 2:33 PM PT: 0 itemsNews & chatterNews & chatter · Nov 22, 8:10 AM PT: 0 itemsNews & chatter · Nov 22, 8:27 AM PT: 0 itemsNews & chatter · Nov 22, 8:43 AM PT: 0 itemsNews & chatter · Nov 22, 9:00 AM PT: 0 itemsNews & chatter · Nov 22, 9:17 AM PT: 0 itemsNews & chatter · Nov 22, 9:33 AM PT: 0 itemsNews & chatter · Nov 22, 9:50 AM PT: 0 itemsNews & chatter · Nov 22, 10:07 AM PT: 0 itemsNews & chatter · Nov 22, 10:23 AM PT: 0 itemsNews & chatter · Nov 22, 10:40 AM PT: 0 itemsNews & chatter · Nov 22, 10:57 AM PT: 0 itemsNews & chatter · Nov 22, 11:13 AM PT: 0 itemsNews & chatter · Nov 22, 11:30 AM PT: 0 itemsNews & chatter · Nov 22, 11:47 AM PT: 0 itemsNews & chatter · Nov 22, 12:03 PM PT: 0 itemsNews & chatter · Nov 22, 12:20 PM PT: 0 itemsNews & chatter · Nov 22, 12:37 PM PT: 0 itemsNews & chatter · Nov 22, 12:53 PM PT: 0 itemsNews & chatter · Nov 22, 1:10 PM PT: 0 itemsNews & chatter · Nov 22, 1:27 PM PT: 0 itemsNews & chatter · Nov 22, 1:43 PM PT: 0 itemsNews & chatter · Nov 22, 2:00 PM PT: 0 itemsNews & chatter · Nov 22, 2:17 PM PT: 0 itemsNews & chatter · Nov 22, 2:33 PM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Nov 22, 8:10 AM PT: 0 itemsCoincidence (KEV) · Nov 22, 8:27 AM PT: 0 itemsCoincidence (KEV) · Nov 22, 8:43 AM PT: 0 itemsCoincidence (KEV) · Nov 22, 9:00 AM PT: 0 itemsCoincidence (KEV) · Nov 22, 9:17 AM PT: 0 itemsCoincidence (KEV) · Nov 22, 9:33 AM PT: 0 itemsCoincidence (KEV) · Nov 22, 9:50 AM PT: 0 itemsCoincidence (KEV) · Nov 22, 10:07 AM PT: 0 itemsCoincidence (KEV) · Nov 22, 10:23 AM PT: 0 itemsCoincidence (KEV) · Nov 22, 10:40 AM PT: 0 itemsCoincidence (KEV) · Nov 22, 10:57 AM PT: 0 itemsCoincidence (KEV) · Nov 22, 11:13 AM PT: 0 itemsCoincidence (KEV) · Nov 22, 11:30 AM PT: 0 itemsCoincidence (KEV) · Nov 22, 11:47 AM PT: 0 itemsCoincidence (KEV) · Nov 22, 12:03 PM PT: 0 itemsCoincidence (KEV) · Nov 22, 12:20 PM PT: 0 itemsCoincidence (KEV) · Nov 22, 12:37 PM PT: 0 itemsCoincidence (KEV) · Nov 22, 12:53 PM PT: 0 itemsCoincidence (KEV) · Nov 22, 1:10 PM PT: 0 itemsCoincidence (KEV) · Nov 22, 1:27 PM PT: 0 itemsCoincidence (KEV) · Nov 22, 1:43 PM PT: 0 itemsCoincidence (KEV) · Nov 22, 2:00 PM PT: 0 itemsCoincidence (KEV) · Nov 22, 2:17 PM PT: 0 itemsCoincidence (KEV) · Nov 22, 2:33 PM PT: 0 itemsNov 22, 8:10 AM PTnow

Correlation is not causation

Five independent lanes across the window. Brighter = stronger item. Items landing in the same column are coincidence unless the provider says otherwise.

6Four clocks

Source says it beganNov 22, 2:10 PM PTORBIT first saw itNov 22, 2:50 PM PTLast checkedNov 22, 2:49 PM PT

Detection gap not measurable from public clocks.

Public status always trails reality. These are the times each public record states, in PT.

7Historical twins

Nearest matches in the Control-Plane Meltdown Index (1.0.0, vendor-sourced, tracked since 2024 with earlier landmark cases). Similarity = provider + failure modes + scope.

Cloudy_Day take

  • 3 independent kinds of public evidence line up in the same window. Corroboration, still not causation.

Automated take: rules written by Cloudy_Day, applied to public data. Not a human verdict on this incident, not a root-cause finding, not affiliated with Twilio.

8Dissection capsule

Share card for this dissection

Everything above as one shareable, citable capsule with a content hash.

JSON capsuleMarkdownShare card (SVG)

Open Twilio in the War Room →Status page →

Embed this card
<a href="https://www.chyp.ai/dissect/vi/twilio~wp5h8ggpfh2k/"><img src="https://www.chyp.ai/dissect/vi/twilio~wp5h8ggpfh2k/card.svg" alt="SMS Delivery Receipt Delays from Twilio to Telekom Srbija S… · ORBIT Outage Dissector" width="600"></a>

Sources & limits

  • Provider-stated: this repeats what the vendor's public status page said. It is not an independent root-cause verification.
  • Temporal overlap with other events is coincidence, not causation, unless a provider states a causal link.
  • Correlation is not causation. Lanes are kept apart so overlap never reads as cause.
  • ORBIT is passive: it never contacts the provider or probes its systems. Independent researcher, not affiliated.