H3XA — Operational Evidence

Stress score600–100

Confidence15%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude100%

Breadth44%

Persistence100%

Corroboration0%

Baseline deviation38%

Confidence

Confidence factors

15%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations50%

statistical significance100%

Affected infrastructure

Scope

ASNsAS9498

ServicesChatGPT, Claude, Facebook, Gemini, Instagram, ProtonVPN, Signal, Telegram, TikTok, WhatsApp, X, YouTube

RegionsIN

Started2026-08-11 06:10

Last observed2026-10-02 16:55

Evidence

Underlying observations

Kashmir internet shutdownincident--b6ec6548-62e3-552e-cee0-79c999a7f92a

2019-08-05 00:00 voidly-atlas

Internet connectivity disruption in Indiaincident--15e53b6d-eefc-569f-bf9a-8008f3f4aa57

2026-08-11 06:10 voidly-atlas

Internet censorship detected in Indiaincident--0b41d993-b7a0-5576-f405-134f58fa8a0f

2026-08-12 00:00 voidly-atlas

Internet connectivity disruption in Indiaincident--d106f25e-612a-5b83-6110-b89ac1753d1c

2026-08-28 18:35 voidly-atlas

Internet connectivity disruption in Indiaincident--1a5fbdc9-1f3e-5062-14e7-c5c4cd8c2ac9

2026-08-30 16:15 voidly-atlas

Internet connectivity disruption in Indiaincident--72b226e5-f200-5e39-a950-cbc998cdd874

2026-09-22 13:30 voidly-atlas

Internet censorship detected in Indiaincident--feacb9f2-82bf-59e2-571c-845bdc40937c

2026-09-23 00:00 voidly-atlas

Internet censorship detected in Indiaincident--b2d64b9d-b06b-5618-bfad-9b6c6c6dfc5f

2026-09-27 00:00 voidly-atlas

Internet connectivity disruption in Indiaincident--ef1c079e-65dd-5c80-c371-6ceaf8ef072b

2026-09-28 19:50 voidly-atlas

Internet connectivity disruption in Indiaincident--7208fd71-6810-5a71-4f5a-07ef619d14a9

2026-09-30 19:55 voidly-atlas

Internet connectivity disruption in Indiaincident--edb728b4-3e05-5259-8036-9eee19bbed2c

2026-10-01 22:20 voidly-atlas

Internet connectivity disruption in Indiaincident--ed55823d-7945-5466-ae7a-8e64956ddcc9

2026-10-02 16:55

Alternative explanations

What else could this be?

single-source signal
insufficient corroboration

Provenance

Ownership boundary

This event is an h3xa-derived analytical product. The evidence references above point to source-owned STIX observations; h3xa claims no ownership of the underlying data.