voidly
Solutions

For AI labs

Model shipped.
Can people reach it?

See the difference between a service restriction and a network that gets in the way.

Two questions between a model and its audienceAn illustrative model signal passes through two separate screens: provider availability rules and observed network reach. Both need to be checked; missing measurements remain unknown.
Your model
Provider rules
Network evidence
Two separate layers. One clearer picture.Conceptual illustration

Three things to know
before the next launch.

Inspect the evidence behind a rollout decision.

Bring the signal
into your stack.

Start with public data. Discuss a monitored rollout when you need more.

For your agents

Explore the MCP tools and their documented inputs.

Explore MCP

For your product team

Use the API to inspect a domain and country.

Read the API docs

For a custom rollout

Discuss target networks, filters and additional probes.

Discuss requirements
Sources, scope and reuse

Measurement sources include OONI, CensoredPlanet, IODA and Voidly probes. Citizen Lab provides test-list context. Coverage, recency and confidence vary by source and network.

Voidly-original incidents, scores and annotations are CC BY 4.0. Raw upstream data retains its own license; OONI raw data and Citizen Lab test lists are CC BY-NC-SA 4.0. Dataset licenses do not license application code.

A provider-supported country list describes policy. Network measurements describe observed reachability. One does not establish the other, and missing observations do not establish access.

Try an API example

Inspect the response for chat.openai.com in China. Check its observation time, method and evidence before drawing a conclusion.

Open the accessibility API response
GET /v1/accessibility/check?domain=chat.openai.com&country=CN
Custom monitoring and pilot scope

Contact the team about domain and country filters, signed notifications, custom probe placement and a pilot. Timing, coverage, delivery commitments and pricing depend on the agreed scope.

Bring your next rollout.

Tell us what you need to reach.

Talk to the team
Full referenceRead the AI labs reference

Full ai labs reference

Original reference text retained with its links and context. Historical product, metric and availability statements describe that reference; the current presentation and dated source records above take precedence.

voidly for ai labs·enterprise data feeds·updated 2026-04-25

Know where your model is accessible.Decide your geographic rollout. Get alerted when blocking changes.

Voidly is a network-measurement layer for the modern AI stack. This response includes probe observations from 8 countries. Anthropic, OpenAI, Google DeepMind, Meta AI, Mistral, xAI, DeepSeek, Cohere — the data is identical for all of you. The asymmetry is the story.

01 / The problem AI labs face

Your model launches. A user in Country X can't load it.

You don't know if it's a network issue, an ISP block, or a regulatory move. Your support team writes a generic “sorry, working on it” reply. Your policy team has no data to ground a decision. Your product team has to guess at rollout priorities. Your competitor's service may already be working in that country.

Voidly answers, in one API call, whether your service is accessible from inside that country's network — and how it's being blocked if not.

02 / The matrix (live preview)

AI services × restrictive countries.

Each cell reflects either provider-stated restriction (yellow) or network-confirmed blocking from retrieved probe observations (red). Missing measurements remain unknown.

CountryChatGPTClaudeGeminiMistralDeepSeekMeta AIGrokPerplexity
CNChina
IRIran
RURussia
KPNorth Korea
CUCuba
SYSyria
BYBelarus
VEVenezuela
TRTurkey
AEUAE
PKPakistan
KZKazakhstan
network-blockedprovider-restrictedaccessible (notable)unknown / no dataView full matrix →

03 / The asymmetry data

Your service is not your competitor's service.

Each AI lab has a distinct accessibility footprint. This is the highest-leverage data we publish — every cell here is a commercial decision someone on your team should be able to make. We publish it free; we do not sell it.

Countries blocking or restricting each AI service
Claude
9 countries
9
ChatGPT
8 countries
8
Gemini
7 countries
7
Mistral
6 countries
6
Meta AI
6 countries
6
Grok
6 countries
6
Perplexity
4 countries
4
DeepSeek
0 countries
0
Source: retrieved probe observations from 8 countries plus provider-policy restrictions. Unmeasured access remains unknown.
Anthropic
9
countries blocking or restricting claude.ai

Claude reaches places ChatGPT and Gemini do not — a competitive asymmetry your policy and rollout teams should be tracking week-over-week.

OpenAI
8
countries blocking or restricting chat.openai.com

ChatGPT is the most-searched-for chat assistant globally, and also the most blocked. Network methods, country list, and the exact ASNs blocking you — we have the data.

Google DeepMind
7
countries blocking or restricting gemini.google.com

Gemini is the most-restricted of the major Western chat assistants in our data. The breakdown of provider-restricted vs network-blocked is the conversation worth having.

04 / What we offer

Six things only Voidly does for AI labs.

Monitoring
Real-time accessibility monitoring

Signed webhook fires when your service's status changes in a country we monitor — DNS poisoning, TCP reset, blockpage, TLS interference, or full unreachability. HMAC-SHA256 signed, retry with exponential backoff (2/4/8/16/32 min). Per-country, per-domain, per-method filters.

Diligence
Pre-shipping diligence

Before you launch a new model surface or domain, we test it from 130 countries on demand. Returns accessibility status, observed methods, and any historical incidents involving the domain or related infra. One API call, machine-readable output.

Regulatory
Regulatory mapping

We separate provider-stated restrictions (your own ToS / supported-country list) from network-level blocking (DPI, DNS poisoning, BGP withdrawal). Your policy team gets a clean dashboard of where you have chosen not to ship vs where you are being blocked.

Competitive
Competitive intelligence

How does your service's accessibility compare with peer labs? Side-by-side, country-by-country, method-by-method. The asymmetry is the value — Claude is accessible in places ChatGPT is blocked, and vice versa. We track this longitudinally.

Probes
Custom probe deployment

We already operate 37+ globally distributed nodes. Enterprise customers can request additional probes in target jurisdictions — physical hosting, AS-level placement, or your own VM. Lead time depends on the region, typically 2-6 weeks.

MCP
MCP integration for self-monitoring

Your agents can self-monitor their own service status via @voidly/mcp-server (84 tools, on npm). Use cases: automatically failover to a peer service when blocked; notify support before the user does; gate features by accessibility tier per region.

05 / Concrete use cases

Three scenarios you have right now.

A
Regional rollout verification

You launch your model in a new region. Voidly verifies accessibility from probes physically inside that region — DNS resolution, TCP handshake, TLS, end-to-end loadability of the chat surface. Before your support team learns about a problem from social media.

B
Policy-team compliance answer

Your policy team needs to answer "is our service accessible in country X" for a regulator, a partnership conversation, or a data-export questionnaire. Voidly returns the answer — with citation-grade evidence — in one API call. No vague "we think so."

C
Comparative blocking telemetry

Your release team ships a new model surface (new domain, new subdomain, new region) and wants to know if it gets blocked faster than your standard product. Voidly tracks every domain you point us at, longitudinally, with method-level diagnostics.

06 / Proof

Verifiable now. No paywall on the data.

The whole stack is open before you talk to us. Every claim on this page is measurable from public endpoints.

5+
data sources cross-referenced
130
countries actively monitored
5 min
probe cadence
6 hr
OONI ingest cycle
0.87
F1 ML classifier (honest LOCO)
CC BY 4.0
public API + dataset
Try it yourself · curl
# Is ChatGPT accessible in China?
curl "https://api.voidly.ai/v1/accessibility/check\
?domain=chat.openai.com&country=CN"

# Same for Claude — note the asymmetry
curl "https://api.voidly.ai/v1/accessibility/check\
?domain=claude.ai&country=CN"

# Batch — every major AI service in one call
curl -X POST https://api.voidly.ai/v1/accessibility/batch \
  -H "Content-Type: application/json" \
  -d '{"domains":["chat.openai.com","claude.ai","gemini.google.com",
                  "chat.mistral.ai","x.ai","meta.ai"],
       "country":"RU"}'

07 / Pricing

Enterprise data feeds — schedule a call.

The public API is free, CC BY 4.0, and rate-limited. AI lab feeds are priced per use case — number of monitored domains, alert webhook volume, custom-probe deployments, white-label requirements.

We don't list a sticker price because we haven't commoditized this yet and refuse to overcharge a team whose use case doesn't need the full stack. A 30-min call gets you a fixed quote and a pilot start date.

Most AI-lab pilots start within a week of the discovery call.

08 / By name

We are watching you. Politely.

These are statements of what our public data shows, not endorsements or partnerships. If anything below is wrong, tell us — we will publish a correction with the same prominence.

Anthropic
claude.ai
Claude reaches places ChatGPT and Gemini do not — a competitive asymmetry your policy and rollout teams should be tracking week-over-week.
9 blocked / restricted·0 observed accessible
hello@voidly.ai →
OpenAI
chat.openai.com
ChatGPT is the most-searched-for chat assistant globally, and also the most blocked. Network methods, country list, and the exact ASNs blocking you — we have the data.
8 blocked / restricted·0 observed accessible
hello@voidly.ai →
Google DeepMind
gemini.google.com
Gemini is the most-restricted of the major Western chat assistants in our data. The breakdown of provider-restricted vs network-blocked is the conversation worth having.
7 blocked / restricted·0 observed accessible
hello@voidly.ai →
Mistral AI
chat.mistral.ai
Coverage is sparse for emerging providers — let us add chat.mistral.ai and api.mistral.ai to our priority probe list.
6 blocked / restricted·0 observed accessible
hello@voidly.ai →
xAI
x.ai
Grok inherits some of x.com's blocking pattern in restrictive countries. Want a clean separation of the chat product from the parent network?
6 blocked / restricted·Accessibility unknown
hello@voidly.ai →
Meta AI
meta.ai
meta.ai accessibility tracks differently than facebook.com / whatsapp.com. Where does the AI surface diverge from the social graph? We can show you.
6 blocked / restricted·Accessibility unknown
hello@voidly.ai →
DeepSeek
chat.deepseek.com
A China-origin chat product has an inverse blocking footprint — accessible where Western providers are not. That asymmetry is a story worth telling.
0 blocked / restricted·1 observed accessible
hello@voidly.ai →

09 / Talk to us

Pilot in a week. Production in two.

One email gets you a 30-min discovery call, a sandbox API key, and sample integration code (LangChain, CrewAI, raw HTTP, your stack).