voidly
Transparency · Probe network

Where our probes actually are

Voidly operates 16+ probe nodes globally — but they're mostly in non-censoring countries. This page is the honest disclosure of where we DO have inside-country presence and where we DON'T, vs where censorship actually happens.

Updated every 30 minutes from /v1/probe/network · CC BY 4.0

Total nodes
16
active probes
Countries covered
14
inside-country presence
Top-country coverage
10%
50/515 incidents inside-covered
High-censorship gaps
28
countries without probes

The honest version

Our probe nodes are mostly hosted in places where it's easy to host probes — the US, UK, Germany, Japan, Singapore, India, Brazil, South Africa. Those vantage points are great for “is this domain reachable from outside” tests (which is how CensoredPlanet works), but they don't tell you what someone inside Iran or China actually sees.

For inside-country measurements, the Voidly Atlas relies on OONI (volunteer-run probes inside countries) and CensoredPlanet Satellite (remote DNS measurement technique that works for ~50 countries). The data we publish IS honest — but the “our 37 probes verify censorship” claim is partially-true at best.

The fix is community probe operators inside censored regions. See /probes for the install path. Anyone with a Raspberry Pi, a VPS, or a spare laptop in one of the gap countries below can directly improve our ability to verify censorship from the inside.

Wanted: probe operators in these countries

High-censorship countries where we have no inside-country probe presence. Hosting a probe here would directly improve our coverage of the events that matter most.

465 incidents in the corpus come from these gap countries — currently verified via OONI volunteer probes + CensoredPlanet remote measurement.

Coverage of top-incident countries

The 10 countries with the most incidents in the Voidly corpus, sorted by incident count. The right column shows whether we have inside-country probe presence in each.

CountryIncidentsProbe
Venezuela VE64external only
Egypt EG55external only
Iran IR55external only
Russia RU53external only
Nigeria NG52external only
India IN50✓ inside
Pakistan PK49external only
TT TT49external only
Azerbaijan AZ46external only
Bangladesh BD42external only

Where we DO have probes (16 active)

DE3840/24h
Frankfurt
78 domains · 98 blocked
US3820/24h
Chicago
78 domains · 98 blocked
SG3800/24h
Singapore
78 domains · 98 blocked
GB3800/24h
London
78 domains · 98 blocked
NL3800/24h
Amsterdam
78 domains · 97 blocked
CA3800/24h
Toronto
78 domains · 96 blocked
ES3800/24h
Madrid
78 domains · 98 blocked
US3800/24h
New York
78 domains · 99 blocked
AU3780/24h
Sydney
78 domains · 97 blocked
JP3760/24h
Tokyo
78 domains · 97 blocked
KR3760/24h
Seoul
78 domains · 96 blocked
BR3760/24h
São Paulo
78 domains · 97 blocked
IN3760/24h
Bangalore
78 domains · 155 blocked
MX3740/24h
Mexico City
78 domains · 95 blocked
ZA3720/24h
Johannesburg
78 domains · 96 blocked
US0/24h
San Jose
0 domains

Host a probe (Pi, VPS, spare laptop)

The probe is a single-purpose process — measures censorship of ~80 domains every 5 minutes and reports to api.voidly.ai/v1/probe/results over HMAC. Runs as a dedicated non-root user, uses pinned TLS, never exposes your location to other probe operators.

Related

  • /probes — Voidly probe network status + install instructions
  • /methodology — full data pipeline including external-source fallbacks
  • /atlas/methods — how blocking is detected (DNS, SNI, TCP RST, etc.)