voidly
Active Incident

Internet outage in Kyrgyzstan

Kyrgyzstan · May 3, 2026 · Ongoing

IODA detected significant connectivity drop in Kyrgyzstan. 2 critical alerts recorded.

Evidence

65%
Anomaly Rate
2
Measurements
67%
Confidence

What This Means

65% of 2 network tests from Kyrgyzstan failed to reach these services. Global baseline failure rate is typically 1-3%. This 62+ percentage point difference strongly indicates intentional blocking.

How We Detected This

Data Sourceioda
ML ModelGradientBoosting v3.3 (LOCO median F1 0.87, honest across 127 countries)
Confidence Score67% certainty of censorship
Detection TimeMay 3, 2026

Corroborating Evidence (2)

Evidence collected from multiple independent sources. Upstream claims shown in quotes are not Voidly assertions.

IODAInternet Outage Detection & Analysis2 records
outage
"IODA detected critical level outage for Bishkek"IODA report
Signal value: 0.65
May 3, 2026
View source →
outage
"IODA detected critical level outage for Chuy"IODA report
Signal value: 0.65
May 3, 2026
View source →

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). Internet outage in Kyrgyzstan [KG-2026-0012]. Voidly Global Censorship Index. https://voidly.ai/incident/KG-2026-0012

Related