H3XA — Operational Evidence

Stress score190–100

Confidence0%

TrajectorySTABLE

Statusactive

Explainable score

Stress score components

Anomaly magnitude0%

Breadth2%

Persistence100%

Corroboration0%

Baseline deviation22%

Confidence

Confidence factors

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations60%

statistical significance0%

Affected infrastructure

Scope

ASNs—

Services—

RegionsCV

Started2026-08-26 08:40

Last observed2026-08-29 01:10

Evidence

Underlying observations

voidly-atlas

Internet connectivity disruption in CVincident--2f5b9edb-576d-502d-e922-ed93e6591374

2026-08-26 08:40 voidly-atlas

Internet connectivity disruption in CVincident--3beec4ac-d3fe-510f-be5c-b300b8b174a6

2026-08-27 07:40 voidly-atlas

Internet connectivity disruption in CVincident--d20f7a5a-ffae-5868-999c-08929b6670f6

2026-08-28 00:10 voidly-atlas

Internet connectivity disruption in CVincident--2cc061fd-427a-5cc8-8235-e5a5bf8d6fb5

2026-08-29 01:10

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.