Things are real bad here at the moment:

C:\Windows\System32>pathping snap.net.nz

Tracing route to snap.net.nz [202.37.100.28]
over a maximum of 30 hops:
  0  desktop6.home.local [192.168.1.172]
  1  internal.firewall.home.local [192.168.1.1]
  2  16.17.69.111.static.snap.net.nz [111.69.17.16]
  3  54.32.69.111.dynamic.snap.net.nz [111.69.32.54]
  4  1.111.124.202.static.snap.net.nz [202.124.111.1]
  5  28.100.37.202.static.snap.net.nz [202.37.100.28]

Computing statistics for 125 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           desktop6.home.local [192.168.1.172]
                                0/ 100 =  0%   |
  1    6ms     0/ 100 =  0%     0/ 100 =  0%  home.richms.com.richms.com [192.168.1.1]
                               24/ 100 = 24%   |
  2  949ms    28/ 100 = 28%     4/ 100 =  4%  16.17.69.111.static.snap.net.nz [111.69.17.16]
                                0/ 100 =  0%   |
  3  883ms    25/ 100 = 25%     1/ 100 =  1%  54.32.69.111.dynamic.snap.net.nz [111.69.32.54]
                                0/ 100 =  0%   |
  4  862ms    24/ 100 = 24%     0/ 100 =  0%  1.111.124.202.static.snap.net.nz [202.124.111.1]
                                6/ 100 =  6%   |
  5  920ms    30/ 100 = 30%     0/ 100 =  0%  28.100.37.202.static.snap.net.nz [202.37.100.28]

Trace complete.


The 6ms is because it was over wifi as I was initially thinking it may be my ethernet or something causing the issues.

Anyway, I am about to go into the house and swap the router over etc to prove it isnt my gear, but what is the likely time-frame to get something like this looked at over xmas? Otherwise I will just stop the torrenting on the slingshot connection and move over to using that instead for now.