H3XA — Operational Evidence

Stress score640–100

Confidence15%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude100%

Breadth22%

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, WhatsApp, Telegram

RegionsLY

Started2026-08-12 00:00

Last observed2026-10-02 00:00

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

Censorship detected in LYincident--d2c793c7-8b01-5789-8a1f-feae544e1033

2026-08-29 00:00 voidly-atlas

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

2026-08-29 10:55 voidly-atlas

Internet connectivity disruption in Libyaincident--eb0649bb-edd9-5274-03c2-be74424f40f3

2026-08-30 06:15 voidly-atlas

Censorship detected in LYincident--f1ff4572-7fe5-51fa-40e4-52fe8a68ce37

2026-09-23 00:00 voidly-atlas

Internet connectivity disruption in Libyaincident--3ab0b14c-2be7-5a43-068f-7944f46506ab

2026-09-23 15:05 voidly-atlas

Censorship detected in LYincident--a747e02f-fb5e-5f79-522f-82e1324a2030

2026-09-24 00:00 voidly-atlas

Censorship detected in LYincident--dffca48a-6573-5514-5609-a3df231f84a8

2026-09-25 00:00 voidly-atlas

Censorship detected in LYincident--9fef956d-bfc6-579f-d4f4-ab585e16307d

2026-09-26 00:00 voidly-atlas

Censorship detected in LYincident--e4184d92-aa77-5901-a495-6f25d7b343fa

2026-09-27 00:00 voidly-atlas

Censorship detected in LYincident--8c5f1a13-81f9-58c1-46f6-fefa73640106

2026-09-28 00:00 voidly-atlas

Censorship detected in LYincident--cd03a0b2-4f03-503f-f89b-97136e9e35e1

2026-09-29 00:00 voidly-atlas

Censorship detected in LYincident--065abb4f-d247-5550-ff96-6f6da89c5553

2026-09-30 00:00 voidly-atlas

Censorship detected in LYincident--ccf47888-b8f2-5298-8b76-59091502a07f

2026-10-01 00:00 voidly-atlas

Censorship detected in LYincident--686b48dc-50ca-5fe5-1d09-8cc66a15bd73

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.