CHYP.ai · ORBIT // Cloudy_Day Security Suite

OUTAGE DISSECTOR · CASE FILE · NetWeather event

Twilio: 2 components degraded performance · AS

Twilio active M4.1 Squall since Nov 9, 6:10 AM PT

Twilio reported “Twilio: 2 components degraded performance · AS” starting Nov 9, 6:10 AM PT.

  • 11d 22hDurationand counting
  • 2Peak componentsnow 2
  • 3Places named1 on the map
  • 0Dependentscatalogued, inferred
  • 2/4Evidence kindsindependent families
  • 1Updatesofficial revisions

1Scrub the outage

full window
Severitypeak 2 components Nov 9, 8 PMNov 12, 1 AMNov 14, 5 AMNov 16, 10 AMNov 18, 3 PMNov 20, 7 PM Official statusNov 16, 4:41 PM PT · Vendor incident opened: United States MMS Carrier Maintenance - Verizon (maintenance)Nov 18, 7:56 AM PT · Vendor incident opened: Voice Call Silent and One-Way Audio from Colombia to a Subset of Twilio Phone N… (minor)Nov 19, 3:38 AM PT · Twilio: 2 components degraded performance · ASNov 19, 1:36 PM PT · Vendor incident opened: Russia SMS Carrier Maintenance - Tele2 (maintenance)Nov 20, 4:51 AM PT · Vendor incident opened: SMS Delivery Delays from Twilio to Proximus Belgium (minor)Nov 20, 9:08 AM PT · Vendor incident opened: United Kingdom Account Security Carrier Partner Maintenance - Vodafone (maintenance)Nov 20, 11:53 AM PT · Vendor incident opened: SMS Delivery Receipt Delays from a Subset of Twilio Phone Numbers to CTBC Brazil (minor)Nov 20, 2:23 PM PT · Vendor incident opened: Twilio Help Center Chat Issues (minor)Network & routingNov 18, 6:25 AM PT · Twilio: Voice Call Failures from a Subset of Twilio Philippines Phone Numbers to Multiple…Nov 20, 10:00 PM PT · Twilio: Voice Call Silent and One-Way Audio from Colombia to a Subset of Twilio Phone Num…Early 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 “Twilio: 2 components degraded performance · AS” starting Nov 9, 6:10 AM PT.

What broke

Voice, APAC, MMS, APAC, Lookup Line Type Intelligence [Legacy API], Voice, Latin America and 1 more.

Who was hit

Hit: 3 named locations (Asia). No catalogued services depend on Twilio.

How it recovered

Still open after 11d 22h.

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

Philippines · identified · Voice, APAC — Twilio custo… · same provider, other region: Twilio: Voice Call Failures from a Subset of Twilio Philippines Phone Numbers to Multiple Networks in PhilippinesColombia · monitoring · Voice, Latin America — We … · same provider, other region: Twilio: Voice Call Silent and One-Way Audio from Colombia to a Subset of Twilio Phone NumbersAsia ×3 · Voice, APAC (CARRIER NETWORK); MMS, APAC (CARRIER NETWORK)
  1. Asia ×3

Bright: this event. Dim: the same provider's other open events (3). Places come from names in the public text (cities, PoP codes, countries, regions). Approximate.

4Failure-mode fingerprint

RetriesControl planeConfig pushCascadeCapacity
  • Dependency cascade“carrier”, “subset of”
  • Control-plane coupling“api”
  • Capacity exhaustion“degraded performance”
  • Retry amplificationno sign
  • Config propagationno sign

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

5Evidence matrix

Official statusOfficial status · Nov 9, 12:10 AM PT: 0 itemsOfficial status · Nov 9, 12:21 PM PT: 0 itemsOfficial status · Nov 10, 12:33 AM PT: 0 itemsOfficial status · Nov 10, 12:44 PM PT: 0 itemsOfficial status · Nov 11, 12:56 AM PT: 0 itemsOfficial status · Nov 11, 1:07 PM PT: 0 itemsOfficial status · Nov 12, 1:19 AM PT: 0 itemsOfficial status · Nov 12, 1:30 PM PT: 0 itemsOfficial status · Nov 13, 1:41 AM PT: 0 itemsOfficial status · Nov 13, 1:53 PM PT: 0 itemsOfficial status · Nov 14, 2:04 AM PT: 0 itemsOfficial status · Nov 14, 2:16 PM PT: 0 itemsOfficial status · Nov 15, 2:27 AM PT: 0 itemsOfficial status · Nov 15, 2:39 PM PT: 0 itemsOfficial status · Nov 16, 2:50 AM PT: 0 itemsOfficial status · Nov 16, 3:02 PM PT: 1 itemOfficial status · Nov 17, 3:13 AM PT: 0 itemsOfficial status · Nov 17, 3:25 PM PT: 0 itemsOfficial status · Nov 18, 3:36 AM PT: 1 itemOfficial status · Nov 18, 3:48 PM PT: 1 itemOfficial status · Nov 19, 3:59 AM PT: 1 itemOfficial status · Nov 19, 4:11 PM PT: 0 itemsOfficial status · Nov 20, 4:22 AM PT: 4 itemsOfficial status · Nov 20, 4:33 PM PT: 0 itemsNetwork & routingNetwork & routing · Nov 9, 12:10 AM PT: 0 itemsNetwork & routing · Nov 9, 12:21 PM PT: 0 itemsNetwork & routing · Nov 10, 12:33 AM PT: 0 itemsNetwork & routing · Nov 10, 12:44 PM PT: 0 itemsNetwork & routing · Nov 11, 12:56 AM PT: 0 itemsNetwork & routing · Nov 11, 1:07 PM PT: 0 itemsNetwork & routing · Nov 12, 1:19 AM PT: 0 itemsNetwork & routing · Nov 12, 1:30 PM PT: 0 itemsNetwork & routing · Nov 13, 1:41 AM PT: 0 itemsNetwork & routing · Nov 13, 1:53 PM PT: 0 itemsNetwork & routing · Nov 14, 2:04 AM PT: 0 itemsNetwork & routing · Nov 14, 2:16 PM PT: 0 itemsNetwork & routing · Nov 15, 2:27 AM PT: 0 itemsNetwork & routing · Nov 15, 2:39 PM PT: 0 itemsNetwork & routing · Nov 16, 2:50 AM PT: 0 itemsNetwork & routing · Nov 16, 3:02 PM PT: 0 itemsNetwork & routing · Nov 17, 3:13 AM PT: 0 itemsNetwork & routing · Nov 17, 3:25 PM PT: 0 itemsNetwork & routing · Nov 18, 3:36 AM PT: 1 itemNetwork & routing · Nov 18, 3:48 PM PT: 0 itemsNetwork & routing · Nov 19, 3:59 AM PT: 0 itemsNetwork & routing · Nov 19, 4:11 PM PT: 0 itemsNetwork & routing · Nov 20, 4:22 AM PT: 0 itemsNetwork & routing · Nov 20, 4:33 PM PT: 1 itemEarly signalsEarly signals · Nov 9, 12:10 AM PT: 0 itemsEarly signals · Nov 9, 12:21 PM PT: 0 itemsEarly signals · Nov 10, 12:33 AM PT: 0 itemsEarly signals · Nov 10, 12:44 PM PT: 0 itemsEarly signals · Nov 11, 12:56 AM PT: 0 itemsEarly signals · Nov 11, 1:07 PM PT: 0 itemsEarly signals · Nov 12, 1:19 AM PT: 0 itemsEarly signals · Nov 12, 1:30 PM PT: 0 itemsEarly signals · Nov 13, 1:41 AM PT: 0 itemsEarly signals · Nov 13, 1:53 PM PT: 0 itemsEarly signals · Nov 14, 2:04 AM PT: 0 itemsEarly signals · Nov 14, 2:16 PM PT: 0 itemsEarly signals · Nov 15, 2:27 AM PT: 0 itemsEarly signals · Nov 15, 2:39 PM PT: 0 itemsEarly signals · Nov 16, 2:50 AM PT: 0 itemsEarly signals · Nov 16, 3:02 PM PT: 0 itemsEarly signals · Nov 17, 3:13 AM PT: 0 itemsEarly signals · Nov 17, 3:25 PM PT: 0 itemsEarly signals · Nov 18, 3:36 AM PT: 0 itemsEarly signals · Nov 18, 3:48 PM PT: 0 itemsEarly signals · Nov 19, 3:59 AM PT: 0 itemsEarly signals · Nov 19, 4:11 PM PT: 0 itemsEarly signals · Nov 20, 4:22 AM PT: 0 itemsEarly signals · Nov 20, 4:33 PM PT: 0 itemsNews & chatterNews & chatter · Nov 9, 12:10 AM PT: 0 itemsNews & chatter · Nov 9, 12:21 PM PT: 0 itemsNews & chatter · Nov 10, 12:33 AM PT: 0 itemsNews & chatter · Nov 10, 12:44 PM PT: 0 itemsNews & chatter · Nov 11, 12:56 AM PT: 0 itemsNews & chatter · Nov 11, 1:07 PM PT: 0 itemsNews & chatter · Nov 12, 1:19 AM PT: 0 itemsNews & chatter · Nov 12, 1:30 PM PT: 0 itemsNews & chatter · Nov 13, 1:41 AM PT: 0 itemsNews & chatter · Nov 13, 1:53 PM PT: 0 itemsNews & chatter · Nov 14, 2:04 AM PT: 0 itemsNews & chatter · Nov 14, 2:16 PM PT: 0 itemsNews & chatter · Nov 15, 2:27 AM PT: 0 itemsNews & chatter · Nov 15, 2:39 PM PT: 0 itemsNews & chatter · Nov 16, 2:50 AM PT: 0 itemsNews & chatter · Nov 16, 3:02 PM PT: 0 itemsNews & chatter · Nov 17, 3:13 AM PT: 0 itemsNews & chatter · Nov 17, 3:25 PM PT: 0 itemsNews & chatter · Nov 18, 3:36 AM PT: 0 itemsNews & chatter · Nov 18, 3:48 PM PT: 0 itemsNews & chatter · Nov 19, 3:59 AM PT: 0 itemsNews & chatter · Nov 19, 4:11 PM PT: 0 itemsNews & chatter · Nov 20, 4:22 AM PT: 0 itemsNews & chatter · Nov 20, 4:33 PM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Nov 9, 12:10 AM PT: 0 itemsCoincidence (KEV) · Nov 9, 12:21 PM PT: 0 itemsCoincidence (KEV) · Nov 10, 12:33 AM PT: 0 itemsCoincidence (KEV) · Nov 10, 12:44 PM PT: 0 itemsCoincidence (KEV) · Nov 11, 12:56 AM PT: 0 itemsCoincidence (KEV) · Nov 11, 1:07 PM PT: 0 itemsCoincidence (KEV) · Nov 12, 1:19 AM PT: 0 itemsCoincidence (KEV) · Nov 12, 1:30 PM PT: 0 itemsCoincidence (KEV) · Nov 13, 1:41 AM PT: 0 itemsCoincidence (KEV) · Nov 13, 1:53 PM PT: 0 itemsCoincidence (KEV) · Nov 14, 2:04 AM PT: 0 itemsCoincidence (KEV) · Nov 14, 2:16 PM PT: 0 itemsCoincidence (KEV) · Nov 15, 2:27 AM PT: 0 itemsCoincidence (KEV) · Nov 15, 2:39 PM PT: 0 itemsCoincidence (KEV) · Nov 16, 2:50 AM PT: 0 itemsCoincidence (KEV) · Nov 16, 3:02 PM PT: 0 itemsCoincidence (KEV) · Nov 17, 3:13 AM PT: 0 itemsCoincidence (KEV) · Nov 17, 3:25 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 3:36 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 3:48 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 3:59 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 4:11 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 4:22 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 4:33 PM PT: 0 itemsNov 9, 12: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 9, 6:10 AM PTORBIT first saw itNov 19, 3:38 AM PTLatest source updateNov 9, 6:10 AM PTLast checkedNov 21, 4:44 AM PT

This event was already open when the NetWeather ledger started (Nov 19, 2026), so the detection gap isn't measurable.

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

  • Open 11d 22h. At that age this is a standing condition, not an incident. It deserves its own runbook and its own SLO conversation.
  • By the clock it has outlasted 19 of 19 indexed meltdowns (median 3h 48m). By impact it isn't close. That's why ORBIT ranks by magnitude, not minutes.

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 →NetWeather evidence page →Status page →

Embed this card
<a href="https://www.chyp.ai/dissect/event-nw-4c1590104285e85e/"><img src="https://www.chyp.ai/dissect/event-nw-4c1590104285e85e/card.svg" alt="Twilio: 2 components degraded performance · AS · 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.
  • NetWeather is independent research, not an official status source. Confirm with the provider.
  • 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.