Infrastructure Stress Event · h3xa-derived
country PK · PK
Application restriction — derived from 1 independent signal across 21 observations.
Stress score400–100
Confidence0%
TrajectoryRESOLVED
Statusresolved
Explainable score
Stress score components
Anomaly magnitude0%
Breadth48%
Persistence100%
Corroboration0%
Baseline deviation100%
Confidence
Confidence factors
0%
method diversity25%
source agreement0%
timestamp overlap0%
infrastructure overlap0%
alternative explanations60%
statistical significance0%
Affected infrastructure
Scope
ASNsAS17557, AS24440, AS45773
ServicesSignal, Telegram, Tor, Psiphon, ProtonVPN, ChatGPT, Claude, Facebook, Gemini, Instagram, TikTok, X, YouTube
RegionsPK
Started2026-08-10 00:00
Last observed2026-10-02 00:00
Evidence
Underlying observations
voidly-atlas
Censorship detected in PKincident--bc3cb634-bb3c-58c5-3e06-015689dcb39e
voidly-atlasCensorship detected in PKincident--5270815c-5dc8-5079-27bb-a6c68933ab0d
voidly-atlasCensorship detected in PKincident--972d48f3-89c4-5f0b-936f-0f8445615308
voidly-atlasInternet connectivity disruption in Pakistanincident--e7730ad1-a777-55fe-a53d-12c4573b325e
voidly-atlasCensorship detected in PKincident--1e916b8e-d9b4-5b9c-981d-c05c141f8e1f
voidly-atlasInternet connectivity disruption in Pakistanincident--9395081a-197d-5025-e852-b2eba983ce08
voidly-atlasCensorship detected in PKincident--1c014644-57ea-5f56-b0a2-79dd2750b920
voidly-atlasInternet connectivity disruption in Pakistanincident--9563ab1a-a407-5e6d-27f4-87e7c0d456f3
voidly-atlasCensorship detected in PKincident--12e0c8b7-0d85-51fa-3940-0a9e50e99328
voidly-atlasCensorship detected in PKincident--7de543f4-c353-5524-1e32-6dd6bab52e58
voidly-atlasCensorship detected in PKincident--89e92a01-1866-5bec-cc40-1d772741bf7f
voidly-atlasCensorship detected in PKincident--adc37ba6-e650-5e26-b622-aa3af60d2981
voidly-atlasInternet connectivity disruption in Pakistanincident--b9d7bc37-bc5a-5525-6464-c3c869d16c9b
voidly-atlasCensorship detected in PKincident--aa239ef8-59ec-5683-8e96-90eeef031fb5
voidly-atlasCensorship detected in PKincident--8ef2b8e0-27a1-5fd4-e2b1-0536c4990100
voidly-atlasInternet connectivity disruption in Pakistanincident--a0daad92-1c19-56da-8fa9-e8b2b50b3de0
voidly-atlasCensorship detected in PKincident--c488ee09-57ae-54be-7ddc-8830c42e3b6d
voidly-atlasCensorship detected in PKincident--b294811f-8c40-5948-c6ed-067c73abdece
voidly-atlasCensorship detected in PKincident--21c492ac-551f-562f-1cf1-84a2036039f5
voidly-atlasCensorship detected in PKincident--4f525271-7edf-580c-db8d-795abb92627a
voidly-atlasCensorship detected in PKincident--3ba05474-ca77-523d-4b53-cfb532001a13
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.