anyns.io.

Authoritative DNS Latency

A fixed vantage point queries each authoritative DNS provider directly on a schedule and records round-trip time and whether an answer came back. The numbers are measured from that location and describe only that place and time; rows are sorted by 24-hour median, click a row to see each address.

Chengdu · Tencent Cloudlast 24 h · 26 rounds · latest round 09-29 02:30 UTC+8
ProviderAnsweredMedianP90Latest
Huawei Cloud DNS InternationalSOA of huaweicloud-dns.com97.5%33 ms36 ms34 ms
NS hostAddressAnsweredMedianP90Latest
ns1.huaweicloud-dns.net159.138.112.11192.3%314 ms607 ms630 ms
ns1.huaweicloud-dns.net159.138.160.10799.2%323 ms334 ms336 ms
ns1.huaweicloud-dns.net159.138.17.11298.5%189 ms194 ms191 ms
ns1.huaweicloud-dns.net159.138.208.388.5%368 ms372 mstimeout
ns1.huaweicloud-dns.org159.138.112.11192.3%315 ms603 ms624 ms
ns1.huaweicloud-dns.org159.138.160.10797.7%328 ms339 ms315 ms
ns1.huaweicloud-dns.org159.138.17.18799.2%188 ms195 ms193 ms
ns1.huaweicloud-dns.org159.138.208.389.2%369 ms379 ms430 ms
ns1.huaweicloud-dns.com114.115.192.11100%37 ms39 ms40 ms
ns1.huaweicloud-dns.com116.205.223.128100%34 ms37 ms37 ms
ns1.huaweicloud-dns.com116.205.5.31100%49 ms52 ms50 ms
ns1.huaweicloud-dns.com122.112.208.253100%37 ms39 ms37 ms
ns1.huaweicloud-dns.cn113.45.105.30100%35 ms38 ms34 ms
ns1.huaweicloud-dns.cn114.115.192.11100%37 ms39 ms36 ms
ns1.huaweicloud-dns.cn116.205.223.129100%34 ms37 ms34 ms
ns1.huaweicloud-dns.cn116.205.5.32100%48 ms51 ms51 ms
ns1.huaweicloud-dns.net2407:c080:20:ffff:ffff:fffe:0:1100%36 ms39 ms35 ms
ns1.huaweicloud-dns.org2407:c080:20:ffff:ffff:fffe:0:1100%36 ms39 ms36 ms
ns1.huaweicloud-dns.com2407:c080:20:ffff:ffff:fffe:0:1100%36 ms39 ms34 ms
ns1.huaweicloud-dns.cn2407:c080:20:ffff:ffff:fffe:0:1100%36 ms39 ms36 ms
Alibaba Cloud DNS International (free plan)SOA of alibabacloud.com100%35 ms36 ms35 ms
NS hostAddressAnsweredMedianP90Latest
ns7.alidns.com39.96.153.47100%43 ms44 ms43 ms
ns7.alidns.com39.96.153.57100%43 ms44 ms44 ms
ns7.alidns.com47.118.199.207100%47 ms49 ms49 ms
ns7.alidns.com47.118.199.217100%41 ms48 ms48 ms
ns8.alidns.com39.96.153.48100%43 ms45 ms42 ms
ns8.alidns.com39.96.153.58100%43 ms45 ms43 ms
ns8.alidns.com47.118.199.208100%47 ms49 ms40 ms
ns8.alidns.com47.118.199.218100%49 ms49 ms49 ms
ns7.alidns.com2408:4009:501::3100%36 ms39 ms39 ms
ns8.alidns.com2408:4009:501::4100%36 ms38 ms35 ms
DNSPod InternationalSOA of dnspod.com96.7%35 ms36 ms37 ms
NS hostAddressAnsweredMedianP90Latest
a.dnspod.com101.227.168.75100%36 ms37 ms37 ms
a.dnspod.com117.135.128.175100%36 ms37 ms37 ms
a.dnspod.com43.130.172.7596.4%258 ms265 ms255 ms
a.dnspod.com43.134.249.7487.3%123 ms125 ms91 ms
b.dnspod.com163.177.5.79100%37 ms37 ms37 ms
b.dnspod.com220.196.136.75100%36 ms37 ms37 ms
b.dnspod.com43.161.3.75100%75 ms82 ms69 ms
c.dnspod.com112.80.181.175100%41 ms42 ms42 ms
c.dnspod.com125.94.59.175100%37 ms38 ms37 ms
c.dnspod.com43.134.249.7583.6%123 ms126 ms93 ms
anynsSOA of anyns.io100%38 ms41 ms41 ms
NS hostAddressAnsweredMedianP90Latest
ns1.anyns.io23.141.4.164100%38 ms41 ms41 ms
ns2.anyns.io54.169.167.45100%78 ms83 ms74 ms
CloudflareSOA of cloudflare.com99.9%74 ms94 ms73 ms
NS hostAddressAnsweredMedianP90Latest
ns3.cloudflare.com162.159.0.33100%80 ms174 ms82 ms
ns3.cloudflare.com162.159.7.226100%82 ms203 ms75 ms
ns4.cloudflare.com162.159.1.33100%82 ms201 ms78 ms
ns4.cloudflare.com162.159.8.55100%83 ms141 ms73 ms
ns3.cloudflare.com2400:cb00:2049:1::a29f:21100%82 ms209 ms79 ms
ns3.cloudflare.com2400:cb00:2049:1::a29f:7e2100%80 ms186 ms79 ms
ns4.cloudflare.com2400:cb00:2049:1::a29f:12199.2%83 ms188 ms76 ms
ns4.cloudflare.com2400:cb00:2049:1::a29f:837100%85 ms202 ms83 ms
Amazon Route 53SOA of awsdns-00.com98.5%75 ms80 ms76 ms
NS hostAddressAnsweredMedianP90Latest
g-ns-1.awsdns-00.com205.251.192.199.2%181 ms185 ms182 ms
g-ns-576.awsdns-00.com205.251.194.64100%79 ms87 ms76 ms
g-ns-1.awsdns-00.com2600:9000:5300:100::194.6%194 ms198 ms191 ms
g-ns-576.awsdns-00.com2600:9000:5302:4000::1100%77 ms83 ms83 ms
Hurricane Electric (free)SOA of he.net98.5%176 ms178 ms178 ms
NS hostAddressAnsweredMedianP90Latest
ns1.he.net216.218.130.299.2%179 ms183 ms178 ms
ns2.he.net216.218.131.296.9%180 ms189 ms180 ms
ns3.he.net216.218.132.2100%181 ms186 ms180 ms
ns4.he.net216.66.1.299.2%181 ms187 ms178 ms
ns5.he.net216.66.80.1899.2%182 ms186 ms181 ms
ns1.he.net2001:470:100::296.9%181 ms187 ms182 ms
ns2.he.net2001:470:200::297.7%179 ms185 ms181 ms
ns3.he.net2001:470:300::299.2%179 ms185 ms183 ms
ns4.he.net2001:470:400::298.5%180 ms185 ms180 ms
ns5.he.net2001:470:500::298.5%180 ms186 ms178 ms
Bunny DNSSOA of bunny.net92.9%191 ms199 ms187 ms
NS hostAddressAnsweredMedianP90Latest
kiki.bunny.net91.200.176.183.1%191 ms201 ms187 ms
coco.bunny.net109.104.147.198.5%248 ms260 ms257 ms
kiki.bunny.net2400:52e0:fff0::190.8%201 ms206 ms197 ms
coco.bunny.net2400:52e0:fff2::199.2%241 ms258 ms225 ms
ClouDNS (free plan, unicast)SOA of who.sb87.1%231 ms235 ms231 ms
NS hostAddressAnsweredMedianP90Latest
ns71.cloudns.net109.201.133.25198.5%238 ms252 ms243 ms
ns72.cloudns.com178.156.179.11859.2%249 ms253 ms250 ms
ns73.cloudns.net51.91.57.24494.6%234 ms244 ms231 ms
ns74.cloudns.uk185.206.180.5596.9%269 ms278 ms269 ms
ns71.cloudns.net2a00:1768:1001:9::25199.2%240 ms254 ms281 ms
ns72.cloudns.com2a01:4ff:f0:6e7b::156.9%249 ms273 ms253 ms
ns73.cloudns.net2001:41d0:305:2100::596194.6%240 ms244 ms231 ms
ns74.cloudns.uk2a0b:1640:1:1:1:1:1ce8:344696.9%274 ms282 ms273 ms
Method
  • Each NS address gets an SOA query with recursion disabled. Only a NOERROR answer counts as success; no answer counts as a timeout; an answer with any other code is recorded as refused, treated as a broken target and left out of the answered rate.
  • One round every 5 minutes; each address gets 5 queries per round, 60 ms apart, 2 s wait each; the median is that address's round-trip for the round.
  • A provider row uses the fastest of its addresses in each round (recursive resolvers tend to pick the fastest address too). Median and P90 are computed over the rounds of the last 24 hours; answered rate = NOERROR answers ÷ queries sent.
  • NS host names are resolved through public resolvers commonly used in the vantage point's region, so the addresses are what users there actually get; at most 4 addresses per name and address family are measured.
  • Every query targets a zone the provider actually hosts (expand a row to see it); for ClouDNS it is who.sb, created on its free plan.
  • Each round also checks two baseline targets; when both go largely unanswered, the whole round is treated as a vantage-point fault and excluded.

Machine-readable (JSON, verify it yourself): /api/anyns/speed