Hi everyone, Hoping a local network engineer or 2degrees rep can shed some light on a sudden international routing issue that kicked off overnight. My baseline ping to Oceania game servers (specifically Battlefield 6, which utilizes Amazon Web Services Sydney infrastructure) suddenly jumped from ~30ms to a flat 100+ms without any changes to my local hardware or software setup. (For reference if needed I am Hyperfibre 4) My Setup:

 

• ISP: 2degrees (Vocus network backbone)
• Connection Type: Fibre (ONT and router have been fully power-cycled)
• Location: NZ

To troubleshoot, I ran a fresh traceroute targeting the primary AWS Sydney data block (54.252.0.0). As you can see below, the packets hit an absolute brick wall and time out completely the moment they try to leave the Vocus international edge gateway at Hop 5. There are also some highly unstable latency spikes on the first probes inside the core network at Hops 3 and 4.

```Tracing route to ://amazonaws.com
over a maximum of 30 hops:

  1    10 ms     1 ms     1 ms  HB810
  2     3 ms     2 ms     2 ms  v1.cpcch-ric-bng1.tranzpeer.net
  3   123 ms    22 ms    21 ms  192.168.255.237
  4    60 ms    22 ms    22 ms  192.168.255.233
  5   131 ms    22 ms    21 ms  default-rdns.vocus.co.nz
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.```



(Hop 3 cut off with static IP) > 

Cross-Testing Done:

 

1. Mobile Hotspot Test: Confirmed that switching my PC over to a mobile hotspot on a different cellular network drops the baseline ping straight back down to normal (~50-60ms over cellular). This rules out my PC, Wi-Fi hardware, or game client, proving the drop-off is strictly happening inside the Vocus infrastructure.
2. Cloudflare WARP: Attempted to use Cloudflare WARP to find an alternate route, but the traffic still hits the exact same high-ping detour or drop-off.
3. 2degrees Support Call: I spent time on the phone with 2degrees support. They initially attempted to apply a Static IP profile to my account, but it completely black-holed all traffic right at Hop 3. They have since reverted me to a standard dynamic IP, and the frontline agent has escalated the case to the Network Assurance Team (they quoted an SLA turnaround of up to 7 working days).

It feels like a major trans-Tasman peering or border gateway protocol (BGP) routing breakdown pushing my data onto a slow international backup loop. While I wait for the Assurance Team ticket to move through the corporate queue, is there anything else I can do on my end to bypass this? Cheers!