H3XA — Operational Evidence

Stress score640–100

Confidence15%

TrajectorySTABLE

Statusactive

Explainable score

Stress score components

Anomaly magnitude100%

Breadth35%

Persistence100%

Corroboration0%

Baseline deviation81%

Confidence

Confidence factors

15%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations50%

statistical significance100%

Affected infrastructure

Scope

ASNs—

ServicesFacebook Messenger, Signal, Telegram, Tor, WhatsApp

RegionsLB

Started2026-08-11 00:00

Last observed2026-08-29 02:20

Evidence

Underlying observations

Censorship detected in LBincident--d7be26ec-faff-58c2-9504-2e8bbb8aac0e

2026-08-11 00:00 voidly-atlas

Internet connectivity disruption in Lebanonincident--52c78a15-348f-52fe-a659-2aaf63159c60

2026-08-12 02:20 voidly-atlas

Internet connectivity disruption in Lebanonincident--8741a254-2a28-5758-5132-04c8b8832f38

2026-08-26 06:25 voidly-atlas

Censorship detected in LBincident--dc6c40e4-2fa4-542d-dc8a-0f5ccd725ce6

2026-08-27 00:00 voidly-atlas

Censorship detected in LBincident--52259dd2-5d54-54f4-6edf-609caa3bc1ce

2026-08-28 00:00 voidly-atlas

Internet connectivity disruption in Lebanonincident--1d19a992-bd81-5ab1-b251-b086cc49b2d7

2026-08-29 02:20

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.