H3XA — Operational Evidence

Stress score500–100

Confidence15%

TrajectorySTABLE

Statusactive

Explainable score

Stress score components

Anomaly magnitude100%

Breadth2%

Persistence100%

Corroboration0%

Baseline deviation32%

Confidence

Confidence factors

15%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations50%

statistical significance100%

Affected infrastructure

Scope

ASNs—

Services—

RegionsUA

Started2026-08-10 09:00

Last observed2026-10-03 14:30

Evidence

Underlying observations

Internet connectivity disruption in Ukraineincident--b7f157eb-830b-58bf-59e4-f10eb8747886

2026-08-10 09:00 voidly-atlas

Internet connectivity disruption in Ukraineincident--c921ee9f-fd27-572c-6dec-8c9811753b59

2026-08-11 00:20 voidly-atlas

Internet connectivity disruption in Ukraineincident--6ebf26cf-ff3c-5d88-c9f9-b36e59b43379

2026-08-12 19:05 voidly-atlas

Internet connectivity disruption in Ukraineincident--21c45573-8675-5d8f-b7f4-2cf9809e2d90

2026-08-13 19:15 voidly-atlas

Internet connectivity disruption in Ukraineincident--103fdc6b-2bda-5c06-adec-c5a0c1686e48

2026-08-26 04:00 voidly-atlas

Internet connectivity disruption in Ukraineincident--488b1a0b-fb99-5f68-a145-d5636fc60716

2026-08-27 00:00 voidly-atlas

Internet connectivity disruption in Ukraineincident--51327833-99f4-5bdd-6a00-ba4b13afc056

2026-08-28 00:05 voidly-atlas

Internet connectivity disruption in Ukraineincident--48c29b06-9140-5f43-ebbe-9652ed69fb26

2026-08-29 05:40 voidly-atlas

Internet connectivity disruption in Ukraineincident--82990682-219a-5400-45a9-e9285032940b

2026-08-30 00:30 voidly-atlas

Internet connectivity disruption in Ukraineincident--8da8c8ed-611a-556c-cc01-6c03d4758e9b

2026-09-23 08:20 voidly-atlas

Internet connectivity disruption in Ukraineincident--7aa311af-af3d-540c-354d-397c50018f07

2026-09-24 02:10 voidly-atlas

Internet connectivity disruption in Ukraineincident--3d90e420-6a98-5313-dccf-154dd80f0a4b

2026-09-25 15:25 voidly-atlas

Internet connectivity disruption in Ukraineincident--315238a8-10db-57dc-e5ce-6b99d05e5668

2026-09-26 02:15 voidly-atlas

Internet connectivity disruption in Ukraineincident--ce012521-5ef8-5e35-7885-02ea3bfc76c9

2026-09-27 02:05 voidly-atlas

Internet connectivity disruption in Ukraineincident--974f54fa-a3ab-537d-cb36-9cd71377df9d

2026-09-28 09:45 voidly-atlas

Internet connectivity disruption in Ukraineincident--4afd449d-bfaa-5c4f-d483-e7bd66bb34f6

2026-09-29 14:50 voidly-atlas

Internet connectivity disruption in Ukraineincident--77017389-b9dd-5c2c-66f3-54eda2db1456

2026-09-30 15:00 voidly-atlas

Internet connectivity disruption in Ukraineincident--6264073c-fc16-5595-2323-644d3ccd8fff

2026-10-01 23:10 voidly-atlas

Internet connectivity disruption in Ukraineincident--8736362b-b138-57a5-4685-d049f033091b

2026-10-02 15:20 voidly-atlas

Internet connectivity disruption in Ukraineincident--42dd8dee-54a1-5154-4a81-eb1647c8a0b3

2026-10-03 14:30

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.