CHYP.ai · ORBIT // Cloudy_Day Security Suite

OUTAGE DISSECTOR · CASE FILE · NetWeather event

GitHub: 1 component degraded performance

GitHub resolved M3.4 Squall since Nov 19, 7:56 AM PT

GitHub reported “GitHub: 1 component degraded performance” starting Nov 19, 7:56 AM PT.

  • 34mDurationstart → resolved
  • 1Peak componentsnow 1
  • —Places named0 on the map
  • 2Dependentscatalogued, inferred
  • 1/4Evidence kindsindependent families
  • 2Updatesofficial revisions

1Scrub the outage

full window
Severitypeak 1 components Nov 19, 7 AMNov 19, 7 AMNov 19, 8 AMNov 19, 8 AMNov 19, 8 AMNov 19, 8 AM Official statusNov 19, 7:56 AM PT · GitHub: 1 component degraded performanceNov 19, 8:30 AM PT · GitHub: 1 component degraded performanceNetwork & 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

GitHub reported “GitHub: 1 component degraded performance” starting Nov 19, 7:56 AM PT.

What broke

The official source does not list components.

Who was hit

2 catalogued services run on GitHub (inferred). Hit: global/unspecified.

How it recovered

Resolved after 34m.

2Blast radius

GitHub Copilot · OperationalGitHub CopilotGitHub Pages · OperationalGitHub PagesMicrosoft Azure · OperationalMicrosoft AzureGitHub2 dependents

Center: GitHub. 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
  • Capacity exhaustion“degraded performance”
  • Retry amplificationno sign
  • Control-plane couplingno sign
  • Config propagationno sign
  • Dependency cascadeno sign

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

5Evidence matrix

Official statusOfficial status · Nov 19, 1:56 AM PT: 0 itemsOfficial status · Nov 19, 2:12 AM PT: 0 itemsOfficial status · Nov 19, 2:28 AM PT: 0 itemsOfficial status · Nov 19, 2:45 AM PT: 0 itemsOfficial status · Nov 19, 3:01 AM PT: 0 itemsOfficial status · Nov 19, 3:18 AM PT: 0 itemsOfficial status · Nov 19, 3:34 AM PT: 0 itemsOfficial status · Nov 19, 3:51 AM PT: 0 itemsOfficial status · Nov 19, 4:07 AM PT: 0 itemsOfficial status · Nov 19, 4:23 AM PT: 0 itemsOfficial status · Nov 19, 4:40 AM PT: 0 itemsOfficial status · Nov 19, 4:56 AM PT: 0 itemsOfficial status · Nov 19, 5:13 AM PT: 0 itemsOfficial status · Nov 19, 5:29 AM PT: 0 itemsOfficial status · Nov 19, 5:46 AM PT: 0 itemsOfficial status · Nov 19, 6:02 AM PT: 0 itemsOfficial status · Nov 19, 6:19 AM PT: 0 itemsOfficial status · Nov 19, 6:35 AM PT: 0 itemsOfficial status · Nov 19, 6:51 AM PT: 0 itemsOfficial status · Nov 19, 7:08 AM PT: 0 itemsOfficial status · Nov 19, 7:24 AM PT: 0 itemsOfficial status · Nov 19, 7:41 AM PT: 1 itemOfficial status · Nov 19, 7:57 AM PT: 0 itemsOfficial status · Nov 19, 8:14 AM PT: 0 itemsNetwork & routingNetwork & routing · Nov 19, 1:56 AM PT: 0 itemsNetwork & routing · Nov 19, 2:12 AM PT: 0 itemsNetwork & routing · Nov 19, 2:28 AM PT: 0 itemsNetwork & routing · Nov 19, 2:45 AM PT: 0 itemsNetwork & routing · Nov 19, 3:01 AM PT: 0 itemsNetwork & routing · Nov 19, 3:18 AM PT: 0 itemsNetwork & routing · Nov 19, 3:34 AM PT: 0 itemsNetwork & routing · Nov 19, 3:51 AM PT: 0 itemsNetwork & routing · Nov 19, 4:07 AM PT: 0 itemsNetwork & routing · Nov 19, 4:23 AM PT: 0 itemsNetwork & routing · Nov 19, 4:40 AM PT: 0 itemsNetwork & routing · Nov 19, 4:56 AM PT: 0 itemsNetwork & routing · Nov 19, 5:13 AM PT: 0 itemsNetwork & routing · Nov 19, 5:29 AM PT: 0 itemsNetwork & routing · Nov 19, 5:46 AM PT: 0 itemsNetwork & routing · Nov 19, 6:02 AM PT: 0 itemsNetwork & routing · Nov 19, 6:19 AM PT: 0 itemsNetwork & routing · Nov 19, 6:35 AM PT: 0 itemsNetwork & routing · Nov 19, 6:51 AM PT: 0 itemsNetwork & routing · Nov 19, 7:08 AM PT: 0 itemsNetwork & routing · Nov 19, 7:24 AM PT: 0 itemsNetwork & routing · Nov 19, 7:41 AM PT: 0 itemsNetwork & routing · Nov 19, 7:57 AM PT: 0 itemsNetwork & routing · Nov 19, 8:14 AM PT: 0 itemsEarly signalsEarly signals · Nov 19, 1:56 AM PT: 0 itemsEarly signals · Nov 19, 2:12 AM PT: 0 itemsEarly signals · Nov 19, 2:28 AM PT: 0 itemsEarly signals · Nov 19, 2:45 AM PT: 0 itemsEarly signals · Nov 19, 3:01 AM PT: 0 itemsEarly signals · Nov 19, 3:18 AM PT: 0 itemsEarly signals · Nov 19, 3:34 AM PT: 0 itemsEarly signals · Nov 19, 3:51 AM PT: 0 itemsEarly signals · Nov 19, 4:07 AM PT: 0 itemsEarly signals · Nov 19, 4:23 AM PT: 0 itemsEarly signals · Nov 19, 4:40 AM PT: 0 itemsEarly signals · Nov 19, 4:56 AM PT: 0 itemsEarly signals · Nov 19, 5:13 AM PT: 0 itemsEarly signals · Nov 19, 5:29 AM PT: 0 itemsEarly signals · Nov 19, 5:46 AM PT: 0 itemsEarly signals · Nov 19, 6:02 AM PT: 0 itemsEarly signals · Nov 19, 6:19 AM PT: 0 itemsEarly signals · Nov 19, 6:35 AM PT: 0 itemsEarly signals · Nov 19, 6:51 AM PT: 0 itemsEarly signals · Nov 19, 7:08 AM PT: 0 itemsEarly signals · Nov 19, 7:24 AM PT: 0 itemsEarly signals · Nov 19, 7:41 AM PT: 0 itemsEarly signals · Nov 19, 7:57 AM PT: 0 itemsEarly signals · Nov 19, 8:14 AM PT: 0 itemsNews & chatterNews & chatter · Nov 19, 1:56 AM PT: 0 itemsNews & chatter · Nov 19, 2:12 AM PT: 0 itemsNews & chatter · Nov 19, 2:28 AM PT: 0 itemsNews & chatter · Nov 19, 2:45 AM PT: 0 itemsNews & chatter · Nov 19, 3:01 AM PT: 0 itemsNews & chatter · Nov 19, 3:18 AM PT: 0 itemsNews & chatter · Nov 19, 3:34 AM PT: 0 itemsNews & chatter · Nov 19, 3:51 AM PT: 0 itemsNews & chatter · Nov 19, 4:07 AM PT: 0 itemsNews & chatter · Nov 19, 4:23 AM PT: 0 itemsNews & chatter · Nov 19, 4:40 AM PT: 0 itemsNews & chatter · Nov 19, 4:56 AM PT: 0 itemsNews & chatter · Nov 19, 5:13 AM PT: 0 itemsNews & chatter · Nov 19, 5:29 AM PT: 0 itemsNews & chatter · Nov 19, 5:46 AM PT: 0 itemsNews & chatter · Nov 19, 6:02 AM PT: 0 itemsNews & chatter · Nov 19, 6:19 AM PT: 0 itemsNews & chatter · Nov 19, 6:35 AM PT: 0 itemsNews & chatter · Nov 19, 6:51 AM PT: 0 itemsNews & chatter · Nov 19, 7:08 AM PT: 0 itemsNews & chatter · Nov 19, 7:24 AM PT: 0 itemsNews & chatter · Nov 19, 7:41 AM PT: 0 itemsNews & chatter · Nov 19, 7:57 AM PT: 0 itemsNews & chatter · Nov 19, 8:14 AM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Nov 19, 1:56 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 2:12 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 2:28 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 2:45 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 3:01 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 3:18 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 3:34 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 3:51 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 4:07 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 4:23 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 4:40 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 4:56 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 5:13 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 5:29 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 5:46 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 6:02 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 6:19 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 6:35 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 6:51 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 7:08 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 7:24 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 7:41 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 7:57 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 8:14 AM PT: 0 itemsNov 19, 1:56 AM PTNov 19, 8:30 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 19, 7:56 AM PTORBIT first saw itNov 19, 7:56 AM PTLatest source updateNov 19, 7:56 AM PTLast checkedNov 21, 8:00 PM PT

Detection gap: 1m between the source's start time and ORBIT's first sighting.

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

  • Small, contained and documented. This is what a well-run status page looks like. Note it, don't panic.

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 GitHub.

8Dissection capsule

Share card for this dissection

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

JSON capsuleMarkdownShare card (SVG)

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

Embed this card
<a href="https://www.chyp.ai/dissect/event-nw-d0e1fd2202f526ed/"><img src="https://www.chyp.ai/dissect/event-nw-d0e1fd2202f526ed/card.svg" alt="GitHub: 1 component 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.