H3XA — Operational Evidence

Stress score340–100

Confidence0%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude28%

Breadth24%

Persistence100%

Corroboration0%

Baseline deviation42%

Confidence

Confidence factors

0%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations60%

statistical significance28%

Affected infrastructure

Scope

ASNsAS51375

ServicesProtonVPN, X, WhatsApp

RegionsBH

Started2026-08-12 00:00

Last observed2026-09-30 00:00

Evidence

Underlying observations

Internet censorship detected in Bahrainincident--35143280-45a6-50b2-d8d7-4853169fda29

2026-08-12 00:00 voidly-atlas

Internet censorship detected in Bahrainincident--58cb18cd-12dc-5bd3-1e05-2717444f2166

2026-09-23 00:00 voidly-atlas

Internet connectivity disruption in Bahrainincident--c4e77a4e-f32a-5052-00fb-efc7837e2b0c

2026-09-25 01:40 voidly-atlas

Internet censorship detected in Bahrainincident--557c510c-eb30-5183-0ec3-50bcf58265bc

2026-09-27 00:00 voidly-atlas

Censorship detected in BHincident--04c43ee9-24b5-5369-4a6f-62a04bf0e972

2026-09-29 00:00 voidly-atlas

Internet censorship detected in Bahrainincident--d464dad4-1810-5967-c77d-09eccc02011d

2026-09-30 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.