H3XA — Operational Evidence

Stress score370–100

Confidence0%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude0%

Breadth35%

Persistence100%

Corroboration0%

Baseline deviation100%

Confidence

Confidence factors

0%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations60%

statistical significance0%

Affected infrastructure

Scope

ASNs—

ServicesFacebook Messenger, Signal, Telegram, Tor, WhatsApp

RegionsCN

Started2026-08-10 00:00

Last observed2026-08-28 00:00

Evidence

Underlying observations

Censorship detected in CNincident--ebc592eb-af2e-5274-30ff-de7bbda93b7c

2026-08-10 00:00 voidly-atlas

Censorship detected in CNincident--86e115a0-cb80-534f-d46d-924df55f6a2e

2026-08-11 00:00 voidly-atlas

Internet connectivity disruption in Chinaincident--928aaab2-3f7c-5e86-47ba-0d5caef3981c

2026-08-11 17:10 voidly-atlas

Censorship detected in CNincident--d44ffdd1-c044-50d4-d81a-40b24d8b8e89

2026-08-12 00:00 voidly-atlas

Censorship detected in CNincident--8852ddc9-5cd5-53b9-8b0a-f95768475932

2026-08-27 00:00 voidly-atlas

Censorship detected in CNincident--9511a42e-217b-507b-1cf7-0a94032de3f4

2026-08-28 00:00

Alternative explanations

What else could this be?

single-source signal
low statistical significance
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.