H3XA — Operational Evidence

Stress score310–100

Confidence4%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude46%

Breadth2%

Persistence100%

Corroboration0%

Baseline deviation12%

Confidence

Confidence factors

4%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations50%

statistical significance46%

Affected infrastructure

Scope

ASNs—

Services—

RegionsNE

Started2026-08-11 16:15

Last observed2026-09-26 10:25

Evidence

Underlying observations

Internet connectivity disruption in Nigerincident--569995fb-e245-5b96-2d96-a7de11392369

2026-08-11 16:15 voidly-atlas

Internet connectivity disruption in Nigerincident--90b312b2-89e9-5f2b-2d32-c717ca7c01db

2026-08-27 13:30 voidly-atlas

Internet connectivity disruption in Nigerincident--22f19749-f2a3-5f63-368a-987ab7856564

2026-08-29 10:35 voidly-atlas

Internet connectivity disruption in Nigerincident--e5a50f47-72cf-5d8e-dae7-92975ca2c321

2026-09-23 00:25 voidly-atlas

Internet connectivity disruption in Nigerincident--855b4e08-7bf4-5e10-b3a0-e8ed7a71e1a0

2026-09-24 09:35 voidly-atlas

Internet connectivity disruption in Nigerincident--2704930d-4d31-5324-c0b4-e059c9bb8be1

2026-09-26 10: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.