H3XA — Operational Evidence

Stress score600–100

Confidence15%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude100%

Breadth28%

Persistence100%

Corroboration0%

Baseline deviation66%

Confidence

Confidence factors

15%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations50%

statistical significance100%

Affected infrastructure

Scope

ASNsAS212082, AS202660, AS8193

ServicesFacebook Messenger, TikTok, Psiphon

RegionsUZ

Started2026-08-12 00:00

Last observed2026-10-01 00:00

Evidence

Underlying observations

Internet censorship detected in Uzbekistanincident--19643d1f-1834-5a63-9d12-8fdf13d078b6

2026-08-12 00:00 voidly-atlas

Censorship detected in UZincident--51f7dc7a-66a5-5bc6-4595-514bb5c6d4a3

2026-08-27 00:00 voidly-atlas

Censorship detected in UZincident--698d1f2d-c64e-5499-3f34-ea000c4b51e6

2026-08-28 00:00 voidly-atlas

Censorship detected in UZincident--3a230a39-1393-56a1-bd1c-500f9c645ad7

2026-08-29 00:00 voidly-atlas

Censorship detected in UZincident--4a8c2492-1dd5-581b-0130-80a1931b04fd

2026-09-23 00:00 voidly-atlas

Internet censorship detected in Uzbekistanincident--7603ed68-9935-5052-f9ec-f511a39a4550

2026-09-24 00:00 voidly-atlas

Censorship detected in UZincident--c12f7be2-08b5-5247-1eb5-b84a5be00bc1

2026-09-27 00:00 voidly-atlas

Internet censorship detected in Uzbekistanincident--5dd6acbb-890c-5fc8-7c76-c9b24ff61325

2026-09-28 00:00 voidly-atlas

Internet censorship detected in Uzbekistanincident--5e6e6caf-bef8-55d1-41b2-0afcde273c2e

2026-09-30 00:00 voidly-atlas

Internet censorship detected in Uzbekistanincident--9d4c400c-c5df-5ad8-040e-931b4f953a69

2026-10-01 00:00

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.