Active Incident
Censorship detected in Russia
Russia · June 16, 2026 · Ongoing
CenAlert detected interference. Impact: 0.8. Reported by: HTTPS blocking (timeout): 134/166 probes blocked (80.7%) for bbc.com.
Evidence
1%
Anomaly Rate
1
Measurements
65%
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 Score65% certainty of censorship
Detection TimeJune 16, 2026
Corroborating Evidence (6)
Evidence collected from multiple independent sources. Upstream claims shown in quotes are not Voidly assertions.
Censored PlanetUniversity of Michigan research6 records
http-blocking-timeout
"HTTPS blocking (timeout): 134/166 probes blocked (80.7%) for bbc.com"— Censored Planet report
Signal value: 0.81
Jun 16, 2026
View source →http-blocking-tcp-reset
"HTTPS blocking (tcp-reset): 127/164 probes blocked (77.4%) for facebook.com"— Censored Planet report
Signal value: 0.77
Jun 16, 2026
View source →http-blocking-timeout
"HTTPS blocking (timeout): 126/164 probes blocked (76.8%) for instagram.com"— Censored Planet report
Signal value: 0.77
Jun 16, 2026
View source →http-blocking-tcp-reset
"HTTPS blocking (tcp-reset): 126/163 probes blocked (77.3%) for medium.com"— Censored Planet report
Signal value: 0.77
Jun 16, 2026
View source →http-blocking-timeout
"HTTPS blocking (timeout): 128/163 probes blocked (78.5%) for nytimes.com"— Censored Planet report
Signal value: 0.79
Jun 16, 2026
View source →+ 1 more Censored Planet records
Affected Services (6)
BBCFacebookInstagramMediumNew York TimesWhatsApp
Blocked Domains (6)
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.
- A confirmed duration — we report the observation window, not a verified start/stop of any block.
- 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. (2026). Censorship detected in Russia [RU-2026-0529]. Voidly Global Censorship Index. https://voidly.ai/incident/RU-2026-0529
Related
Related incidents
More in Russia
Internet connectivity disruption in Russia
2026-06-20 · Infrastructure outage
Internet censorship detected in Russia
2026-06-17 · DNS blocking
Internet censorship detected in Russia
2026-06-15 · Connection timeout / throttling
Internet censorship detected in Russia
2026-06-14 · DNS blocking
Sustained censorship in RU (2026-06)
2026-06-01
Internet censorship detected in Russia
2026-05-31 · DNS blocking
Same mechanism · Connection timeout / throttling
Internet censorship detected in Russia
2026-05-25 · Connection timeout / throttling
Internet censorship detected in Russia
2026-04-23 · Connection timeout / throttling
Internet censorship detected in Russia
2026-04-13 · Connection timeout / throttling
Internet connectivity disruption in Russia
2026-03-26 · Connection timeout / throttling
Internet connectivity disruption in Russia
2026-03-23 · Connection timeout / throttling