CHYP.ai · ORBIT // Cloudy_Day Security Suite

OUTAGE DISSECTOR · CASE FILE · NetWeather event

DigitalOcean: Increased Error Rates in SFO3

DigitalOcean resolved M3.4 Squall since Nov 18, 9:46 PM PT

DigitalOcean reported “DigitalOcean: Increased Error Rates in SFO3” starting Nov 18, 9:46 PM PT.

  • 12h 20mDurationstart → resolved
  • —Systems namedfrom the source
  • —Places named0 on the map
  • 0Dependentscatalogued, inferred
  • 1/4Evidence kindsindependent families
  • 2Updatesofficial revisions

1Scrub the outage

full window
Severityofficial state Nov 18, 10 PMNov 19, 12 AMNov 19, 2 AMNov 19, 5 AMNov 19, 7 AMNov 19, 9 AM Official statusNov 19, 3:38 AM PT · DigitalOcean: Increased Error Rates in SFO3Nov 19, 10:06 AM PT · DigitalOcean: Increased Error Rates in SFO3Network & routingnothing in this windowEarly signalsnothing in this windowNews & chatternothing in this windowCoincidence (KEV)nothing in this window ▼ startresolved ▼

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

DigitalOcean reported “DigitalOcean: Increased Error Rates in SFO3” starting Nov 18, 9:46 PM PT.

What broke

The official source does not list components.

Who was hit

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

How it recovered

Resolved after 12h 20m.

2Blast radius

DigitalOcean0 dependents

Center: DigitalOcean. 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

No place names in the public text. Region tag: global/unspecified.

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

4Failure-mode fingerprint

RetriesControl planeConfig pushCascadeCapacity
  • Retry amplification“error rates”, “timeouts”, “retry”
  • Config propagation“update”
  • Control-plane couplingno 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 18, 3:46 PM PT: 0 itemsOfficial status · Nov 18, 4:32 PM PT: 0 itemsOfficial status · Nov 18, 5:18 PM PT: 0 itemsOfficial status · Nov 18, 6:03 PM PT: 0 itemsOfficial status · Nov 18, 6:49 PM PT: 0 itemsOfficial status · Nov 18, 7:35 PM PT: 0 itemsOfficial status · Nov 18, 8:21 PM PT: 0 itemsOfficial status · Nov 18, 9:07 PM PT: 0 itemsOfficial status · Nov 18, 9:53 PM PT: 0 itemsOfficial status · Nov 18, 10:39 PM PT: 0 itemsOfficial status · Nov 18, 11:24 PM PT: 0 itemsOfficial status · Nov 19, 12:10 AM PT: 0 itemsOfficial status · Nov 19, 12:56 AM PT: 0 itemsOfficial status · Nov 19, 1:42 AM PT: 0 itemsOfficial status · Nov 19, 2:28 AM PT: 0 itemsOfficial status · Nov 19, 3:14 AM PT: 1 itemOfficial status · Nov 19, 3:59 AM PT: 0 itemsOfficial status · Nov 19, 4:45 AM PT: 0 itemsOfficial status · Nov 19, 5:31 AM PT: 0 itemsOfficial status · Nov 19, 6:17 AM PT: 0 itemsOfficial status · Nov 19, 7:03 AM PT: 0 itemsOfficial status · Nov 19, 7:49 AM PT: 0 itemsOfficial status · Nov 19, 8:34 AM PT: 0 itemsOfficial status · Nov 19, 9:20 AM PT: 0 itemsNetwork & routingNetwork & routing · Nov 18, 3:46 PM PT: 0 itemsNetwork & routing · Nov 18, 4:32 PM PT: 0 itemsNetwork & routing · Nov 18, 5:18 PM PT: 0 itemsNetwork & routing · Nov 18, 6:03 PM PT: 0 itemsNetwork & routing · Nov 18, 6:49 PM PT: 0 itemsNetwork & routing · Nov 18, 7:35 PM PT: 0 itemsNetwork & routing · Nov 18, 8:21 PM PT: 0 itemsNetwork & routing · Nov 18, 9:07 PM PT: 0 itemsNetwork & routing · Nov 18, 9:53 PM PT: 0 itemsNetwork & routing · Nov 18, 10:39 PM PT: 0 itemsNetwork & routing · Nov 18, 11:24 PM PT: 0 itemsNetwork & routing · Nov 19, 12:10 AM PT: 0 itemsNetwork & routing · Nov 19, 12:56 AM PT: 0 itemsNetwork & routing · Nov 19, 1:42 AM PT: 0 itemsNetwork & routing · Nov 19, 2:28 AM PT: 0 itemsNetwork & routing · Nov 19, 3:14 AM PT: 0 itemsNetwork & routing · Nov 19, 3:59 AM PT: 0 itemsNetwork & routing · Nov 19, 4:45 AM PT: 0 itemsNetwork & routing · Nov 19, 5:31 AM PT: 0 itemsNetwork & routing · Nov 19, 6:17 AM PT: 0 itemsNetwork & routing · Nov 19, 7:03 AM PT: 0 itemsNetwork & routing · Nov 19, 7:49 AM PT: 0 itemsNetwork & routing · Nov 19, 8:34 AM PT: 0 itemsNetwork & routing · Nov 19, 9:20 AM PT: 0 itemsEarly signalsEarly signals · Nov 18, 3:46 PM PT: 0 itemsEarly signals · Nov 18, 4:32 PM PT: 0 itemsEarly signals · Nov 18, 5:18 PM PT: 0 itemsEarly signals · Nov 18, 6:03 PM PT: 0 itemsEarly signals · Nov 18, 6:49 PM PT: 0 itemsEarly signals · Nov 18, 7:35 PM PT: 0 itemsEarly signals · Nov 18, 8:21 PM PT: 0 itemsEarly signals · Nov 18, 9:07 PM PT: 0 itemsEarly signals · Nov 18, 9:53 PM PT: 0 itemsEarly signals · Nov 18, 10:39 PM PT: 0 itemsEarly signals · Nov 18, 11:24 PM PT: 0 itemsEarly signals · Nov 19, 12:10 AM PT: 0 itemsEarly signals · Nov 19, 12:56 AM PT: 0 itemsEarly signals · Nov 19, 1:42 AM PT: 0 itemsEarly signals · Nov 19, 2:28 AM PT: 0 itemsEarly signals · Nov 19, 3:14 AM PT: 0 itemsEarly signals · Nov 19, 3:59 AM PT: 0 itemsEarly signals · Nov 19, 4:45 AM PT: 0 itemsEarly signals · Nov 19, 5:31 AM PT: 0 itemsEarly signals · Nov 19, 6:17 AM PT: 0 itemsEarly signals · Nov 19, 7:03 AM PT: 0 itemsEarly signals · Nov 19, 7:49 AM PT: 0 itemsEarly signals · Nov 19, 8:34 AM PT: 0 itemsEarly signals · Nov 19, 9:20 AM PT: 0 itemsNews & chatterNews & chatter · Nov 18, 3:46 PM PT: 0 itemsNews & chatter · Nov 18, 4:32 PM PT: 0 itemsNews & chatter · Nov 18, 5:18 PM PT: 0 itemsNews & chatter · Nov 18, 6:03 PM PT: 0 itemsNews & chatter · Nov 18, 6:49 PM PT: 0 itemsNews & chatter · Nov 18, 7:35 PM PT: 0 itemsNews & chatter · Nov 18, 8:21 PM PT: 0 itemsNews & chatter · Nov 18, 9:07 PM PT: 0 itemsNews & chatter · Nov 18, 9:53 PM PT: 0 itemsNews & chatter · Nov 18, 10:39 PM PT: 0 itemsNews & chatter · Nov 18, 11:24 PM PT: 0 itemsNews & chatter · Nov 19, 12:10 AM PT: 0 itemsNews & chatter · Nov 19, 12:56 AM PT: 0 itemsNews & chatter · Nov 19, 1:42 AM PT: 0 itemsNews & chatter · Nov 19, 2:28 AM PT: 0 itemsNews & chatter · Nov 19, 3:14 AM PT: 0 itemsNews & chatter · Nov 19, 3:59 AM PT: 0 itemsNews & chatter · Nov 19, 4:45 AM PT: 0 itemsNews & chatter · Nov 19, 5:31 AM PT: 0 itemsNews & chatter · Nov 19, 6:17 AM PT: 0 itemsNews & chatter · Nov 19, 7:03 AM PT: 0 itemsNews & chatter · Nov 19, 7:49 AM PT: 0 itemsNews & chatter · Nov 19, 8:34 AM PT: 0 itemsNews & chatter · Nov 19, 9:20 AM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Nov 18, 3:46 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 4:32 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 5:18 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 6:03 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 6:49 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 7:35 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 8:21 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 9:07 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 9:53 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 10:39 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 11:24 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 12:10 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 12:56 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 1:42 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 2:28 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 3:14 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 3:59 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 4:45 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 5:31 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 6:17 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 7:03 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 7:49 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 8:34 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 9:20 AM PT: 0 itemsNov 18, 3:46 PM PTNov 19, 10:06 AM PT

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 18, 9:46 PM PTORBIT first saw itNov 19, 3:38 AM PTLatest source updateNov 18, 9:46 PM PTLast checkedNov 21, 4:26 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

  • By the clock it has outlasted 17 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 DigitalOcean.

8Dissection capsule

Share card for this dissection

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

JSON capsuleMarkdownShare card (SVG)

Open DigitalOcean in the War Room →NetWeather evidence page →Status page →

Embed this card
<a href="https://www.chyp.ai/dissect/event-nw-a3ddda3deeedfd18/"><img src="https://www.chyp.ai/dissect/event-nw-a3ddda3deeedfd18/card.svg" alt="DigitalOcean: Increased Error Rates in SFO3 · 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.