Abstract pattern of interconnected red and black data lines suggesting network traffic on a dark background

Net Neutrality Monitor analyses how Internet Service Providers resolve, block and inject DNS traffic. The platform tracks servers under examination, surfaces country-level reports, and publishes a live blacklist of injected addresses.

View Country Reports
Continuous DNS probing across participating ISPs
Country-level neutrality scoring and breakdowns
Blacklist of injected addresses from probe data
Community-driven via forum, IRC and wiki

What the platform does

Net Neutrality Monitor provides real-time analysis of the censorship systems used by Internet Service Providers. It tracks DNS servers currently under examination, lists known DNS servers that respond correctly to specific tests, and produces country reports on the types of blocking detected — from gambling and file-sharing to streaming and image hosting.

  • DNS probes
  • Country reports
  • Injected addresses
  • ISP scoring
About the Project
Minimal line drawing of a server rack and connecting cables on a white background

Coverage across the monitored regions

Country reports are available for China, Colombia, Denmark, Estonia, Finland, Italy, Korea Republic of, Sweden, Switzerland, Thailand, Turkey and additional regions as new probes are activated.

  • 11+Countries with published reports
  • LiveDNS server list under examination
  • CC BY 2.5 IT / BY-SA 3.0Content licensing applied
  • OpenDonations and probe submissions
Browse DNS List
Monitored since 2010 Geo data · ipinfodb

Why we encourage probes from underrepresented regions like South America

Net Neutrality Monitor tracks and analyses Internet censorship and filtering by Internet service providers and DNS servers. It gathers country-level results and publishes blacklist, probe, DNS and statistical data so patterns can be compared rather than inferred from one failed request. Its purpose is practical observation: identifying where a particular hostname or IP address can be reached and where it cannot.

A probe is valuable because filtering is rarely uniform. An address may work on one broadband connection, fail through a mobile network and return a different error when checked against a particular resolver. Measurements from several locations and access types provide a clearer picture of these differences, while also helping distinguish deliberate blocking from outages, configuration errors or routing problems.

The need for broader coverage is especially strong where fewer volunteers and monitoring nodes exist. This is why we encourage probes from underrepresented regions like South America: local evidence can reveal restrictions that would otherwise remain invisible in global datasets. The service is currently a beta, volunteer-supported project developed and powered by AirVPN, and its findings should be treated as indicative research rather than a definitive national index.

Seeing censorship through a local lens

Filtering is local even when the service being accessed is global. ISPs apply network policies, DNS operators maintain their own resolver systems, and mobile operators route traffic through infrastructure that may differ substantially from fixed broadband. A restriction imposed in one market or city should not automatically be attributed to an entire country or continent.

South America is particularly diverse in this respect. São Paulo, Bogotá, Buenos Aires, Lima and Santiago each have different combinations of fixed-line providers, mobile networks and interconnection arrangements. Networks serving metropolitan communities may behave differently from those used in smaller cities, rural districts or areas where fixed broadband remains limited. Population size alone cannot capture those variations.

Community participation is therefore part of the measurement process, not an optional addition. Local volunteers understand which operators serve their area, when restrictions appear and which services matter to them. Reciprocal outreach through organisations such as We Are Girl Force can help technical projects remain connected to affected communities while ensuring that data collection addresses locally relevant conditions.

Why South America needs more probes

Global monitoring datasets often reflect where participants and technical resources are concentrated. That can leave entire countries without observations, or make a country appear healthier or freer because only its major service providers were tested. The absence of reported blocks is not proof that blocking is absent when no suitable probes have been run.

A single urban probe also has limits. It may represent one ISP, one DNS resolver and one period of the day without revealing how conditions change elsewhere. Coverage becomes more informative when volunteers test several cities, both fixed and mobile connections, and networks operated by smaller regional providers. Each additional vantage point helps separate a local network decision from a broader trend.

Connection type deserves particular attention. A guide to network comparison tests shows how mobile and fixed broadband checks can expose different filtering behaviour. The same approach is valuable in cities where customers can switch between an NBN-style fixed service, a domestic mobile plan and a tethered hotspot without changing the target being tested.

What networks and resolvers reveal

A probe records an outcome reached through a particular combination of client, ISP, router, resolver and destination. It does not describe every possible route to a website. DNS resolution may succeed while the subsequent connection is blocked, or the address may fail to resolve even though the web server remains available through a different resolver. Recording the stage of failure is essential for interpreting the result correctly.

DNS servers also complicate attribution. Blocking can occur at an ISP’s recursive resolver, within an intermediate network or at the point where traffic leaves the country. Encrypted DNS may change the observable path, while cached answers may briefly preserve access after a policy change. Probe records therefore need supporting context such as resolver configuration, transport type, timing and the access network used.

For Australian readers, several familiar details illustrate the same issue. Sydney, Melbourne, Brisbane and Perth have different fixed-line traffic paths, while the National Broadband Network combines fibre-to-the-premises, fibre-to-the-node, hybrid fibre-coax and fixed-wireless technologies. Retail services from Telstra, Optus, Vodafone and specialist providers such as iiNet or Aussie Broadband may still produce different observations. Mobile plans use separate radio and backhaul infrastructure, and Australian .au or .com.au domains can be resolved through materially different routes from international domains.

What a useful regional probe contributes

Regional volunteers can place measurement points where central datasets have little visibility. Their observations are most useful when the target, connection and surrounding context are recorded consistently.

Locations and access types worth covering

  • Fixed broadband in major South American cities
  • Mobile-only connections outside dense urban areas
  • Smaller regional ISPs and municipal networks
  • Public Wi-Fi used by schools, libraries and small businesses

Evidence to capture with each observation

  • City, operator, access type and timestamp
  • DNS resolver and any encrypted-DNS setting
  • Target hostname or IP address and failure stage
  • Status, error response and relevant routing details

Participants can submit a target as a URL or IP address for monitoring. Submissions should use addresses that are appropriate to test and should avoid collecting unrelated personal information. Local context can be added through existing probe records, helping the project distinguish an isolated incident from repeated filtering without asking volunteers to publish identifying details.

A practical next measurement cycle

A credible regional campaign requires comparable tests rather than a large but inconsistent collection of results. Each location should use the same target set, document fixed and mobile access separately, and include both major operators and smaller providers where possible. Australian measurements from Sydney, Melbourne or Brisbane can provide a useful reference, but they should complement rather than substitute for evidence gathered inside South America.

The beta status and volunteer-supported nature of Net Neutrality Monitor make transparency essential. Results should retain uncertainty, identify the network context and avoid converting isolated observations into broad claims about an entire population. Independent observations and careful metadata can strengthen the dataset while preserving the distinction between research findings and authoritative national assessments.

The concrete next step is to run a matched pair of fixed-broadband and mobile probes in one underrepresented South American city, record the operator, resolver and time, and submit the observations alongside an equivalent pair from an Australian city.

Transparent, analytical, community-run

The platform documents how ISPs handle neutrality on the wire, with method notes, country breakdowns and a public blacklist of injected addresses. — Project methodology
Minimal line drawing of a person silhouette with a speech bubble on neutral background

Country reports at a glance

Snapshots from the published country reports. Open a tile to view the full regional analysis on the Reports page.

Minimal line drawing of Italy outline in red on white Minimal line drawing of Denmark outline in red on white Minimal line drawing of Switzerland outline in red on white Minimal line drawing of Thailand outline in red on white Minimal line drawing of Turkey outline in red on white Minimal line drawing of Malaysia outline in red on white Minimal line drawing of Belgium outline in red on white

Follow new probes, blacklist updates and country reports as they are published.

Subscribe