H3XA — Operational Evidence

Stress score340–100

Confidence0%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude0%

Breadth22%

Persistence100%

Corroboration0%

Baseline deviation100%

Confidence

Confidence factors

0%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations60%

statistical significance0%

Affected infrastructure

Scope

ASNs—

ServicesTor, Signal, WhatsApp

RegionsAE

Started2026-08-10 00:00

Last observed2026-08-28 00:00

Evidence

Underlying observations

Censorship detected in AEincident--8c92f272-eb3e-5e4d-bd92-5c2491d533b0

2026-08-10 00:00 voidly-atlas

Censorship detected in AEincident--0719a9a0-028d-54e4-6c65-a58cb9645e5b

2026-08-11 00:00 voidly-atlas

Internet censorship detected in UAEincident--f73a0b78-fd5f-5117-dd59-cc8181701f20

2026-08-12 00:00 voidly-atlas

Censorship detected in AEincident--a28a76e9-3cda-57ce-3c35-72df423b4cb9

2026-08-12 00:00 voidly-atlas

Censorship detected in AEincident--eb330e34-78f2-5d1a-daa5-18072dd3590b

2026-08-27 00:00 voidly-atlas

Censorship detected in AEincident--0d5404d4-0c07-58b2-b0d6-83ca9b545e09

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.