H3XA — Operational Evidence

Stress score360–100

Confidence0%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude21%

Breadth9%

Persistence100%

Corroboration0%

Baseline deviation90%

Confidence

Confidence factors

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations60%

statistical significance21%

Affected infrastructure

Scope

ASNs—

ServicesTor

RegionsSY

Started2026-08-10 10:30

Last observed2026-08-27 13:45

Evidence

Underlying observations

voidly-atlas

Internet connectivity disruption in Syriaincident--b042a13a-9bee-5e4a-de98-eebbdbeb073d

2026-08-10 10:30 voidly-atlas

Censorship detected in SYincident--a39daef2-f06d-5abb-fbe8-c3c94f714b28

2026-08-11 00:00 voidly-atlas

Internet connectivity disruption in Syriaincident--95e7973e-e0b3-5fb6-9929-dd5d6025b596

2026-08-11 02:20 voidly-atlas

Internet connectivity disruption in Syriaincident--1ca9d93a-68d5-51df-3780-df230e98494a

2026-08-13 10:50 voidly-atlas

Internet connectivity disruption in Syriaincident--a4d27075-3d0b-5776-72fb-cf5597b870f3

2026-08-27 13:45

Alternative explanations

What else could this be?

single-source signal
low statistical significance
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.