CHYP.ai · ORBIT // Cloudy_Day Security Suite

OUTAGE DISSECTOR · CASE FILE · NetWeather event

Twilio: 2 components degraded performance

Twilio active M4.2 Squall since Aug 12, 3:55 PM PT

Twilio reported “Twilio: 2 components degraded performance” starting Aug 12, 3:55 PM PT.

  • 101d 5hDurationand counting
  • 2Peak componentsnow 2
  • —Places named0 on the map
  • 0Dependentscatalogued, inferred
  • 3/4Evidence kindsindependent families
  • 6Updatesofficial revisions

1Scrub the outage

full window
Severitypeak 2 components Aug 21, 2026Sep 8, 2026Sep 26, 2026Oct 14, 2026Nov 1, 2026Nov 18, 2026 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: 1 component degraded performanceNov 19, 6:51 AM PT · Vendor incident opened: United Kingdom Account Security Carrier Partner Maintenance - Vodafone (maintenance)Nov 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, 7:02 AM PT · Vendor incident opened: Russia SMS Carrier Maintenance - Sberbank Mobile (maintenance)Nov 20, 9:08 AM PT · Vendor incident opened: United Kingdom Account Security Carrier Partner Maintenance - Vodafone (maintenance)Nov 20, 9:10 AM PT · Vendor incident opened: Italy Account Security Carrier Partner Maintenance - Wind Tre (maintenance)Nov 20, 9:14 AM PT · Twilio: 2 components degraded performanceNov 20, 9:42 AM PT · Twilio: 1 component degraded performanceNov 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)Nov 20, 2:24 PM PT · Twilio: 2 components degraded performanceNov 20, 3:26 PM PT · Twilio: 1 component degraded performanceNov 21, 12:02 PM PT · Official status Degraded / minor incident → MaintenanceNov 21, 12:52 PM PT · Vendor incident opened: Russia SMS Carrier Maintenance - Tinkoff Mobile (maintenance)Nov 21, 7:01 PM PT · Official status Maintenance → Degraded / minor incidentNov 21, 7:50 PM PT · Vendor incident opened: Gateway API (Lookup API) Failure Increase in Canada (minor)Nov 21, 7:52 PM PT · Twilio: 2 components degraded performanceNetwork & routingNov 21, 7:50 PM PT · Twilio: Gateway API (Lookup API) Failure Increase in CanadaNov 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…Nov 9, 6:10 AM PT · Twilio: 2 components degraded performance · ASEarly signalsNov 21, 7:01 PM PT · SendGrid status page: Degraded / minor incident (Voice Call Failures from a Subset of Twi…Nov 21, 7:01 PM PT · Twilio status page: Degraded / minor incident (Voice Call Failures from a Subset of Twili…News & 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” starting Aug 12, 3:55 PM PT.

What broke

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

Who was hit

Hit: global/unspecified. No catalogued services depend on Twilio.

How it recovered

Still open after 101d 5h, at or near its peak (2 components).

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

Canada · investigating · Lookup SIM Swap — Twili… · same provider, other region: Twilio: Gateway API (Lookup API) Failure Increase in CanadaPhilippines · 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) · same provider, other region: Twilio: 2 components degraded performance · AS

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

4Failure-mode fingerprint

RetriesControl planeConfig pushCascadeCapacity
  • Control-plane coupling“api”
  • Dependency cascade“carrier”
  • 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 · Aug 12, 9:55 AM PT: 0 itemsOfficial status · Aug 16, 3:23 PM PT: 0 itemsOfficial status · Aug 20, 8:52 PM PT: 0 itemsOfficial status · Aug 25, 2:20 AM PT: 0 itemsOfficial status · Aug 29, 7:49 AM PT: 0 itemsOfficial status · Sep 2, 1:17 PM PT: 0 itemsOfficial status · Sep 6, 6:46 PM PT: 0 itemsOfficial status · Sep 11, 12:14 AM PT: 0 itemsOfficial status · Sep 15, 5:43 AM PT: 0 itemsOfficial status · Sep 19, 11:11 AM PT: 0 itemsOfficial status · Sep 23, 4:40 PM PT: 0 itemsOfficial status · Sep 27, 10:08 PM PT: 0 itemsOfficial status · Oct 2, 3:37 AM PT: 0 itemsOfficial status · Oct 6, 9:05 AM PT: 0 itemsOfficial status · Oct 10, 2:34 PM PT: 0 itemsOfficial status · Oct 14, 8:02 PM PT: 0 itemsOfficial status · Oct 19, 1:31 AM PT: 0 itemsOfficial status · Oct 23, 6:59 AM PT: 0 itemsOfficial status · Oct 27, 12:28 PM PT: 0 itemsOfficial status · Oct 31, 5:56 PM PT: 0 itemsOfficial status · Nov 4, 10:25 PM PT: 0 itemsOfficial status · Nov 9, 3:53 AM PT: 0 itemsOfficial status · Nov 13, 9:21 AM PT: 1 itemOfficial status · Nov 17, 2:50 PM PT: 19 itemsNetwork & routingNetwork & routing · Aug 12, 9:55 AM PT: 0 itemsNetwork & routing · Aug 16, 3:23 PM PT: 0 itemsNetwork & routing · Aug 20, 8:52 PM PT: 0 itemsNetwork & routing · Aug 25, 2:20 AM PT: 0 itemsNetwork & routing · Aug 29, 7:49 AM PT: 0 itemsNetwork & routing · Sep 2, 1:17 PM PT: 0 itemsNetwork & routing · Sep 6, 6:46 PM PT: 0 itemsNetwork & routing · Sep 11, 12:14 AM PT: 0 itemsNetwork & routing · Sep 15, 5:43 AM PT: 0 itemsNetwork & routing · Sep 19, 11:11 AM PT: 0 itemsNetwork & routing · Sep 23, 4:40 PM PT: 0 itemsNetwork & routing · Sep 27, 10:08 PM PT: 0 itemsNetwork & routing · Oct 2, 3:37 AM PT: 0 itemsNetwork & routing · Oct 6, 9:05 AM PT: 0 itemsNetwork & routing · Oct 10, 2:34 PM PT: 0 itemsNetwork & routing · Oct 14, 8:02 PM PT: 0 itemsNetwork & routing · Oct 19, 1:31 AM PT: 0 itemsNetwork & routing · Oct 23, 6:59 AM PT: 0 itemsNetwork & routing · Oct 27, 12:28 PM PT: 0 itemsNetwork & routing · Oct 31, 5:56 PM PT: 0 itemsNetwork & routing · Nov 4, 10:25 PM PT: 0 itemsNetwork & routing · Nov 9, 3:53 AM PT: 1 itemNetwork & routing · Nov 13, 9:21 AM PT: 0 itemsNetwork & routing · Nov 17, 2:50 PM PT: 3 itemsEarly signalsEarly signals · Aug 12, 9:55 AM PT: 0 itemsEarly signals · Aug 16, 3:23 PM PT: 0 itemsEarly signals · Aug 20, 8:52 PM PT: 0 itemsEarly signals · Aug 25, 2:20 AM PT: 0 itemsEarly signals · Aug 29, 7:49 AM PT: 0 itemsEarly signals · Sep 2, 1:17 PM PT: 0 itemsEarly signals · Sep 6, 6:46 PM PT: 0 itemsEarly signals · Sep 11, 12:14 AM PT: 0 itemsEarly signals · Sep 15, 5:43 AM PT: 0 itemsEarly signals · Sep 19, 11:11 AM PT: 0 itemsEarly signals · Sep 23, 4:40 PM PT: 0 itemsEarly signals · Sep 27, 10:08 PM PT: 0 itemsEarly signals · Oct 2, 3:37 AM PT: 0 itemsEarly signals · Oct 6, 9:05 AM PT: 0 itemsEarly signals · Oct 10, 2:34 PM PT: 0 itemsEarly signals · Oct 14, 8:02 PM PT: 0 itemsEarly signals · Oct 19, 1:31 AM PT: 0 itemsEarly signals · Oct 23, 6:59 AM PT: 0 itemsEarly signals · Oct 27, 12:28 PM PT: 0 itemsEarly signals · Oct 31, 5:56 PM PT: 0 itemsEarly signals · Nov 4, 10:25 PM PT: 0 itemsEarly signals · Nov 9, 3:53 AM PT: 0 itemsEarly signals · Nov 13, 9:21 AM PT: 0 itemsEarly signals · Nov 17, 2:50 PM PT: 2 itemsNews & chatterNews & chatter · Aug 12, 9:55 AM PT: 0 itemsNews & chatter · Aug 16, 3:23 PM PT: 0 itemsNews & chatter · Aug 20, 8:52 PM PT: 0 itemsNews & chatter · Aug 25, 2:20 AM PT: 0 itemsNews & chatter · Aug 29, 7:49 AM PT: 0 itemsNews & chatter · Sep 2, 1:17 PM PT: 0 itemsNews & chatter · Sep 6, 6:46 PM PT: 0 itemsNews & chatter · Sep 11, 12:14 AM PT: 0 itemsNews & chatter · Sep 15, 5:43 AM PT: 0 itemsNews & chatter · Sep 19, 11:11 AM PT: 0 itemsNews & chatter · Sep 23, 4:40 PM PT: 0 itemsNews & chatter · Sep 27, 10:08 PM PT: 0 itemsNews & chatter · Oct 2, 3:37 AM PT: 0 itemsNews & chatter · Oct 6, 9:05 AM PT: 0 itemsNews & chatter · Oct 10, 2:34 PM PT: 0 itemsNews & chatter · Oct 14, 8:02 PM PT: 0 itemsNews & chatter · Oct 19, 1:31 AM PT: 0 itemsNews & chatter · Oct 23, 6:59 AM PT: 0 itemsNews & chatter · Oct 27, 12:28 PM PT: 0 itemsNews & chatter · Oct 31, 5:56 PM PT: 0 itemsNews & chatter · Nov 4, 10:25 PM PT: 0 itemsNews & chatter · Nov 9, 3:53 AM PT: 0 itemsNews & chatter · Nov 13, 9:21 AM PT: 0 itemsNews & chatter · Nov 17, 2:50 PM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Aug 12, 9:55 AM PT: 0 itemsCoincidence (KEV) · Aug 16, 3:23 PM PT: 0 itemsCoincidence (KEV) · Aug 20, 8:52 PM PT: 0 itemsCoincidence (KEV) · Aug 25, 2:20 AM PT: 0 itemsCoincidence (KEV) · Aug 29, 7:49 AM PT: 0 itemsCoincidence (KEV) · Sep 2, 1:17 PM PT: 0 itemsCoincidence (KEV) · Sep 6, 6:46 PM PT: 0 itemsCoincidence (KEV) · Sep 11, 12:14 AM PT: 0 itemsCoincidence (KEV) · Sep 15, 5:43 AM PT: 0 itemsCoincidence (KEV) · Sep 19, 11:11 AM PT: 0 itemsCoincidence (KEV) · Sep 23, 4:40 PM PT: 0 itemsCoincidence (KEV) · Sep 27, 10:08 PM PT: 0 itemsCoincidence (KEV) · Oct 2, 3:37 AM PT: 0 itemsCoincidence (KEV) · Oct 6, 9:05 AM PT: 0 itemsCoincidence (KEV) · Oct 10, 2:34 PM PT: 0 itemsCoincidence (KEV) · Oct 14, 8:02 PM PT: 0 itemsCoincidence (KEV) · Oct 19, 1:31 AM PT: 0 itemsCoincidence (KEV) · Oct 23, 6:59 AM PT: 0 itemsCoincidence (KEV) · Oct 27, 12:28 PM PT: 0 itemsCoincidence (KEV) · Oct 31, 5:56 PM PT: 0 itemsCoincidence (KEV) · Nov 4, 10:25 PM PT: 0 itemsCoincidence (KEV) · Nov 9, 3:53 AM PT: 0 itemsCoincidence (KEV) · Nov 13, 9:21 AM PT: 0 itemsCoincidence (KEV) · Nov 17, 2:50 PM PT: 0 itemsAug 12, 9:55 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 beganAug 12, 3:55 PM PTORBIT first saw itNov 19, 3:38 AM PTLatest source updateNov 21, 7:50 PM PTLast checkedNov 21, 8:18 PM 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 101d 5h. 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.
  • 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 →NetWeather evidence page →Status page →

Embed this card
<a href="https://www.chyp.ai/dissect/event-nw-4483df286d06d058/"><img src="https://www.chyp.ai/dissect/event-nw-4483df286d06d058/card.svg" alt="Twilio: 2 components degraded performance · 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.
  • Region: global / unspecified. The source did not assert a region; none was inferred from publisher location.
  • 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.