Higher latency ping from New York City!


#1


I’m in Mahattan, NYC, and the ping to 1.1.1.1 averages 16ms.
However, pings to 8.8.8.8 or 9.9.9.9 or OpenDns’s 208.67.222.222 average 11 ms.
Also, using https://www.dnsleaktest.com/ and an IP checker, I see that the server for 1.1.1.1 is in Boston.
So, 1.1.1.1 is NOT faster for me, and apparently cloudflare does not have a server in NYC.
Cloudflare, please advise.


#2

There’s one in Newark, which should be pretty close to you. You can double check with:
dig @1.1.1.1 id.server ch txt

For more help, do a traceroute to 1.1.1.1 and post the results here (hide your origin IP if you prefer).


#3

sdayman - how can I run your command? It doesn’t run in cmd or powershell.

Here are the tracert results, from a .bat file I wrote that runs FIVE tracerts…
The results to 1.1.1.1 and 1.0.0.1 and to two IPs for Cloudflare that were showing in my https://www.dnsleaktest.com/ are to Boston.
However, the result to “cloudfare.com” is to NY.
Unfortunately, only the results to 1.1.1.1 and 1.0.0.1 are relevant here, and Boston means that this service is 50% slower than 8.8.8.8. and 9.9.9.9 and OpenDNS.


The current date is: Sat 04/07/2018
Enter the new date: (mm-dd-yy) The current time is: 18:41:00.34
Enter the new time:
1.1.1.1

Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 8 ms 8 ms 10.32.183.1
3 12 ms 11 ms 11 ms G0-5-5-7.NYCMNY-LCR-21.verizon-gni.net [130.81.193.72]
4 * * * Request timed out.
5 11 ms 11 ms 11 ms 0.ae6.BR1.NYC1.ALTER.NET [140.222.228.131]
6 12 ms 10 ms 10 ms ae13.cr0-nyc2.ip4.gtt.net [173.205.47.145]
7 16 ms 17 ms 15 ms xe-7-2-2.bos10.ip4.gtt.net [89.149.136.90]
8 15 ms 15 ms 15 ms cloudflare-gw.cr0-bos1.ip4.gtt.net [69.174.23.10]
9 15 ms 15 ms 15 ms 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1]

Trace complete.

1.0.0.1

Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.0.0.1]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 8 ms 10.32.183.1
3 28 ms 26 ms 13 ms G0-5-5-7.NYCMNY-LCR-21.verizon-gni.net [130.81.193.72]
4 * * * Request timed out.
5 11 ms 11 ms 11 ms 0.ae6.BR1.NYC1.ALTER.NET [140.222.228.131]
6 12 ms 10 ms 10 ms ae13.cr0-nyc2.ip4.gtt.net [173.205.47.145]
7 15 ms 16 ms 15 ms xe-7-2-2.bos10.ip4.gtt.net [89.149.136.90]
8 15 ms 15 ms 15 ms cloudflare-gw.cr0-bos1.ip4.gtt.net [69.174.23.10]
9 16 ms 15 ms 16 ms 1dot1dot1dot1.cloudflare-dns.com [1.0.0.1]

Trace complete.

172.68.53.47 CF Boston

Tracing route to 172.68.53.47 over a maximum of 30 hops

1 1 ms <1 ms 1 ms 192.168.1.1
2 9 ms 8 ms 8 ms 10.32.183.1
3 10 ms 11 ms 11 ms G0-1-2-5.NYCMNY-LCR-21.verizon-gni.net [130.81.174.52]
4 * * * Request timed out.
5 12 ms 11 ms 11 ms 0.ae6.BR1.NYC1.ALTER.NET [140.222.228.131]
6 11 ms 10 ms 11 ms ae13.cr0-nyc2.ip4.gtt.net [173.205.47.145]
7 15 ms 15 ms 15 ms xe-7-2-2.bos10.ip4.gtt.net [89.149.136.90]
8 15 ms 17 ms 15 ms cloudflare-gw.cr0-bos1.ip4.gtt.net [69.174.23.10]
9 17 ms 16 ms 16 ms 172.68.53.47

Trace complete.

172.68.53.180 CF Boston 2

Tracing route to 172.68.53.180 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 8 ms 10.32.183.1
3 13 ms 11 ms 11 ms G0-1-2-5.NYCMNY-LCR-21.verizon-gni.net [130.81.174.52]
4 * * * Request timed out.
5 12 ms 11 ms 11 ms 0.ae6.BR1.NYC1.ALTER.NET [140.222.228.131]
6 11 ms 11 ms 12 ms ae13.cr0-nyc2.ip4.gtt.net [173.205.47.145]
7 15 ms 16 ms 17 ms xe-7-2-2.bos10.ip4.gtt.net [89.149.136.90]
8 16 ms 16 ms 15 ms cloudflare-gw.cr0-bos1.ip4.gtt.net [69.174.23.10]
9 16 ms 16 ms 16 ms 172.68.53.180

Trace complete.

cloudflare

Tracing route to www.cloudflare.com [198.41.215.162]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 8 ms 10.32.183.1
3 10 ms 11 ms 11 ms G0-5-5-7.NYCMNY-LCR-21.verizon-gni.net [130.81.193.72]
4 * * * Request timed out.
5 12 ms 10 ms 11 ms 0.ae6.BR1.NYC1.ALTER.NET [140.222.228.131]
6 13 ms 11 ms 10 ms ae13.cr0-nyc2.ip4.gtt.net [173.205.47.145]
7 11 ms 11 ms 11 ms xe-8-2-1.cr0-nyc4.ip4.gtt.net [89.149.181.186]
8 11 ms 10 ms 10 ms cloudflare-gw.cr0-nyc4.ip4.gtt.net [69.174.23.54]
9 11 ms 17 ms 11 ms 198.41.215.162

Trace complete.

Please advise, and thanks.


#4

For what it’s worth, Google Public DNS has a multi-level architecture. They do some caching in NYC, but many queries – if not most – are forwarded to North Carolina. Average DNS resolution time is likely not much faster than Cloudflare BOS.


#5

:diamonds:
ALL - Just now, running SImpleDNSCrypt in the background and going to www.dnsleaktest.com, one of the three DNS servers is 172.68.53.71 Cloudflare, but again when I check its IP I see it is located in Boston.

With respect, how can Cloudflare assure fastest response to users in NYC if it lacks a server in NYC?

To mnordhoff - understood about 8.8.8.8 but before I started trying 1.1.1.1 two days ago, I was using only OpenDNS at 208.67.222.222, and it is always fast. I shall return to it or try 9.9.9.9 unless Cloudflare advises of a way to make its DNS responses faster. The goal is to get BOTH security AND speed.

Thanks.
:spades:


#6

They do have an NYC-area PoP. Your packets are just going farther away for some reason. :slightly_frowning_face:


#7

mnordhoff – Many years ago, when I first tried OpenDNS and ran some tests, I saw the same issue - my queries were going to a server far from NYC.
But when I asked them about it, they checked and from then on my queries go to their server in NYC.
Could you send a note to CF to check as well? (I’m not a tech person.)
Thanks.


#8

You are in a CF forum, they will be reading this on Monday and will contact the appropriate ISPs to fix routing issues (it’s actually not CF’s fault in this case).


#9

matteo - great. And on my other PC without SimpleDNSCrypt, the same thing continues - pings to 1.1.1.1 are slower than to the others, and tracert to 1.1.1.1 goes to Boston.
(And www.dnsleaktest.com shows ONLY cloudflare, as it should.)


#10
       ,

I just tried the same tracert tests from a completely different location in NYC - my office.
Same thing - 8.8.8.8 and 9.9.9.9 and 208.67.222.222 are all staying in NYC with low final ping times (approx 3 - 4 ms), but 1.1.1.1 goes to Boston (the URLs say :“bos”) with a longer ping time - 8ms, which is 100% more relatively.

So it’s not just my home location.
.


#11

Will reply to both messages together. Well a different PC on the same LAN won’t change anything. Are the ISPs different between your home and office?


#12

If you do digs against them for the domain of your choice it is probably a better measure than ping.

dig cnn.com @1.1.1.1
dig cnn.com @8.8.8.8


#13

matteo - NOT on the same LAN. Home and office are 2/3 mile apart.
Home is currently Verizon DSL with download limited to 7Mbps. The CO is on West 73rd Street.
Office is commercial Verizon high-speed of some type - not sure whether or not FIOS - with download limited to 100 Mbps. Don’t know where the CO is, but it’s probably not the same.
That’s why the total ping times are much lower across the board in the office. But 1.1.1.1 is still Boston with longer ping times - not in NYC.


#14

cscharff - I figured out that dig is a Linux or Unix command, and I have neither. I’m not a tech person, unlike many of the knowledgeable posters here (including yourself).


#15

The Windows alternative to dig is this (the step-by-step is better seen if you click through):

From what you wrote here it seems you tried both your office AND a second in your home (but changes nothing).

The thing is that this is the same ISP (Verizon), so the routing is most likely the same. You would have to try a different ISP to check. Even the tracert to www.cloudflare.com goes through many hops, so probably, for some strange reason, 1.1.1.1 for them is closer in BOS than in NYC.


#16

matteo - OK - you got me thinking.

I have now linked in to a third location - my wife’s mini-office (also 2/3 mile from my home) which she rents from a mini-office company. They provide a fast internet connection, and their ISP seems to be Level 3 Communications in NYC…

On the PC in her mini-office, tracert to 1.1.1.1 is 2 - 3 ms and just as fast as to 8.8.8.8. This time, tracert to 9.9.9.9 is much slower.

The tracert to 1.1.1.1 is staying in NYC - it is not going to Boston. (The next-to-last line is “cloudflare-ic-301663-nyk-b2.c.telia.net [213.248.77.162]”)

So — can cloudflare ask Verizon (my home and office ISP) to make sure that connections from NYC to 1.1.1.1 stay in NYC and don’t go to Boston?

I don’t think we have to do more in the way of nslookup. Clearly, Verizon as ISP (my home and my office) is forcing connections to 1.1.1.1 to go to Boston. Level 3 (my wife’s office ISP) is not doing this.


#17

I assume that @cscharff will open an internal ticket with the networking team.

This is the conundrum of networking latency. I would assume they would love to have trace routes from all 3 location and, maybe, to at least 8.8.8.8 so they can understand exactly where the problem occurs and which path it takes.


#18

matteo - I have now run the same tracert bat as I first posted above, but this time I have done it at my wife’s mini-office that has Level 3 communications as ISP.

What’s important are the tracerts to 1.1.1.1 and 1.0.0.1. (Please don’t get distracted by the tracerts to 172.68.53.47 and 172.68.53.180, which must go to Boston - they are not relevant. I just had them in the .bat for reference purposes. Also, “dslrouter” is not connected to DSL - in my wife’s mini-office, I set an old leftover DSL router to bridge mode - there is no DSL.)

Here it is -



The current date is: Sun 04/08/2018
Enter the new date: (mm-dd-yy) The current time is: 13:40:10.87
Enter the new time:

1.1.1.1

Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms dslrouter.westell.com [192.168.0.1]
2 1 ms 1 ms 1 ms 10.120.137.17
3 1 ms 1 ms 1 ms 8.31.244.73
4 * * * Request timed out.
5 2 ms 2 ms 1 ms telia-level3-10.NewYork1.Level3.net [4.68.110.82]
6 2 ms 2 ms 2 ms nyk-bb3-link.telia.net [62.115.115.0]
7 2 ms 2 ms 2 ms nyk-b2-link.telia.net [213.155.130.28]
8 2 ms 2 ms 2 ms cloudflare-ic-301663-nyk-b2.c.telia.net [213.248.77.162]
9 2 ms 2 ms 2 ms 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1]

Trace complete.

1.0.0.1

Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.0.0.1]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms dslrouter.westell.com [192.168.0.1]
2 1 ms 1 ms 1 ms 10.120.137.17
3 1 ms 1 ms 1 ms 8.31.244.73
4 * * * Request timed out.
5 2 ms 1 ms 1 ms telia-level3-10.NewYork1.Level3.net [4.68.110.82]
6 1 ms 2 ms 1 ms nyk-bb3-link.telia.net [62.115.115.0]
7 2 ms 2 ms 2 ms nyk-b2-link.telia.net [213.155.130.28]
8 2 ms 2 ms 2 ms cloudflare-ic-301663-nyk-b2.c.telia.net [213.248.77.162]
9 2 ms 2 ms 2 ms 1dot1dot1dot1.cloudflare-dns.com [1.0.0.1]

Trace complete.

172.68.53.47 CF Boston

Tracing route to 172.68.53.47 over a maximum of 30 hops

1 1 ms <1 ms <1 ms dslrouter.westell.com [192.168.0.1]
2 1 ms 1 ms 1 ms 10.120.137.17
3 1 ms 1 ms 1 ms 8.31.244.73
4 * * * Request timed out.
5 2 ms 1 ms 2 ms telia-level3-10.NewYork1.Level3.net [4.68.110.82]
6 2 ms 2 ms 2 ms nyk-bb4-link.telia.net [80.91.254.15]
7 10 ms 9 ms 9 ms bost-b1-link.telia.net [62.115.122.235]
8 8 ms 8 ms 8 ms cloudflare-ic-316981-bost-b1.c.telia.net [62.115.146.47]
9 8 ms 8 ms 8 ms 172.68.53.47

Trace complete.

172.68.53.180 CF Boston 2

Tracing route to 172.68.53.180 over a maximum of 30 hops

1 1 ms <1 ms <1 ms dslrouter.westell.com [192.168.0.1]
2 1 ms 1 ms 1 ms 10.120.137.17
3 1 ms 1 ms 1 ms 8.31.244.73
4 * * * Request timed out.
5 2 ms 1 ms 1 ms telia-level3-10.NewYork1.Level3.net [4.68.110.82]
6 2 ms 2 ms 2 ms nyk-bb4-link.telia.net [80.91.254.15]
7 10 ms 9 ms 9 ms bost-b1-link.telia.net [62.115.122.235]
8 8 ms 8 ms 8 ms cloudflare-ic-316981-bost-b1.c.telia.net [62.115.146.47]
9 8 ms 8 ms 8 ms 172.68.53.180

Trace complete.

cloudflare

Tracing route to www.cloudflare.com [198.41.214.162]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms dslrouter.westell.com [192.168.0.1]
2 1 ms 1 ms 1 ms 10.120.137.17
3 <1 ms 1 ms 1 ms 8.31.244.73
4 * * * Request timed out.
5 2 ms 2 ms 2 ms telia-level3-10.NewYork1.Level3.net [4.68.110.82]
6 8 ms 2 ms 1 ms nyk-bb3-link.telia.net [62.115.115.0]
7 2 ms 2 ms 2 ms nyk-b2-link.telia.net [213.155.130.28]
8 2 ms 2 ms 2 ms cloudflare-ic-301663-nyk-b2.c.telia.net [213.248.77.162]
9 2 ms 2 ms 2 ms 198.41.214.162

Trace complete.


#19

You can try also doing the same to 1.0.0.1, it could be different.


#20

Matteo - 1.0.0.1 is in both of my tracert postings above - at start of this thread where slow to Boston via Verizon and just above from my wife’s mini-office where fast to NYC via Level 3.
My posts show FIVE tracerts each. They are the results of a bat file I wrote that has five tracert queries in it.