H3XA — Operational Evidence

Stress score490–100

Confidence15%

TrajectorySTABLE

Statusactive

Explainable score

Stress score components

Anomaly magnitude100%

Breadth2%

Persistence100%

Corroboration0%

Baseline deviation21%

Confidence

Confidence factors

15%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations50%

statistical significance100%

Affected infrastructure

Scope

ASNs—

Services—

RegionsBW

Started2026-08-13 09:00

Last observed2026-10-03 00:25

Evidence

Underlying observations

voidly-atlas

Internet connectivity disruption in BWincident--288adf43-b52f-5551-f30d-f3b7944833c0

2026-08-13 09:00 voidly-atlas

Internet connectivity disruption in BWincident--043347e4-d406-5ed3-4e10-c15e44a7eac3

2026-09-23 07:30 voidly-atlas

Internet connectivity disruption in BWincident--9e74061d-5324-56d5-cd8d-41da22683f1e

2026-09-27 03:30 voidly-atlas

Internet connectivity disruption in BWincident--ba61d6d5-1420-500c-5b03-a206cf06f663

2026-10-03 00:25

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.