Active Incident
Confirmed: censorship detected in Pakistan
Pakistan · September 20, 2025 · 162 days
CenAlert detected interference. Impact: 1.0. Reported by: HTTP blocking (tcp-reset): 5/5 probes blocked (100.0%) for telegram.org.
Evidence
1%
Anomaly Rate
7
Measurements
75%
Confidence
What This Means
1% of tests showed anomalies, above the typical 1-3% baseline. This suggests potential network interference.
How We Detected This
Data Sourcecensoredplanet
ML ModelGradientBoosting v3.3 (LOCO median F1 0.87, honest across 127 countries)
Confidence Score75% certainty of censorship
Detection TimeSeptember 20, 2025
Corroborating Evidence (96)
Evidence collected from multiple independent sources. Upstream claims shown in quotes are not Voidly assertions.
Censored PlanetUniversity of Michigan research96 records
http-blocking-tcp-reset
"HTTP blocking (tcp-reset): 6/7 probes blocked (85.7%) for telegram.org"— Censored Planet report
Signal value: 0.86
Mar 1, 2026
View source →dns-blocking
"DNS blocking detected: 4/4 probes anomalous (100.0%) for bbc.com"— Censored Planet report
Signal value: 1.00
Mar 1, 2026
View source →dns-blocking
"DNS blocking detected: 4/4 probes anomalous (100.0%) for binance.com"— Censored Planet report
Signal value: 1.00
Mar 1, 2026
View source →dns-blocking
"DNS blocking detected: 3/3 probes anomalous (100.0%) for facebook.com"— Censored Planet report
Signal value: 1.00
Mar 1, 2026
View source →dns-blocking
"DNS blocking detected: 4/4 probes anomalous (100.0%) for getlantern.org"— Censored Planet report
Signal value: 1.00
Mar 1, 2026
View source →+ 91 more Censored Planet records
Affected Services (16)
BBCFacebookInstagramLanternMediumNew York TimesProton VPNProtonVPNPsiphonSignalTelegramThe GuardianTikTokTwitter/XXYouTube
Blocked Domains (20)
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.
- Independent corroboration — this rests on a single source; treat it as a single-source signal, not a multi-source confirmation.
Cite This Incident
Voidly Research. (2025). Confirmed: censorship detected in Pakistan [PK-2025-0007]. Voidly Global Censorship Index. https://voidly.ai/incident/PK-2025-0007
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 · DNS blocking
Internet censorship detected in Pakistan
2026-06-10 · DNS blocking
Internet censorship detected in Pakistan
2026-06-07 · DNS blocking
Internet censorship detected in Pakistan
2026-06-03 · DNS blocking
Internet censorship detected in Pakistan
2026-05-31 · DNS blocking
Internet censorship detected in Pakistan
2026-05-27 · DNS blocking