H3XA — Operational Evidence

Stress score200–100

Confidence0%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude7%

Breadth2%

Persistence100%

Corroboration0%

Baseline deviation20%

Confidence

Confidence factors

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations60%

statistical significance7%

Affected infrastructure

Scope

ASNs—

Services—

RegionsZW

Started2026-08-10 16:05

Last observed2026-08-28 13:40

Evidence

Underlying observations

voidly-atlas

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

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.