Not routed to the closest data centre

Website, Application, Performance
,
1

Two locations, with IP 130.15.*.* and 142.155.*.* having problems.
The closest route should be Toronto instead of Montreal.
This is especially a big deal when using the Cloudflare Public DNS. I am still using 8.8.8.8 instead of 1.1.1.1 because of this issue. Google is resolved to LGA (New York) instead of YYZ (Toronto), same results for Akamai and Fastly.

C:\Users\user1>tracert www.cloudflare.com
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.50.1
  2     1 ms    <1 ms    <1 ms  142.155.
  3     3 ms     2 ms     1 ms  66.97.
  4     7 ms     7 ms     7 ms  be106.p01-ptbo.orion.on.ca [66.97.16.49]
  5     7 ms     7 ms     7 ms  be2.p01-toro.orion.on.ca [66.97.16.5]
  6     7 ms     7 ms     7 ms  66.97.16.201
  7     7 ms     6 ms     7 ms  be4832.ccr31.yyz02.atlas.cogentco.com [38.88.241.17]
  8    14 ms    14 ms    14 ms  be3259.ccr21.ymq01.atlas.cogentco.com [154.54.41.206]
  9    14 ms    17 ms    14 ms  hu0-4-0-1.ccr22.ymq02.atlas.cogentco.com [154.54.25.125]
 10    15 ms    15 ms    14 ms  be3381.agr12.ymq02.atlas.cogentco.com [154.54.41.222]
 11    14 ms    14 ms    14 ms  te0-0-2-3.nr11.b029490-1.ymq02.atlas.cogentco.com [154.24.16.58]
 12    14 ms    14 ms    14 ms  mail.optimalgrp.com [38.122.42.114]
 13    14 ms    14 ms    14 ms  198.41.215.162

C:\Users\user1>tracert 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.50.1
  2     1 ms    <1 ms    <1 ms  142.155.
  3     2 ms     2 ms     2 ms  66.97.
  4     7 ms     7 ms     7 ms  be106.p01-ptbo.orion.on.ca [66.97.16.49]
  5     7 ms     7 ms     7 ms  be2.p01-toro.orion.on.ca [66.97.16.5]
  6     7 ms     7 ms     7 ms  66.97.16.201
  7     7 ms     7 ms     7 ms  be4832.ccr31.yyz02.atlas.cogentco.com [38.88.241.17]
  8    15 ms    14 ms    14 ms  be3259.ccr21.ymq01.atlas.cogentco.com [154.54.41.206]
  9    14 ms    14 ms    14 ms  hu0-4-0-1.ccr22.ymq02.atlas.cogentco.com [154.54.25.125]
 10    14 ms    14 ms    14 ms  be3381.agr12.ymq02.atlas.cogentco.com [154.54.41.222]
 11    15 ms    15 ms    14 ms  te0-0-2-3.nr11.b029490-1.ymq02.atlas.cogentco.com [154.24.16.58]
 12    14 ms    22 ms    14 ms  mail.optimalgrp.com [38.122.42.114]
 13    14 ms    14 ms    14 ms  1dot1dot1dot1.Cloudflare-dns.com [1.1.1.1]

C:\Users\user1>curl https://www.cloudflare.com/cdn-cgi/trace
fl=70f16
h=www.cloudflare.com
ip=142.155.*.*
ts=1522811111.111
visit_scheme=https
uag=curl/7.59.0
colo=YUL
spdy=h2
http=h2
loc=CA

C:\Users\user1>nslookup www.google.com 1.1.1.1
Server:  1dot1dot1dot1.Cloudflare-dns.com
Address:  1.1.1.1

Non-authoritative answer:
Name:    www.google.com
Addresses:  2607:f8b0:4006:801::2004
          172.217.9.228

C:\Users\user1>nslookup 172.217.9.228 1.1.1.1
Server:  1dot1dot1dot1.Cloudflare-dns.com
Address:  1.1.1.1

Name:    lga34s11-in-f4.1e100.net
Address:  172.217.9.228
2

I don’t believe it will be solved anytime soon, since this is an issue with the edsn_client_subnet header. They do not support it because of privacy concerns. It works perfectly for anycast networks, but not Google or akamai.

3

Routing depends a bit on the peering arrangements with various telcos/ partners. Thanks for the report.

4

I believe this issue is basically the same stated, and discussed briefly with @cs-cf, here:

1 Like
5

Don’t believe anything that @cscharff guy says… he’s been wrong 10x this morning already.

1 Like
6

Welp, could you believe me if I said I didn’t realize it was you in here? :see_no_evil::hear_no_evil::speak_no_evil:

Will get back to you in that other thread on Monday though, would love to see if I can download at 800/900 Mbps from a server so far away.

7

Problem seems to be solved. All the Cloudflare traffic is correctly routed to Toronto now. Hopefully it’s not temporary.

fl=xxxxx
h=www.cloudflare.com
ip=142.155.*.*
ts=152351xxxx.xxx
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36
colo=YYZ
spdy=h2
http=h2
loc=CA
1 Like
8

This topic was automatically closed after 14 days. New replies are no longer allowed.