Peering with Megaport Brisbane


#1

My understanding is that Cloudflare is peering with Brisbane Megaport. I live in Brisbane and I want to get connected to the local Cloudflare server for DNS requests.

My ISP (Telecube) is also peering with Megaport in Brisbane, however, I am still getting routed to Sydney:
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 52 byte packets
1 10.0.0.1 (10.0.0.1) 1.559 ms 0.839 ms 0.779 ms
2 103.193.167.212 (103.193.167.212) 6.963 ms 5.888 ms 7.189 ms
3 10.99.212.5 (10.99.212.5) 7.253 ms 8.744 ms 6.463 ms
4 10.97.212.1 (10.97.212.1) 6.755 ms 7.339 ms 6.666 ms
5 as13335.sydney.megaport.com (103.26.68.78) 19.645 ms 20.139 ms 18.399 ms
6 1.1.1.1 18.362 ms 18.028 ms 18.432 ms

If I traceroute a different local ip address, I can see Brisbane Megaport:
traceroute to 119.18.32.2 (119.18.32.2), 64 hops max, 52 byte packets
1 10.0.0.1 (10.0.0.1) 1.048 ms 0.725 ms 0.914 ms
2 103.193.167.212 (103.193.167.212) 7.390 ms 5.889 ms 6.530 ms
3 10.99.212.5 (10.99.212.5) 6.614 ms 7.256 ms 6.452 ms
4 10.97.212.1 (10.97.212.1) 6.639 ms 7.254 ms 6.481 ms
5 as4764.brisbane.megaport.com (103.26.70.70) 7.866 ms 8.562 ms 6.940 ms
6 119.18.32.2 7.930 ms 7.130 ms 6.769 ms

So my question is:

  • is this an issue with my ISP or Megaport or Cloudflare in Brisbane?

#2

Trying changing to Google Public DNS, and retry the traceroutes.


#3

Unfortunately, using 8.8.8.8 made no difference:

1 10.0.0.1 (10.0.0.1) 1.160 ms 0.740 ms 1.041 ms
2 103.193.167.212 (103.193.167.212) 6.403 ms 6.081 ms 6.584 ms
3 10.99.212.5 (10.99.212.5) 6.588 ms 6.163 ms 6.603 ms
4 10.97.212.1 (10.97.212.1) 6.687 ms 7.320 ms 6.499 ms
5 as13335.sydney.megaport.com (103.26.68.78) 18.948 ms 19.029 ms 18.750 ms
6 1dot1dot1dot1.cloudflare-dns.com (1.1.1.1) 18.239 ms 18.334 ms 18.385 ms


#4

So I’ve figured it out, while Cloudflare has peering in Brisbane which helps with faster routes in some cases, they do not have a datacenter there.
Brisbane peering announcement https://blog.cloudflare.com/cloudflare-joins-three-more-peering-exchanges-in-australia/

Perth (Datacenter), Sydney (Datacenter), Melbourne (Datacenter) have Cloudflare Datacenters.

Brisbane only has peering to their network, no datacenter.


#5

Sorry, but you are wrong, there is a data center in Brisbane.

When I use Telstra as an ISP, I get the following traceroute to 1.1.1.1:
1 telstra.gateway (192.168.15.1) 1.582 ms 1.502 ms 1.192 ms
2 * * *
3 144.130.212.209 (144.130.212.209) 3.350 ms 2.278 ms 1.979 ms
4 bundle-ether5.woo-core1.brisbane.telstra.net (203.50.11.136) 3.676 ms
bundle-ether2.cha-edge901.brisbane.telstra.net (203.50.11.144) 3.225 ms 2.344 ms
5 bundle-ether1.woo-edge902.brisbane.telstra.net (203.50.11.139) 3.264 ms 2.842 ms
bundle-ether6.cha-core4.brisbane.telstra.net (203.50.11.140) 6.402 ms
6 bundle-ether2.cha-edge902.brisbane.telstra.net (203.50.11.146) 6.784 ms 4.526 ms
bundle-ether1.cha-edge902.brisbane.telstra.net (203.50.11.143) 4.153 ms
7 clo2241696.lnk.telstra.net (139.130.42.194) 2.155 ms 2.311 ms 1.819 ms
8 1dot1dot1dot1.cloudflare-dns.com (1.1.1.1) 2.115 ms 2.084 ms 1.985 ms

2ms is a clear sign that it is not leaving Brisbane. As you can see, there is a direct link between CloudFlare and Telstra, they don’t use Megaport for peering.

Besides, if I run “dig -c CH -t txt id.server +short @1.1.1.1” to see which Cloudflare DNS server is used I get:
“bne01”. Meaning that the response came from the Brisbane data center.

The problem is somewhere in between my home ISP (Telecube) and Megaport.


#6

Please do traceroutes to a website that uses cloudflare


#7

Sure, here is one:

traceroute rankxl.com
traceroute: Warning: rankxl.com has multiple addresses; using 104.28.30.251
traceroute to rankxl.com (104.28.30.251), 64 hops max, 52 byte packets
1 10.0.0.1 (10.0.0.1) 1.164 ms 0.776 ms 0.748 ms
2 103.193.167.212 (103.193.167.212) 7.162 ms 7.376 ms 6.594 ms
3 10.99.212.5 (10.99.212.5) 6.561 ms 7.385 ms 6.574 ms
4 10.97.212.1 (10.97.212.1) 7.844 ms 7.277 ms 7.857 ms
5 as13335.brisbane.megaport.com (103.26.70.17) 7.823 ms 10.031 ms 7.709 ms
6 104.28.30.251 (104.28.30.251) 6.529 ms 9.193 ms 7.628 ms