H3XA — Operational Evidence

Stress score160–100

Confidence0%

TrajectorySTABLE

Statusactive

Explainable score

Stress score components

Anomaly magnitude1%

Breadth2%

Persistence100%

Corroboration0%

Baseline deviation1%

Confidence

Confidence factors

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations60%

statistical significance1%

Affected infrastructure

Scope

ASNs—

Services—

RegionsPE

Started2026-08-10 02:00

Last observed2026-10-03 06:00

Evidence

Underlying observations

voidly-atlas

Internet connectivity disruption in Peruincident--5920b67c-6a26-5b04-59dc-4fadd4d0499e

2026-08-10 02:00 voidly-atlas

Internet connectivity disruption in Peruincident--2f7e6fe1-0b42-5a40-ed4d-97a7193a5320

2026-08-12 11:00 voidly-atlas

Internet connectivity disruption in Peruincident--c164a0e8-e914-59cc-c363-4b2f311a1346

2026-09-28 10:00 voidly-atlas

Internet connectivity disruption in Peruincident--905379a4-cfc7-5932-13ca-6e1340fd91cd

2026-09-29 17:15 voidly-atlas

Internet connectivity disruption in Peruincident--1991dab9-14f9-583b-1f5f-cf34393e9a04

2026-10-03 06:00

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.