H3XA — Operational Evidence

Stress score570–100

Confidence15%

TrajectorySTABLE

Statusactive

Explainable score

Stress score components

Anomaly magnitude100%

Breadth2%

Persistence100%

Corroboration0%

Baseline deviation76%

Confidence

Confidence factors

15%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations50%

statistical significance100%

Affected infrastructure

Scope

ASNs—

Services—

RegionsNP

Started2026-08-10 13:35

Last observed2026-08-29 06:30

Evidence

Underlying observations

Internet connectivity disruption in Nepalincident--14bc3687-966c-5d9a-99ac-0d15e0c68e92

2026-08-10 13:35 voidly-atlas

Internet connectivity disruption in Nepalincident--8156c893-18c8-5371-5993-a0c25e6a0474

2026-08-11 06:20 voidly-atlas

Internet connectivity disruption in Nepalincident--d41cea34-ed08-5702-c88f-24fa90eb4528

2026-08-12 13:45 voidly-atlas

Internet connectivity disruption in Nepalincident--aad827d8-6d1f-532c-acd4-587cba8f8663

2026-08-13 19:25 voidly-atlas

Internet connectivity disruption in Nepalincident--a52dcec4-adca-5ba4-b587-02d2175f6cb0

2026-08-26 09:10 voidly-atlas

Internet connectivity disruption in Nepalincident--93ab051f-7cd3-5723-cf50-c6566c94e707

2026-08-27 17:15 voidly-atlas

Internet connectivity disruption in Nepalincident--823eecd0-b63a-5523-cec5-e4636137b77a

2026-08-28 03:34 voidly-atlas

Internet connectivity disruption in Nepalincident--bbb0e841-19e2-543b-ec34-ed7c27422f80

2026-08-29 06:30

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.