Atlas
A public dataset of citable internet-censorship incidents, each backed by evidence permalinks to the upstream measurement networks.
Read more →Voidly / research
Open measurements. Documented methods. Evidence you can inspect and cite.
Country scores, incident records and evidence sources, each with its own timestamp.
Open the report ↗Historical study / 25 Apr 2026A dated five-domain study. Full evidence, uneven coverage and source discrepancies included.
Read the April study ↗Methods & accountabilityCompare targets, evaluation splits and limits before using a forecast.
Inspect the registry ↗For builders
Read the public API or review the MCP setup. Copying a reference example does not execute it.
The incident ID is illustrative. Use a real identifier from the incident browser. This example is copied as text; it is not executed.
The original observatory documentation, reorganized for reading. Historical descriptions, current source responses and model evaluations are explicitly separated.
No source note supplied.
Source figures are checked once per minute while this page is open. Missing or legacy statistics remain unavailable. Probe and model counts are linked to their own source pages, not guessed from another response.
Voidly exists to make internet censorship measurable for people who are not network engineers. Voidly does this by aggregating existing measurement networks — OONI[1], IODA[2], and CensoredPlanet[3] — into a single citable evidence database, then publishing the resulting incidents, country rankings, and forecasts under CC BY 4.0.
The intended audience is, in priority order: researchers and journalists who need permanent citations for stories about shutdowns and platform blocks; AI-agent and developer-tooling teams who need a free machine-readable feed; and end-users in censored regions who want a real-time picture of what is being blocked. This reference concerns the research observatory; VPN setup is documented separately at /vpn/guide.
The full operating context, governance, and disclosures are on the about page; the data pipeline is documented in the methodology.
The evidence database combines upstream measurement networks, Voidly probes and URL-test-list context. The table preserves the documented source roles and cadences; a schedule is not a fresh health check, and not every historical incident has linked evidence.
| Source | Type | Evidence rows | Documented cadence | License |
|---|---|---|---|---|
| OONI[1] | Active probes (8 test types) | 239,871 | every 6 h | Upstream terms; see /data |
| IODA[2] | BGP + Telescope outage detection | 35,972 | every 6 h | CC BY 4.0 |
| CensoredPlanet[3] | Remote DNS + HTTP/HTTPS | 43,426 | daily | CC BY 4.0 |
| Voidly probes[4] | Active TCP/DNS/HTTP; consult the linked current roster | 223,704 | every 5 min | CC BY 4.0 |
| Voidly community[4] | Volunteer-operated probe nodes | 43,265 | every 5 min | CC BY 4.0 |
| Citizen Lab[12] | URL test lists (domain categories) | Unavailable | static | CC BY-NC-SA 4.0 |
| Total evidence | 586,238 | 80,851 last 7 d |
Source roles and documented cadences are reference information. Voidly-original outputs use CC BY 4.0; upstream measurements and Citizen Lab test lists retain their own terms. See source-specific licenses. Figures above come only from the identified incident-statistics response; a missing source count is unavailable.
Each upstream measurement is normalized to a common evidence row, classified by a Gradient Boosting model, and grouped into a citable incident. Every transformation is documented and reproducible.
The pipeline runs every six hours. Raw measurements are deduplicated, geocoded to the country and ASN level, and joined against the Citizen Lab URL test list[12] for content category. A Gradient Boosting classifier (LOCO mean F1 0.71; 0.90 (v3.3 stratified) AUC on a separate stratified 5-fold evaluation[8]) tags likely censorship, and high-confidence rows are clustered into citable incidents with a permanent human-readable ID like IR-2026-0142.
The original reference describes Sentinel as XGBoost with isotonic calibration, scheduled daily at 02:00 UTC, with a seven-day target. Its historical stratified and leave-country-out evaluations do not establish within-country day-timing skill. The legacy target_7day forward AUC was 0.589 versus 0.957 for predict-yesterday, and onset-row AUC was about 0.33. The distinct honest_forecast_v1 event model has its own target and evaluation; do not transfer these scores to it.[9] Read the current model registryand Atlas forecast for their separate source states.
public/ooni-data.json). It updates on rebuild, not in real time.Full methodology, validation matrix, confidence intervals, and limitations: /methodology.
This source refreshes with the other reads once per minute. Observation time is distinct from publication, creation or response time.
No source note supplied.
2026-09-19T04:55:00Z · disruption · active
2026-09-19T03:40:00Z · disruption · active
2026-09-19T03:30:00Z · disruption · active
2026-09-19T03:20:00Z · disruption · active
2026-09-19T03:20:00Z · disruption · active
The following definitions are preserved from the old research reference. They are not current release or capability checks. Follow each product page for its current scope; research-output licensing does not relicense application code or commercial services.
A public dataset of citable internet-censorship incidents, each backed by evidence permalinks to the upstream measurement networks.
Read more →A daily 7-day shutdown forecast for high-risk countries with conformal-calibrated intervals and SHAP-explained drivers.
Read more →An end-to-end encrypted agent-to-agent messaging network using Double Ratchet plus ML-KEM-768 post-quantum hybrid key exchange.
Read more →One encrypted zero-value sealed-echo task with a pinned provider, one dispatch, signed sealed result, and status-only recovery. No wallet or payment route.
Read more →The dataset is meant to be queried, not just downloaded. Public read endpoints work without auth; ML-prediction and writeable agent endpoints take a free key.
Preserved reference example, not executed here. The sample incident ID is illustrative; latest is a mutable package tag. Read current API authentication and source-specific licensing before use.
Preserved reference example, not executed here. The sample incident ID is illustrative; latest is a mutable package tag. Read current API authentication and source-specific licensing before use.
Examples are preserved reference text, not executed requests. The illustrative incident ID may not identify an extant record; use a real ID from the incident browser. Verify-claim and other write/prediction routes may require credentials; check the current API reference. No clipboard action runs these commands.
Voidly-original research output is published under CC BY 4.0 with attribution. Upstream data retains its own source-specific terms; see /data. Permanent incident IDs (e.g. IR-2026-0142) are stable across versions.
Voidly Research is the canonical author. The example below generates a BibTeX entry for the network as a whole; for an individual incident, use /api/incidents/<ID>/report?format=bibtex in the old reference. The current incident page links the API path below; use a real incident identifier and retain the source dates.
The current source route is https://api.voidly.ai/data/incidents/<ID>/report?format=bibtex. See the incident browser and citation guide.
Need a press kit, headshot, or signed PGP attestation of a specific number? Press kit and facts sheet.
License: CC BY 4.0. Data and code are on GitHub for independent replication.
Voidly does not duplicate these projects — it builds on top of them. Voidly credits its upstreams and links to comparable research orgs and standards bodies that journalists may want to triangulate against.
public/ooni-data.json, regenerated on every site rebuild from the most recent six-hour OONI ingest. @voidly/mcp-server. npmjs.com. Reference URLs and original technical context are retained. No new accessed-on date is assigned to references that were not fetched during this page view. Product history, cadences and training figures are not current deployment checks.
Source networks, standards and distribution references from the original page. A reference link is not a partnership, endorsement or current compliance check.
Agent-to-agent protocol reference. The original page cited v0.3.0.
Original distribution reference: voidly-ai/mcp-server.
Publisher dataset/profile destination. Counts vary over time.
Package organization. Review the individual release.
Current product scope; old staging text remains historical context.
Separate project, not the Voidly observatory.
The original infobox identifies Voidly as an open-data and encrypted-communications observatory, founded in 2024. It lists a five-minute probe cadence and six-hour ingest cadence, along with voidly.ai, api.voidly.ai, @voidly/mcp-server and /atom.xml. These are source descriptions, not a current operational check.
The observatory is distinct from Void Linux and Voidly Bio (cosmetics). The original page's messenger, agent and email destinations remain available: Messenger, agent infrastructure and Voidmail. Governance and disclosures remain at About.
The old reference calls Pay a hosted amount-zero staging session, while older disambiguation text calls it a settlement rail. Those descriptions are inconsistent and are not used as a present product claim here. Read current Pay and the isolated historical audit. The original staging configuration link is retained as historical reference, not a required onboarding action.
Cite the reference
This page's canonical URL is /research. The original network-as-a-whole citation remains in section 07. Keep upstream licenses, source dates and limitations with reused material.