H3XA — Operational Evidence

Stress score650–100

Confidence15%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude100%

Breadth44%

Persistence100%

Corroboration0%

Baseline deviation78%

Confidence

Confidence factors

15%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations50%

statistical significance100%

Affected infrastructure

Scope

ASNsAS6713

ServicesTor, ChatGPT, Claude, Facebook, Gemini, Instagram, ProtonVPN, Signal, Telegram, TikTok, WhatsApp, X, YouTube

RegionsMA

Started2026-08-10 00:00

Last observed2026-10-01 00:00

Evidence

Underlying observations

Censorship detected in MAincident--122094d2-2ad6-5fa7-2e85-539dba1a695d

2026-08-10 00:00 voidly-atlas

Censorship detected in MAincident--6af2ae9e-a179-50e9-7dd5-7a5190823b56

2026-08-11 00:00 voidly-atlas

Internet censorship detected in Moroccoincident--58566138-b39b-59a4-e56a-8bc5b7f34c20

2026-09-23 00:00 voidly-atlas

Internet censorship detected in Moroccoincident--1eea4983-31a6-5230-8cff-5bb6da39b985

2026-09-27 00:00 voidly-atlas

Internet censorship detected in Moroccoincident--27075081-dad8-53a0-fec9-a9bcdad569c9

2026-09-30 00:00 voidly-atlas

Censorship detected in MAincident--abcbd5f7-20e4-5384-8473-33d8199a41c4

2026-10-01 00:00

Alternative explanations

What else could this be?

single-source signal
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.