H3XA — Operational Evidence

Stress score640–100

Confidence15%

TrajectoryRESOLVED

Statusresolved

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-10-02 13:35

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

Censorship detected in LBincident--c4e765e3-d18c-5553-5031-205b11807b9e

2026-08-29 00:00 voidly-atlas

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

2026-08-29 02:20 voidly-atlas

Censorship detected in LBincident--060cbfb7-0dfd-5099-abcf-76413739cbd8

2026-09-23 00:00 voidly-atlas

Censorship detected in LBincident--4870b83a-dda7-54d1-39f5-30c8cc3049d4

2026-09-24 00:00 voidly-atlas

Internet connectivity disruption in Lebanonincident--0b6614d6-5024-5a13-2bdb-cbb5226baf6d

2026-09-24 19:55 voidly-atlas

Censorship detected in LBincident--3a2e6c78-8415-51dd-3743-7a08a0403c0b

2026-09-25 00:00 voidly-atlas

Internet connectivity disruption in Lebanonincident--f8c5e92f-13a3-5ccc-ba39-58eade5d73f2

2026-09-25 02:55 voidly-atlas

Censorship detected in LBincident--360ea9ba-d8d5-535f-db82-c811c049899a

2026-09-27 00:00 voidly-atlas

Censorship detected in LBincident--5def09ab-55ad-5528-ff2d-ac9c6dbd1b2b

2026-09-28 00:00 voidly-atlas

Internet connectivity disruption in Lebanonincident--32406763-4096-550b-6da7-177a2bd49cef

2026-09-28 07:40 voidly-atlas

Censorship detected in LBincident--92b5ab60-1330-5488-610e-cae93871312b

2026-09-29 00:00 voidly-atlas

Internet connectivity disruption in Lebanonincident--e01848a4-017a-53c5-b0d3-d580dcef16a1

2026-09-29 01:05 voidly-atlas

Censorship detected in LBincident--a0a22641-45d7-5e72-16e3-adcdfea798c8

2026-09-30 00:00 voidly-atlas

Internet connectivity disruption in Lebanonincident--a84ceaa8-420a-5ad7-bb7d-229e1c8d6f30

2026-09-30 22:15 voidly-atlas

Censorship detected in LBincident--c25b9c95-9909-5116-923c-c4af2e30c3de

2026-10-02 00:00 voidly-atlas

Internet connectivity disruption in Lebanonincident--cf54051e-3f61-5f0f-e0c7-e3978f659c74

2026-10-02 13:35

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.