H3XA — Operational Evidence

Stress score610–100

Confidence15%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude100%

Breadth15%

Persistence100%

Corroboration0%

Baseline deviation86%

Confidence

Confidence factors

15%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations50%

statistical significance100%

Affected infrastructure

Scope

ASNs—

ServicesFacebook Messenger, WhatsApp

RegionsSN

Started2026-08-10 00:00

Last observed2026-10-02 00:00

Evidence

Underlying observations

Censorship detected in SNincident--4f4d693b-914b-509c-dd3f-aac3fe69f386

2026-08-10 00:00 voidly-atlas

Censorship detected in SNincident--c5fdaa46-a2fa-542e-b6f8-b922617963ca

2026-08-27 00:00 voidly-atlas

Censorship detected in SNincident--513e2dae-a700-51da-8c6a-e857ed0182a8

2026-08-28 00:00 voidly-atlas

Censorship detected in SNincident--1bd63504-767d-576f-a1a0-e32697bb17b4

2026-08-29 00:00 voidly-atlas

Censorship detected in SNincident--5008417c-a34e-5f1e-e876-9b305670c2db

2026-09-28 00:00 voidly-atlas

Censorship detected in SNincident--4966b6c4-0830-537e-b0bd-f387e4740c9a

2026-09-29 00:00 voidly-atlas

Censorship detected in SNincident--e21f34ca-ba6a-5ae6-8f11-6e5b4d91477b

2026-10-01 00:00 voidly-atlas

Censorship detected in SNincident--8e553384-cbcb-59f3-079d-d589ba37f8d0

2026-10-02 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.