Increase in ping and lag

[SoloD007]

That's pretty funny

But looks like hop 6 is the interesting thing here. Would your ISP shed light on this?

and another ping and trace route to an Australia server located in Sydney.

170.64.147.31 Sydney, DIGITALOCEAN-ASN

C:\Users\OEM>ping 170.64.147.31

Pinging 170.64.147.31 with 32 bytes of data:
Reply from 170.64.147.31: bytes=32 time=33ms TTL=51
Reply from 170.64.147.31: bytes=32 time=30ms TTL=51
Reply from 170.64.147.31: bytes=32 time=31ms TTL=51
Reply from 170.64.147.31: bytes=32 time=30ms TTL=51

Ping statistics for 170.64.147.31:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 33ms, Average = 31ms

C:\Users\OEM> tracert 170.64.147.31

Tracing route to 170.64.147.31 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.xxx.xx.1
2 * * * Request timed out.
3 7 ms 3 ms 3 ms as9500.auckland.megaport.com [43.243.22.92]
4 7 ms 7 ms 7 ms as4826.auckland.megaport.com [43.243.22.18]
5 29 ms 31 ms 31 ms be101.bdr01.akl05.akl.nz.vocus.network [114.31.202.50]
6 * * * Request timed out.
7 32 ms 31 ms 31 ms be1.bdr04.syd03.nsw.vocus.network [114.31.192.115]
8 33 ms 31 ms 31 ms ip-250.71.254.124.static.VOCUS.net.au [124.254.71.250]
9 32 ms 31 ms 31 ms 143.244.224.180
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 31 ms 31 ms 31 ms 170.64.147.31