I'm on 2degrees fiber, ping to 1.1.1.1 is 43ms which is a bit higher than usual, but Geekzone and every other website is operating fine for me.

evilonenz: I will continue to blame the AKL POP, makes sense given I'm in Auckland.
Loading Geekzone is horrendous, given seeing nearly 800ms of latency, I'm not surprised!

Strange - Seeing ~50msec to Geekzone and ~ 38msec to 1.1.1.1 on 2degrees in Wellington.

Still Cloudflare traffic being routed Australia for bits being proxied through them.

freitasm: It maybe something affecting only some 2degrees customers/areas.

It must be, the results are horrid:

Pinging geekzone.co.nz [2606:4700:10::6816:2e48] with 32 bytes of data:
Reply from 2606:4700:10::6816:2e48: time=718ms
Request timed out.
Reply from 2606:4700:10::6816:2e48: time=793ms
Reply from 2606:4700:10::6816:2e48: time=753ms

Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=706ms TTL=60
Reply from 1.1.1.1: bytes=32 time=781ms TTL=60
Request timed out.
Reply from 1.1.1.1: bytes=32 time=691ms TTL=60

Ping statistics for 1.1.1.1:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 691ms, Maximum = 781ms, Average = 726ms

I really hope they get this POP sorted, quite painful to browse anything Cloudflare right now.

From Wellington:

 
Reply from 2606:4700:10::6816:2e48: time=36ms
Reply from 2606:4700:10::6816:2e48: time=35ms
Reply from 2606:4700:10::6816:2e48: time=37ms
Reply from 2606:4700:10::6816:2e48: time=37ms
 
Ping statistics for 2606:4700:10::6816:2e48:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 35ms, Maximum = 37ms, Average = 36ms
 

I think it's affecting parts of the 2degrees network. We haven't heard anything from anyone today...

Seems like something has just been sorted, I've dropped to 35ms to Geekzone and 30 odd to 1.1.1.1, definitely a lot more useable, routing doing its thing.

Fingers crossed this lasts, I've been VPN'ing into work to make Cloudflare sites more useable for the evening thus far.

This issue is now resolved. I'm seeing ~35 ms latency to Sydney and upload speed on speed.cloudflare.com is about 4500x faster than before (no exaggeration, and actually rounded down...)

2degrees routing issue is back.

$ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=60 time=733 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=60 time=734 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=60 time=733 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=60 time=707 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=60 time=713 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=60 time=722 ms

@morganbrowne @duffles

Okay, it just resolved itself in about five minutes that time around. Back to normal very shortly after I posted that message.

ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=60 time=32.0 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=60 time=31.7 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=60 time=33.3 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=60 time=32.4 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=60 time=32.0 ms

Kodiack:

 

2degrees routing issue is back.

 

$ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=60 time=733 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=60 time=734 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=60 time=733 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=60 time=707 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=60 time=713 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=60 time=722 ms

 

@morganbrowne @duffles

 

Where are you in the country?

Not seeing it here in Wellington

jxs@IRONHIDE ~ % ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: icmp_seq=0 ttl=60 time=36.465 ms
64 bytes from 1.1.1.1: icmp_seq=1 ttl=60 time=36.269 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=60 time=35.964 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=60 time=37.096 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=60 time=36.086 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=60 time=37.032 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=60 time=36.289 ms
--- 1.1.1.1 ping statistics ---

7 packets transmitted, 7 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 35.964/36.457/37.096/0.411 ms

Jiriteach:

 

Where are you in the country?

 

Not seeing it here in Wellington

 

jxs@IRONHIDE ~ % ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: icmp_seq=0 ttl=60 time=36.465 ms
64 bytes from 1.1.1.1: icmp_seq=1 ttl=60 time=36.269 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=60 time=35.964 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=60 time=37.096 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=60 time=36.086 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=60 time=37.032 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=60 time=36.289 ms
--- 1.1.1.1 ping statistics ---

 

7 packets transmitted, 7 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 35.964/36.457/37.096/0.411 ms

 

It's already resolved itself in about five minutes. I'm Auckland-based.

This issue momentarily recurred again, but has already sorted itself out.

                                                                 Packets               Pings
 Host                                                          Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. fritz.box                                                   0.0%    21    0.5   0.5   0.4   0.5   0.0
 2. 41.7.69.111.static.snap.net.nz                              0.0%    21    5.9   7.9   4.2  30.8   6.0
 3. as23655.auckland.megaport.com                               0.0%    21    4.1   4.9   2.7  21.0   3.7
 4. as4826.auckland.megaport.com                               40.0%    21  690.7 674.6 658.5 705.6  15.1
 5. be101.bdr01.akl03.akl.nz.vocus.network                     35.0%    21  719.2 698.6 678.2 724.0  13.5
 6. be100.bdr01.akl05.akl.nz.vocus.network                     65.0%    21  722.3 698.9 679.7 722.3  13.6
 7. be204.cor02.syd04.nsw.vocus.network                        20.0%    21  715.8 699.2 677.9 716.0  10.9
 8. be101.bdr02.syd03.nsw.vocus.network                        40.0%    21  690.1 700.8 690.1 733.8  12.0
 9. as13335.bdr02.syd03.nsw.VOCUS.net.au                       36.8%    20  687.4 702.2 687.4 724.0  11.7
10. one.one.one.one                                            40.0%    20  710.3 700.2 685.8 714.3   9.7

I noticed the above as well earlier this afternoon - was up in the 700~ms range again, and then dropped back down to 30~ms. Testing from Auckland.