Not Routed to the closest data centre (Bell Canada, AS577)


#1

I don’t know if it is challenging to solve but this seems to be a long-standing issue.
All the data from Bell (AS577) to Cloudflare (AS13335) are routed to ORD (chicago) instead of YYZ (Toronto) causing 1.1.1.1 DNS server to return non-optimal resuits. For example: Google is resolved to Chicago servers.

fl=14f183
h=www.cloudflare.com
ip=64.229.151.*
ts=152762xxxx.xxx
visit_scheme=https
uag=(this is not important, therefore hidden)
colo=ORD
spdy=h2
http=h2
loc=CA

traceroute result:

traceroute to www.cloudflare.com (198.41.215.162), 30 hops max, 60 byte packets
 1  My Router
 2  * * *
 3  kgtnon0817w_lo0_symp.net.bell.ca (64.230.7.202) [AS577]  1.978 ms  1.977 ms  2.309 ms
 4  10.178.206.19 (10.178.206.19) [*]  2.855 ms  2.963 ms  3.338 ms
 5  core2-kingston08_9-0.net.bell.ca (64.230.165.101) [AS577]  22.143 ms  22.157 ms  22.156 ms
 6  tcore3-toronto21_hu2-4-0-2.net.bell.ca (64.230.51.7) [AS577]  25.687 ms  19.296 ms  25.581 ms
 7  tcore3-chicagocp_hundredgige0-8-0-0.net.bell.ca (64.230.79.161) [AS577]  22.590 ms  22.619 ms  22.612 ms
 8  bx6-chicagodt_0-6-0-0.net.bell.ca (64.230.79.85) [AS577]  18.773 ms  18.836 ms  18.840 ms
 9  * * *
10  198.41.215.162 (198.41.215.162) [AS13335]  19.003 ms  19.012 ms  19.010 ms

#2

No peer, no route. Look at the peering points:

https://peeringdb.com/net/1550

According to this post CloudFlare staff is working on it but this is a decision that has to be made by Bell.

Bell could peer with TATA Communications in Toronto for example.
All CF can do is ti ask, and ask and ask. Bell. But if Bell is not interested in peering with the Cloudflare AS…


#3

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