Solved! Solved! Go to Solution.
I think you'll have to ask CloudFlare for that issue.
I am thinking this is more a DNS issue.. that what cloudflare has listed for what that address should be.
While rogers is in charge of ROUTING.. that is just for the routing, to the final IP address.
IF that domain is resolving to the US IP address.. then that is where it will route to.
I am NOT using the rogers DNS servers.. and get the same IP resolution, so i think that most DNS tables have that entry for that domain.
The error massage (I made this error on purpose) clearly shows I am routed to Seattle
And it's not an DNS issue, because I use multiple DNS and get the same results.
It looks like an BGP issue.
"CloudFlare then uses a technology called Anycast to route your visitors to the nearest data center. "
Anycast is a network addressing and routing methodology in which datagrams from a single sender are routed to the topologically nearest node in a group of potential receivers, though it may be sent to several nodes, all identified by the same destination address.
So it doesn't matter what location the IP belongs to. It should be routed to the nearest data centre.
I have to admit wasnt completely sure on what anycasting was.. so did some more research on it.
In a regular scenario.. it would make a difference on where that IP was, as to the routing it would take.
But in an ANYCAST scenario.. you are right, the response that IP should be giving back is from the closest (or first to respond) server.
Only think i could think in this case.. is that the toronto server is not communicating with rogers correctly... or they dont have proper routing to it.
THis may not be a ROGERS only issue.
I just did it from my works BUSINESS Bell direct Fibre into the building.
And my routing goes down into chicago, etc.
Tracing route to www.cloudflare.com.cdn.cloudflare.net [220.127.116.11]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms 10.10.3.22
2 <1 ms <1 ms <1 ms 10.10.3.249
3 1 ms 1 ms 1 ms 10.49.49.37
4 15 ms 13 ms 17 ms tcore4-toronto47_1-0-0-2.net.bell.ca [18.104.22.168]
5 13 ms 13 ms 12 ms newcore2-chicagocp_so3-0-0-0.net.bell.ca [22.214.171.124]
6 18 ms 47 ms 30 ms bx5-chicagodt_xe6-0-0.net.bell.ca [126.96.36.199]
7 12 ms 12 ms 12 ms xe-1-2-0.edge01.ord02.as13335.net [188.8.131.52]
8 12 ms 14 ms 14 ms 184.108.40.206
I think there may be another factor in this. The peering partners that our local carriers use to get to the US would also make a difference as to which site would be seen as "closer" . Those that Cloudfare uses might affect this. In addition if Cloudfare uses a CDN like Akamai, Limelight, etc this could also change things.
OK @gdkitty, can you try copying to address bar or click: https://www.cloudflare.com/cdn-cgi/trace
For example, my test is like this: (I disabled IPv6)
ip=99.225.*.* //This is your IP address. Remember to hide it.
uag=Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.120 Safari/537.36
// Win8.1 64-bit, Chrome 37
colo=SEA //This is the server location (SEA=Seattle)
From my bell account.
Doesnt look like its toronto either?
ORD is chicago? Still closer than seatle..
But that would go along with my trace from BELL, that mine was going through a chicago node.
fl=14f15 h=www.cloudflare.com ip=206.47.x.x
ts=1411045063.952 visit_scheme=https uag=Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; MDDCJS; rv:11.0) like Gecko colo=ORD spdy=off 0
Yes. ORD is Chicago. The server location is often in airport code
For more, you can google "<airport code> + airport"
And, check this out: