Active Incident
Confirmed: network disruption in Pakistan
Pakistan · January 13, 2026 · 46 days
IODA detected significant connectivity drop. 1 critical alerts recorded. CenAlert confirms censorship activity.
Evidence
84%
Anomaly Rate
8
Measurements
70%
Confidence
What This Means
84% of 8 network tests from Pakistan failed to reach these services. Global baseline failure rate is typically 1-3%. This 81+ percentage point difference strongly indicates intentional blocking.
How We Detected This
Data Sourcecensoredplanet + ioda
ML ModelGradientBoosting v3.3 (LOCO median F1 0.87, honest across 127 countries)
Confidence Score70% certainty of censorship
Detection TimeJanuary 13, 2026
Corroborating Evidence (12)
Evidence collected from multiple independent sources. Upstream claims shown in quotes are not Voidly assertions.
IODAInternet Outage Detection & Analysis10 records
outage
"IODA detected critical level outage for F.C.T."— IODA report
Signal value: 0.84
Feb 28, 2026
View source →outage
"IODA detected critical level outage for Punjab"— IODA report
Signal value: 0.90
Feb 28, 2026
View source →outage
"IODA detected critical level outage for Sind"— IODA report
Signal value: 0.80
Feb 28, 2026
View source →outage
"IODA detected critical level outage for Azad Kashmir"— IODA report
Signal value: 0.02
Feb 24, 2026
View source →outage
"IODA detected critical level outage for Azad Kashmir"— IODA report
Signal value: 0.03
Feb 21, 2026
View source →+ 5 more IODA records
Censored PlanetUniversity of Michigan research2 records
http-blocking-tcp-reset
"HTTP blocking (tcp-reset): 5/5 probes blocked (100.0%) for telegram.org"— Censored Planet report
Signal value: 1.00
Feb 19, 2026
View source →http-blocking-tcp-reset
"HTTP blocking (tcp-reset): 8/8 probes blocked (100.0%) for telegram.org"— Censored Planet report
Signal value: 1.00
Feb 4, 2026
View source →Affected Services (1)
Telegram
Blocked Domains (1)
Click any domain to view raw OONI measurements
What we cannot say
- Who caused it — measurement data alone does not attribute this to any government, ISP, or other actor.
- Intent — anomalous or unreachable measurements indicate interference, not a stated motive or a deliberate-vs-incidental determination.
- Which networks — no specific ASN/ISP is identified for this incident.
- The mechanism — we cannot state whether this was DNS tampering, TLS/SNI reset, an HTTP blockpage, throttling, or an infrastructure outage.
- Sub-national scope — measurement is aggregated at the country level; we cannot localize to a province, city, or network segment.
Cite This Incident
Voidly Research. (2026). Confirmed: network disruption in Pakistan [PK-2026-0008]. Voidly Global Censorship Index. https://voidly.ai/incident/PK-2026-0008
Related
Related incidents
More in Pakistan
Internet connectivity disruption in Pakistan
2026-06-20 · Infrastructure outage
Internet censorship detected in Pakistan
2026-06-18 · Connection timeout / throttling
Internet censorship detected in Pakistan
2026-06-17 · DNS blocking
Internet censorship detected in Pakistan
2026-06-16 · Connection timeout / throttling
Internet censorship detected in Pakistan
2026-06-15 · TCP/RST injection
Internet censorship detected in Pakistan
2026-06-14 · DNS blocking
Same mechanism · Infrastructure outage
Internet connectivity disruption in Pakistan
2026-06-05 · Infrastructure outage
Internet connectivity disruption in Pakistan
2026-05-30 · Infrastructure outage
Internet connectivity disruption in Pakistan
2026-05-02 · Infrastructure outage
Internet connectivity disruption in Pakistan
2026-04-27 · Infrastructure outage
Internet connectivity disruption in Pakistan
2026-04-20 · Infrastructure outage