Is your ISP blocking UDP?

Press the button to find out whether UDP is blocked. If it is, you get ready-made text for your ISP's support with the place where the route breaks.

Turn off your VPN and any bypass tools, otherwise the check measures them, not your ISP. Takes about 10 seconds.
Routes to you in detail

Providers

Status based on node measurements and visitor checks over the last 6 hours. The chart shows the share of measurements where UDP from abroad does not pass. Click a card for a detailed chart, results per server and routes. A provider card appears on its own as soon as a check is made in its network or a node comes online.

Loading…

Journal

When a provider's picture changed: the network appeared in checks for the first time, its status changed, or one of the checks showed blocking where there was none before. Hosting and VPN networks are not shown here.

Loading…

Who is who

YouYou press the button. Your browser sends UDP to our servers and asks whether they received the requests, while the servers trace the route to you.
Node: asksA volunteer's home computer or router. Every 15 minutes it sends packets out on its own and looks at whether replies came back. It checks its own network, where UDP is blocked.
Anchor server: answersA server or VPS with a public IP. It receives packets and answers them, and checks nothing itself. It is the reference point inside the country and abroad.

The installer picks the role itself: a machine with a public IP becomes an anchor server, a home network becomes a node. The verdict “blocked or not” is built from the project's anchor servers. Volunteer servers take part in checks as independent witnesses: they can soften the verdict (“partially blocked”), but cannot accuse a provider on their own. In a country without project servers they serve as the reference point.

Nodes and anchor servers

Project anchor servers

For every visitor and node the reference points are the servers in their own country; all the others count as foreign.

Volunteer anchor servers

Loading…

Nodes

Loading…

Connect your own server or router

One line for Linux and OpenWrt, root or sudo required. The installer picks the role itself: a VPS or server with a public IP becomes an anchor server (open UDP 47321, 47322 and TCP 47321), a home network or router becomes a node (nothing needs to be opened).

Install
(curl -fsSL https://dagart.xyz/en/i 2>/dev/null || wget -qO- https://dagart.xyz/en/i) | sh
More: what the installer does, how to turn off the anchor role, uninstall, Windows

It detects the system, installs Python if needed, downloads the agent and checks its SHA-256, and starts a service as an unprivileged user. It does not touch SSH or other services. It does not change the firewall: if the ports of the anchor role turn out to be closed, it shows which ones and offers to open them, but only with your consent. Before starting it shows the plan and waits 5 seconds (cancel with Ctrl+C). Code: install-node.en.sh. If an anchor server is unreachable from outside (firewall, NAT), it stays inactive until the ports are opened.

Force the “node” role (checks its own network, listens to nothing)
(curl -fsSL https://dagart.xyz/en/i 2>/dev/null || wget -qO- https://dagart.xyz/en/i) | UDPCHECK_ROLE=node sh
Force the “anchor server” role (only answers checks)
(curl -fsSL https://dagart.xyz/en/i 2>/dev/null || wget -qO- https://dagart.xyz/en/i) | UDPCHECK_ROLE=ref sh
Uninstall (service, files, token)
(curl -fsSL https://dagart.xyz/en/i 2>/dev/null || wget -qO- https://dagart.xyz/en/i) | sh -s -- uninstall
Windows (PowerShell, Python 3.7+ required). On macOS the same via curl and python3
iwr https://dagart.xyz/node/udpcheck_node.py -OutFile udpcheck_node.py; python udpcheck_node.py

If a proxy, VPN or tunnel is on the path, the node notices it and such a measurement is not counted.

No anchor in your country? Add a server

For the service to compare “you” with “from abroad”, it needs an anchor server in your country. Until there is one, volunteer servers can play that role.

  1. You need a server or VPS in your country: Linux, public IPv4 (not behind NAT).
  2. Open UDP 47321, 47322 and TCP 47321 in the firewall.
  3. Run the installer line from the “Connect your own server” section: a server with a public IP becomes an anchor on its own. A minute later it appears in the list of volunteer anchor servers.

A volunteer server takes part in checks of visitors and nodes as an independent witness: it can soften the verdict (“partially blocked”) but cannot accuse a provider on its own. Where there are no project servers, it serves as the reference point. The server's IP becomes known to the nodes and to the browsers of the visitors it checks.

What we see and store

  • Your IP is visible for the duration of the request, to build the route and identify the provider. It is not written to the database.
  • We store the provider's network number (ASN), country, approximate city and measurement results, for 60 days.
  • The page creates a random anonymous number in your browser: it is needed only for rate limits and for counting checks. It is not linked to you and does not collect device data. You can delete it by clearing the site data.
  • Public: statistics per provider and the list of nodes (callsign, network, number of measurements). No addresses or cities.
  • A volunteer anchor server: its IP is known to the hub, to the nodes the hub assigned this server to, and to the browsers of the visitors it helps check (up to two such servers per check). The server sees the IPs of nodes and visitors the same way any STUN server on the internet does. Traces to a visitor's address are not passed to it. A home node does not give its IP to anyone.
  • Questions, data deletion, remarks about logos and provider names: draldrean@protonmail.com.
  • This is a test project. Conclusions refer to the servers checked and to the moment of measurement.