How Public DNS Server List Monitors and Updates Its DNS Servers

Public DNS Server List keeps its directory current by continuously monitoring each listed server for online status and responsiveness, then using that monitoring data to calculate the reliability percentage and speed figures shown in the table. The site describes its list as "regularly updated" and its servers as "continuously monitored to ensure they remain online and responsive." In practice, that means the numbers you see in the Reliability and Speed columns are not static labels — they are the output of ongoing checks, and entries that stop responding can be dropped or replaced over time.

What the monitoring actually measures

The site's own description names two things it checks: whether a server is online and whether it is responsive. Those two checks map directly onto the two data columns in the list.

Reliability percentage

The Reliability column (for example, 88.68% for 2610:a1:1018::5 or 98.44% for 5.188.59.211) represents the share of checks in which that server answered. A high figure means the server responded consistently across the monitoring window; a low figure means it was frequently unreachable or timed out.

Speed in milliseconds

The Speed column records response time in milliseconds — the lower the number, the faster the server answered. The spread in the current list is wide and worth understanding before you pick anything:

A server can be fast but unreliable (Cloudflare at 5.5 ms but 68.19%), or slow but very reliable (Selectel at 91.22 ms but 98.44%). The monitoring data is what lets you see that trade-off instead of guessing.

How updates keep the list usable

Because monitoring runs continuously, the list can be refreshed to reflect what is currently reachable. The site states its database spans over 160 countries and includes both IPv4 and IPv6 addresses, and that it is "regularly updated." The practical effect for you:

• Servers that fail checks tend to fall in reliability or disappear from the list.
• Newly available public resolvers can be added as they are discovered.
• The list stays a snapshot of currently working options rather than a historical archive.

This is why the same IP can appear with different reliability or speed values at different times — the figures track recent behavior, not a one-time test.

How to use the monitoring data when choosing

Since the site's job is to monitor and update, your job is to read the output correctly. A few concrete rules:

1. Filter by reliability first if stability matters. For always-on use (home router, office network), start with entries above roughly 90% — e.g. 5.188.59.211 at 98.44% or 76.9.245.205 at 97.22%.
2. Filter by speed first if latency matters. For gaming or real-time browsing, low milliseconds win — 96.7.137.150 at 5 ms or 172.64.36.255 at 5.5 ms — but check the reliability figure before committing.
3. Prefer servers geographically near you. The list includes Country and City columns precisely because a 5 ms server in New York will not be 5 ms from Europe or Asia. Match the location to your own region.
4. Re-check periodically. Because the list is updated, a server that was excellent last month may have dropped. Revisit the table rather than trusting a saved IP indefinitely.
5. Test before you switch. Change your DNS settings, then verify with a real browsing session or a DNS lookup tool. The list's numbers are a starting point, not a guarantee for your specific network.

Common pitfalls

• Treating speed as the only metric. The fastest entries in the list often have the lowest reliability. A 5 ms server that answers only half the time is worse than a 30 ms server that always answers.
• Ignoring IPv4 vs IPv6. The list mixes both. If your device or router only supports IPv4, an IPv6-only entry like 2610:a1:1018::5 will not work for you.
• Assuming the data is live to the second. "Continuously monitored" and "regularly updated" describe an ongoing process, not a real-time feed. Expect the figures to reflect a recent window, not this instant.
• Forgetting that your ISP's routing differs. A server's measured speed on the list is from the monitoring vantage point, which may not match the path your own connection takes.

The short version: the site monitors each server for uptime and response time, converts that into the reliability and speed columns, and refreshes the list so dead or slow entries are replaced. You get a maintained, comparable set of public DNS options — and the best pick depends on whether you weight reliability, speed, or proximity more heavily.