H3XA — Operational Evidence

Stress score370–100

Confidence0%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude11%

Breadth44%

Persistence100%

Corroboration0%

Baseline deviation67%

Confidence

Confidence factors

0%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations60%

statistical significance11%

Affected infrastructure

Scope

ASNsAS27725

ServicesFacebook Messenger, Signal, Telegram, Tor, WhatsApp, Facebook, Gemini, Instagram, YouTube

RegionsCU

Started2026-08-28 00:00

Last observed2026-10-02 00:00

Evidence

Underlying observations

Censorship detected in CUincident--91cb7e48-90b9-564b-41b3-c8433e9765e4

2026-08-28 00:00 voidly-atlas

Censorship detected in CUincident--33b5394a-0d07-58d7-f0b2-70f7748e2fd6

2026-08-29 00:00 voidly-atlas

Censorship detected in CUincident--fa1bc3cc-713e-5784-97f5-d231a0db4c1b

2026-09-23 00:00 voidly-atlas

Censorship detected in CUincident--de58a8b2-1f71-582c-2134-74991dc4b05c

2026-09-25 00:00 voidly-atlas

Censorship detected in CUincident--741faa84-996f-5934-3853-992040e83cec

2026-09-26 00:00 voidly-atlas

Internet censorship detected in Cubaincident--4a22c7a8-a2c0-586e-4699-a974ab36cb8f

2026-09-27 00:00 voidly-atlas

Censorship detected in CUincident--4062e72c-05eb-5d7f-e9d9-4c31d8209dbd

2026-09-28 00:00 voidly-atlas

Censorship detected in CUincident--7634dd6d-e745-5368-9b37-ddfab7b2330f

2026-09-29 00:00 voidly-atlas

Internet censorship detected in Cubaincident--a4bd96f4-76a4-5655-541a-daa5b960ab1a

2026-09-30 00:00 voidly-atlas

Censorship detected in CUincident--3dd95d85-98d9-5c3c-f092-a5a5c835651e

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.