WARP connects to SYD from AKL (MyRepublic)

Website, Application, Performance DNS & Network
1

As suggested, I’ve taken the issue from Twitter conversation to here.
I’m on MyRepublic NZ VDSL.
Here’s a traceroute (redacted my IP address slightly):

> traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 52 byte packets
 1  mydevice (192.168.99.1)  9.621 ms  3.103 ms  2.414 ms
 2  101-100-136-xxx.myrepublic.co.nz (101.100.136.xxx)  17.055 ms  17.231 ms  17.555 ms
 3  as13335.auckland.megaport.com (43.243.22.6)  17.720 ms  17.936 ms  17.762 ms
 4  one.one.one.one (1.1.1.1)  16.915 ms  17.467 ms  17.143 ms
> traceroute 1.1
traceroute to 1.1 (1.0.0.1), 64 hops max, 52 byte packets
 1  mydevice (192.168.99.1)  9.754 ms  3.195 ms  2.906 ms
 2  101-100-136-xxx.myrepublic.co.nz (101.100.136.xxx)  17.838 ms  16.822 ms  17.957 ms
 3  as13335.auckland.megaport.com (43.243.22.6)  18.522 ms  17.438 ms  28.828 ms
 4  one.one.one.one (1.0.0.1)  17.131 ms  17.976 ms  16.921 ms

Using the WARP beta on MacOS 10.15.6 (19G2021)
Also running Lulu firewall fwiw

2

Hi Jurgis!

It does connect to Auckland…

3

Maybe I misunderstand something about WARP then? My latency to NZ servers doubled and remained the same to AU ones. Seems my exit node is in Australia. Is that expected?
Here’s a screenshot from WRAP App - says SYD.

Screen Shot 2020-09-01 at 11.53.41 PM
Screen Shot 2020-09-01 at 11.53.41 PM1564×1188 212 KB

4

Traceroute with WARP enabled if that matters

> traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 52 byte packets
 1  one.one.one.one (1.1.1.1)  41.348 ms  41.125 ms  40.401 ms
> traceroute 1.1
traceroute to 1.1 (1.0.0.1), 64 hops max, 52 byte packets
 1  one.one.one.one (1.0.0.1)  40.788 ms  40.323 ms  40.624 ms
5

It seems weird, one possibility is that it’s not actually using the same nodes as 1.1.1.1. Probably due to the fact that Auckland has only 10Gbps of connectivity.

I would send a bug report, they will maybe tell you why that’s the case.

At this point I expect it to be a different host to try and traceroute.

6

You are correct. So two possible reasons:

  1. Not all colos are WARP enabled
  2. ISP has picked a bad (for us) route for Cloudflare WARP traffic

Either way can you make sure and file in-app feedback so we can take a look? We are working on addressing both issues based on incoming load, perf, and feedback recieved.

1 Like
7

What is the host name to test trace routing to? If there even is one…

I presume Auckland can be a combination of both, 10Gbps for the whole country isn’t a lot + higher pricing there to handle tons of traffic.

8

I’ve put feedback, but haven’t heard anything yet.

9

@kkrum is from the team. That’s the best info you’ll get I believe. They won’t reply again once you have an answer…

10

Tried tethering my phone via 2Degrees and it’s same effect.

11

Obviously. The Auckland POP seems to not be used for WARP, so no ISP will ever route you there.

1 Like
12

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.