H3XA — Operational Evidence

Stress score410–100

Confidence0%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude11%

Breadth39%

Persistence100%

Corroboration0%

Baseline deviation100%

Confidence

Confidence factors

0%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations60%

statistical significance11%

Affected infrastructure

Scope

ASNsAS38980, AS6697

ServicesTor, BBC, Psiphon, Facebook, YouTube

RegionsBY

Started2026-08-10 00:00

Last observed2026-10-02 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 voidly-atlas

Censorship detected in BYincident--7f309b4e-6bd3-54ff-56d8-2575491f464d

2026-08-29 00:00 voidly-atlas

Internet connectivity disruption in Belarusincident--cfe547f0-1430-547c-5eb1-b76d71b36ff0

2026-09-22 21:40 voidly-atlas

Censorship detected in BYincident--52e3f35a-b7ed-5777-0f37-34057cbf0d0f

2026-09-23 00:00 voidly-atlas

Censorship detected in BYincident--be3936dc-2dfc-5ef6-2424-8c810d0b317a

2026-09-24 00:00 voidly-atlas

Censorship detected in BYincident--cf5259f7-8705-5a10-c623-d4ccb8820621

2026-09-25 00:00 voidly-atlas

Censorship detected in BYincident--62dc2716-b968-592e-8445-4c695bf312cf

2026-09-26 00:00 voidly-atlas

Censorship detected in BYincident--e91ee2ad-8cfb-5a63-2ef2-30ec2febd854

2026-09-27 00:00 voidly-atlas

Censorship detected in BYincident--c476ea7a-8890-5295-b690-2e5c71d8721a

2026-09-28 00:00 voidly-atlas

Censorship detected in BYincident--73cb5a06-875b-57e8-6268-050844580fa2

2026-09-29 00:00 voidly-atlas

Censorship detected in BYincident--fd30d342-ddba-5054-5d6b-1f11844a41d6

2026-09-30 00:00 voidly-atlas

Censorship detected in BYincident--9930728d-fe6e-5713-703d-f6221b3a35af

2026-10-01 00:00 voidly-atlas

Censorship detected in BYincident--a01f498e-d83f-598b-b212-f6e79f8c6615

2026-10-02 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.