H3XA — Operational Evidence

Stress score610–100

Confidence15%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude100%

Breadth9%

Persistence100%

Corroboration0%

Baseline deviation95%

Confidence

Confidence factors

15%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations50%

statistical significance100%

Affected infrastructure

Scope

ASNs—

ServicesTor

RegionsZW

Started2026-08-10 16:05

Last observed2026-10-01 13:05

Evidence

Underlying observations

Internet connectivity disruption in Zimbabweincident--a2665535-8e4c-5797-d114-0dcb27d61266

2026-08-10 16:05 voidly-atlas

Internet connectivity disruption in Zimbabweincident--053cb141-3744-5d73-47fa-b7a90b331574

2026-08-13 16:00 voidly-atlas

Internet connectivity disruption in Zimbabweincident--fd3985ff-ddd3-509b-70cf-29e5ab50a983

2026-08-26 08:20 voidly-atlas

Internet connectivity disruption in Zimbabweincident--8a742e09-8908-52c9-5d9b-56750bb26248

2026-08-27 16:25 voidly-atlas

Internet connectivity disruption in Zimbabweincident--a0d31590-2e07-522a-a885-d9cfe5ce9936

2026-08-28 13:40 voidly-atlas

Internet connectivity disruption in Zimbabweincident--c11dda24-dbcd-51fa-6fff-67112900336a

2026-08-30 13:45 voidly-atlas

Internet connectivity disruption in Zimbabweincident--b85b1d13-f84f-59a6-0784-9ab6acea0489

2026-09-25 19:20 voidly-atlas

Internet connectivity disruption in Zimbabweincident--eec82865-60e3-57d1-82fd-0e50f7f53cf5

2026-09-26 11:25 voidly-atlas

Internet connectivity disruption in Zimbabweincident--63c08da0-5ea9-5855-6ab6-4af0021ac7ac

2026-09-27 05:45 voidly-atlas

Censorship detected in ZWincident--02f2f369-ef69-5ef4-ab5b-514cb234b49c

2026-09-28 00:00 voidly-atlas

Internet connectivity disruption in Zimbabweincident--80a868d6-cedd-5b94-f095-57545af01f3a

2026-09-28 04:55 voidly-atlas

Internet connectivity disruption in Zimbabweincident--d5a89477-1983-5ba1-96a1-e0fd19985068

2026-09-30 08:55 voidly-atlas

Internet connectivity disruption in Zimbabweincident--0f7a2144-1e7c-5f65-06bf-669bd5d42e1e

2026-10-01 13:05

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.