Seeing same here since about 13 hours ago, it's not just 2degrees/Vocus but also Spark Global-Gateway so probably Southern Cross cable running on one leg again? Appears everything is routing via Sydney.

There was a glimmer of hope overnight with RTT returning to previous levels. However it reverted back to over 200ms at about 3:30am

all fine here on voyager which is going via global gateway

Pinging ec2.us-west-1.amazonaws.com [176.32.118.30] with 32 bytes of data:
Reply from 176.32.118.30: bytes=32 time=166ms TTL=234
Reply from 176.32.118.30: bytes=32 time=166ms TTL=234
Reply from 176.32.118.30: bytes=32 time=166ms TTL=234
Reply from 176.32.118.30: bytes=32 time=166ms TTL=234

Flip flopping all over the place

Following the Vocus NZ network status page, it is looking like maintenance window will conclude tomorrow.

I'm curious for ex-2degrees whether there has been some permanent re-jigging of capacity during this event with regard to merger and access to Vocus' expanded capacity?

Global-Gateway +40 ms ping times only lasted the first day, North American destinations returned mostly to normal from then on although some European locations are still 10-20 ms higher right now. Perhaps there has been some re-routing i.e. via NEXT going on here too.

and it's back again for this week.

I've logged my 4th support ticket with 2D, with tracert's / many graphs like the below showing where the increased latency is being generated from. Of the 4 logged tickets, the last 2 have not been responded to over the last few weeks.

The IP I am tracert to is 198.20.200.1. Super keen to hear from people on different ISPs to tracert to that IP and send me the output in DM. I am at the point now of looking at another ISP (after having been with SNAP/2degrees for 10 years) as this has been an ongoing now for 5 months on and off.

The increased latency causes game disconnects and other in-game issues and 2D are now no longer replying to support requests or seemingly looking to resolve the issue or provide any kind of contact.

Vodafone HFC over Wifi

Pinging ec2.us-west-1.amazonaws.com [176.32.118.53] with 32 bytes of data:
Reply from 176.32.118.53: bytes=32 time=152ms TTL=232
Reply from 176.32.118.53: bytes=32 time=152ms TTL=232
Reply from 176.32.118.53: bytes=32 time=155ms TTL=232
Reply from 176.32.118.53: bytes=32 time=153ms TTL=232

Honestly I am surprised any ISP is guaranteeing that you'll always have the shortest path anywhere. That's just Not How The Internet Works.

Cheers - N

Last weeks 330+ms to Europe reminded me of the interleaving-mandated ADSL days 😅

bensmithnz:

 

The increased latency causes game disconnects and other in-game issues [..]

 

Sounds like you are not the only one going by this other thread. Their traffic routed Cogent looks suspicious not only in regards to network delay and variation characteristics but also the extra propagation delay between the combination of peering PoPs and cable landing points along the west coast of North America and the 33 ms round trip path between Sydney and Auckland. It seems in 2022 the rest of the world is getting farther away. I guess today the major cloud providers are primary consumers of submarine cable capacity and whatever remains is for us plebs.

Voyager Auckland

Tracing route to 198.20.200.1 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     2 ms     2 ms     2 ms  lo-vprn-100.br1.mdr.vygr.net [114.23.3.255]
  3     6 ms     6 ms     7 ms  ae-0-621.cr1.mdr.vygr.net [114.23.3.230]
  4     2 ms     2 ms     2 ms  ae9-143.akbr6.global-gateway.net.nz [122.56.118.157]
  5     2 ms     2 ms     2 ms  ae2-6.tkbr12.global-gateway.net.nz [122.56.127.17]
  6     3 ms     3 ms     3 ms  ae10-10.akbr7.global-gateway.net.nz [202.50.232.30]
  7   133 ms   127 ms   127 ms  122.56.127.53
  8   131 ms   130 ms   137 ms  ae3-10.lebr7.global-gateway.net.nz [122.56.127.26]
  9   132 ms   132 ms   132 ms  ae0-10.lebr8.global-gateway.net.nz [202.50.232.42]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12   161 ms   160 ms   160 ms  ZENIMAX-MED.ear1.Dallas1.Level3.net [4.31.138.162]
 13   161 ms   161 ms   161 ms  198.20.200.1

and 

Tracing route to ec2.us-west-1.amazonaws.com [176.32.118.30]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     2 ms     2 ms     2 ms  lo-vprn-100.br1.mdr.vygr.net [114.23.3.255]
  3     8 ms     2 ms     2 ms  ae-0-621.cr1.mdr.vygr.net [114.23.3.230]
  4     3 ms     3 ms     3 ms  ae9-143.akbr6.global-gateway.net.nz [122.56.118.157]
  5    15 ms     4 ms     3 ms  ae7-2.akbr7.global-gateway.net.nz [122.56.119.53]
  6     4 ms     5 ms     5 ms  ae10-10.tkbr12.global-gateway.net.nz [202.50.232.29]
  7   129 ms   130 ms   130 ms  xe7-0-1-10.lebr7.global-gateway.net.nz [202.50.232.162]
  8   139 ms   135 ms   134 ms  ae3-10.sjbr3.global-gateway.net.nz [122.56.127.25]
  9   141 ms   150 ms   141 ms  ae0.pabr5.global-gateway.net.nz [203.96.120.74]
 10   139 ms   140 ms   138 ms  99.82.178.242
 11   136 ms   136 ms   137 ms  54.240.243.217
 12   136 ms   135 ms   135 ms  150.222.111.93
 13     *        *        *     Request timed out.
 14   140 ms   140 ms   142 ms  150.222.30.34
 15   137 ms   136 ms   136 ms  150.222.30.195
 16   141 ms   141 ms   142 ms  15.230.36.78
 28   137 ms   136 ms   136 ms  176.32.118.30

bensmithnz:

 

The increased latency causes game disconnects and other in-game issues and 2D are now no longer replying to support requests or seemingly looking to resolve the issue or provide any kind of contact.

 

It is looking like they are making further routing changes, for example today there have been changes with Level 3 and Hurricane Electric peering in North America now coming via Vocus 9790 so routes on 2degrees will be closer to that of Slingshot/Orcon/SkyBB. Level 3 is a large transit and content provider including that for Elder Scrolls Online so the route now might be avoiding the dodgy Cogent connection. Hurricane Electric transit picks up traffic from a selection of peering exchanges in North America and Europe which may also result in a more direct route.

Looks like they're playing with the routing again today.

US Google server

Even google.com / YouTube has been hit today

And this is what Unify is showing

Seems pretty widespread. Even local traffic (Cloudflare) has had an increase interestingly, though weirdly, not NextDNS's main NZ DNS ip.