H3XA — Operational Evidence

Stress score340–100

Confidence0%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude0%

Breadth22%

Persistence100%

Corroboration0%

Baseline deviation100%

Confidence

Confidence factors

0%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations60%

statistical significance0%

Affected infrastructure

Scope

ASNs—

ServicesSignal, Telegram, Tor

RegionsPK

Started2026-08-10 00:00

Last observed2026-08-28 07:45

Evidence

Underlying observations

Censorship detected in PKincident--bc3cb634-bb3c-58c5-3e06-015689dcb39e

2026-08-10 00:00 voidly-atlas

Censorship detected in PKincident--5270815c-5dc8-5079-27bb-a6c68933ab0d

2026-08-11 00:00 voidly-atlas

Censorship detected in PKincident--972d48f3-89c4-5f0b-936f-0f8445615308

2026-08-12 00:00 voidly-atlas

Internet connectivity disruption in Pakistanincident--e7730ad1-a777-55fe-a53d-12c4573b325e

2026-08-26 20:40 voidly-atlas

Censorship detected in PKincident--1e916b8e-d9b4-5b9c-981d-c05c141f8e1f

2026-08-27 00:00 voidly-atlas

Internet connectivity disruption in Pakistanincident--9395081a-197d-5025-e852-b2eba983ce08

2026-08-27 05:20 voidly-atlas

Censorship detected in PKincident--1c014644-57ea-5f56-b0a2-79dd2750b920

2026-08-28 00:00 voidly-atlas

Internet connectivity disruption in Pakistanincident--9563ab1a-a407-5e6d-27f4-87e7c0d456f3

2026-08-28 07:45

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.