H3XA — Operational Evidence

Stress score620–100

Confidence15%

TrajectorySTABLE

Statusactive

Explainable score

Stress score components

Anomaly magnitude100%

Breadth9%

Persistence100%

Corroboration0%

Baseline deviation100%

Confidence

Confidence factors

15%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations50%

statistical significance100%

Affected infrastructure

Scope

ASNs—

ServicesFacebook Messenger

RegionsLY

Started2026-08-12 00:00

Last observed2026-08-29 10:55

Evidence

Underlying observations

Censorship detected in LYincident--13798307-b69d-52f2-8bcc-e18e174a69c0

2026-08-12 00:00 voidly-atlas

Internet connectivity disruption in Libyaincident--00f78c7d-9ac0-5122-7176-8cf34ba31e55

2026-08-26 11:55 voidly-atlas

Internet connectivity disruption in Libyaincident--aef30c6d-e468-5438-c322-7253138c6c4c

2026-08-27 03:05 voidly-atlas

Censorship detected in LYincident--98f342ae-d9a9-5b00-fcfb-ddcd13097f97

2026-08-28 00:00 voidly-atlas

Internet connectivity disruption in Libyaincident--ed1a2464-1f61-5a71-8bd6-274726143558

2026-08-28 20:00 voidly-atlas

Internet connectivity disruption in Libyaincident--07eb70fd-85e4-5fc2-5033-c04b30dc30cf

2026-08-29 10:55

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.