H3XA — Operational Evidence

Stress score350–100

Confidence0%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude11%

Breadth9%

Persistence100%

Corroboration0%

Baseline deviation100%

Confidence

Confidence factors

0%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations60%

statistical significance11%

Affected infrastructure

Scope

ASNs—

ServicesTor

RegionsBY

Started2026-08-10 00:00

Last observed2026-08-28 00:00

Evidence

Underlying observations

Censorship detected in BYincident--7e44909b-c753-5ad6-e8b9-243f4c1a96c5

2026-08-10 00:00 voidly-atlas

Censorship detected in BYincident--638edd75-5643-5aff-618b-b5bd6c409ac4

2026-08-11 00:00 voidly-atlas

Censorship detected in BYincident--1b00cc1d-e9c7-55ff-0d20-c2dd45849f24

2026-08-12 00:00 voidly-atlas

Internet connectivity disruption in Belarusincident--bf90b06a-84eb-5517-2527-cf8cb208514f

2026-08-26 21:30 voidly-atlas

Censorship detected in BYincident--b846e4c0-f106-55ac-d042-58e53f7ad8f1

2026-08-27 00:00 voidly-atlas

Internet connectivity disruption in Belarusincident--738e8311-41d4-589b-58fb-473ce8e5268b

2026-08-27 04:00 voidly-atlas

Censorship detected in BYincident--1a41edb3-6134-5c1c-5381-6c5a7c753b42

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.