H3XA — Operational Evidence

Stress score490–100

Confidence15%

TrajectorySTABLE

Statusactive

Explainable score

Stress score components

Anomaly magnitude100%

Breadth2%

Persistence100%

Corroboration0%

Baseline deviation27%

Confidence

Confidence factors

15%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations50%

statistical significance100%

Affected infrastructure

Scope

ASNs—

Services—

RegionsCD

Started2026-08-10 02:25

Last observed2026-10-03 11:55

Evidence

Underlying observations

Internet connectivity disruption in DR Congoincident--1a569e5b-03ea-5a67-8629-809f0be4da63

2026-08-10 02:25 voidly-atlas

Internet connectivity disruption in DR Congoincident--8fd182d6-4366-5de5-70a3-3265c6442429

2026-08-11 20:25 voidly-atlas

Internet connectivity disruption in DR Congoincident--d362e715-94b1-5c27-6ae3-65122cead82a

2026-08-12 10:00 voidly-atlas

Internet connectivity disruption in DR Congoincident--d4e5673a-7f05-5196-4d36-ccf9e21fc283

2026-08-13 03:45 voidly-atlas

Internet connectivity disruption in DR Congoincident--5cdbe5ef-dc21-53be-95c5-6808ba4527f6

2026-08-26 10:00 voidly-atlas

Internet connectivity disruption in DR Congoincident--2e014304-fe55-5078-3693-b1f7e8e00db2

2026-08-28 02:20 voidly-atlas

Internet connectivity disruption in DR Congoincident--0c4ae1e7-7968-5453-3d6b-c1c21e50e966

2026-08-29 02:10 voidly-atlas

Internet connectivity disruption in DR Congoincident--774af283-cc91-519f-d903-61a8758b4c22

2026-08-30 05:00 voidly-atlas

Internet connectivity disruption in DR Congoincident--27af41f9-9e58-5c0c-1437-4d2c0800e1f0

2026-09-23 02:55 voidly-atlas

Internet connectivity disruption in DR Congoincident--4415bd6e-bdc4-579b-2f02-73cb84647fad

2026-09-24 11:55 voidly-atlas

Internet connectivity disruption in DR Congoincident--af14ada8-b853-54d3-9407-ef9d3be334f8

2026-09-25 03:15 voidly-atlas

Internet connectivity disruption in DR Congoincident--f6e6c002-a90a-5902-dddd-0a2db973dd07

2026-09-26 11:55 voidly-atlas

Internet connectivity disruption in DR Congoincident--f57a0506-1c9c-5bfa-50df-d663e3ae99d9

2026-09-27 05:10 voidly-atlas

Internet connectivity disruption in DR Congoincident--ba53b2f4-66eb-5ee1-4457-ff72f2172790

2026-09-28 13:30 voidly-atlas

Internet connectivity disruption in DR Congoincident--725ddf33-5cd0-5f92-eff4-7a42b632cc25

2026-09-29 11:00 voidly-atlas

Internet connectivity disruption in DR Congoincident--d04b9f3f-96d2-5943-234e-92c00e29652c

2026-09-30 11:55 voidly-atlas

Internet connectivity disruption in DR Congoincident--e216df56-75b9-56a3-adc4-0cbfaff541c7

2026-10-01 00:45 voidly-atlas

Internet connectivity disruption in DR Congoincident--87dde820-2759-5d6c-0e2a-7a542e65f805

2026-10-02 11:55 voidly-atlas

Internet connectivity disruption in DR Congoincident--946962a6-b3f3-54b6-ea8f-8138ce518e99

2026-10-03 11:55

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.