H3XA — Operational Evidence

Stress score330–100

Confidence0%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude0%

Breadth15%

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, Tor

RegionsOM

Started2026-08-10 00:00

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

Censorship detected in OMincident--b2bd55a4-0c79-5bf2-4a48-a0e90fc3ab83

2026-08-29 00:00 voidly-atlas

Censorship detected in OMincident--9c907c84-d243-59b1-97ea-3947415dea8c

2026-09-23 00:00 voidly-atlas

Censorship detected in OMincident--43aecc06-8f35-54db-1828-b92bd7b501be

2026-09-24 00:00 voidly-atlas

Censorship detected in OMincident--b05406f8-70b2-59f2-7587-9e638180bccf

2026-09-25 00:00 voidly-atlas

Internet connectivity disruption in Omanincident--e51d58d0-257f-51bf-00bb-b5cc907efafb

2026-09-25 01:30 voidly-atlas

Censorship detected in OMincident--a9a222aa-2c3e-50df-5fd8-89853007949a

2026-09-26 00:00 voidly-atlas

Censorship detected in OMincident--c073be28-4c08-5f3f-4a64-082f7994985c

2026-09-27 00:00 voidly-atlas

Censorship detected in OMincident--efea8c4e-6913-505f-b061-a452ad1b1557

2026-09-28 00:00 voidly-atlas

Censorship detected in OMincident--7168cf25-0361-531a-6283-b46a87cc34c5

2026-09-29 00:00 voidly-atlas

Censorship detected in OMincident--2e186c96-86bd-517b-e6e9-503814eb1207

2026-09-30 00:00 voidly-atlas

Censorship detected in OMincident--dac8cfe3-c2ef-5b82-7f5c-563c38dd3568

2026-10-01 00:00 voidly-atlas

Censorship detected in OMincident--f1a89bcd-cb73-5700-205d-02f185972bdc

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.