H3XA — Operational Evidence

Stress score320–100

Confidence0%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude0%

Breadth9%

Persistence100%

Corroboration0%

Baseline deviation100%

Confidence

Confidence factors

0%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations60%

statistical significance0%

Affected infrastructure

Scope

ASNs—

ServicesSignal

RegionsOM

Started2026-08-10 00:00

Last observed2026-08-28 00:00

Evidence

Underlying observations

Censorship detected in OMincident--d5408d06-2859-5c5f-fdc8-3e541b589850

2026-08-10 00:00 voidly-atlas

Censorship detected in OMincident--93a8444d-57e2-528a-5d97-930c0ee9afdb

2026-08-11 00:00 voidly-atlas

Censorship detected in OMincident--e36ceffe-5dac-519b-0421-01610ed64057

2026-08-12 00:00 voidly-atlas

Internet censorship detected in Omanincident--70fa4f02-1fd3-551b-b032-74ddcaff9d3b

2026-08-13 00:00 voidly-atlas

Censorship detected in OMincident--3a391423-b34f-51e0-a7c3-36fb202ac157

2026-08-27 00:00 voidly-atlas

Censorship detected in OMincident--b27d39e6-7095-5a50-df11-6f39caf22785

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.