10.126.64.1 is an IP allocated to a private network, so it could either be your own or part of the Virgin Network.
If its on the 3rd hop then its most likely to be part of Virgins, but its difficult to say without actually seeing a
tracert from your side.
The other thing is it just that hop where you are seeing the packet loss and is it impacting future hops further on down the line.?
If its just that hop, it could be one of Virgins routers just not set to prioritise pings, which can be quite common.
** ....or if it continues all the way it could be part of your local cable network which is suffering from congestion... which sounds like what is happening. This can often occur if you have a "few heavy users" living local to you... and this will also affect your speeds.
Ive tried doing a tracert to you from this side but as your router isnt responding to pings its not shown anything conclusive.
----------------------------
** For example this trace of my own shows 'packet loss' at hop1 - which I know is my router not prioritising packets.
C:\Program Files\Support Tools>tracert google.co.uk
Tracing route to google.co.uk [209.85.229.104]
over a maximum of 30 hops:
1 61 ms 99 ms 99 ms Router [192.168.1.254]
2 * * * Request timed out.
3 * * 18 ms 10.1.2.1
4 * * * Request timed out.
5 14 ms 14 ms 46 ms 87-194-0-206.bethere.co.uk [87.194.0.206]
6 14 ms 14 ms 14 ms 64.233.175.25
7 95 ms 88 ms 22 ms 72.14.232.134
8 20 ms 20 ms 19 ms 216.239.49.45
9 27 ms 20 ms 33 ms 209.85.243.81
10 20 ms 20 ms 19 ms ww-in-f104.google.com [209.85.229.104]
Trace complete.
Hop 2 is where I join my ISPs network at the exchange - it never responds to pings
Hop 3 is the regional router for my ISP - it doesnt respond but at one point it did. Its interesting to note that it responded at 18ms.. but if you look further down you see that hop 6 is still responding in 14ms, so its obvious that hops 3 & 5 are just deprioritising pings rather than it being actual packet loss.
An interesting test to complete is also at
visual ware and then compare to a trace from your own network.
eg
C:\Program Files\Support Tools>tracert 205.177.182.160
Tracing route to dtg376.defenderhosting.com [205.177.182.160]
over a maximum of 30 hops:
1 20 ms 99 ms 99 ms Router [192.168.1.254]
2 * * * Request timed out.
3 15 ms 15 ms 17 ms 10.1.2.1
4 14 ms 13 ms 13 ms cr02.ldn01.pccwbtn.net [195.66.224.167]
5 14 ms 13 ms 13 ms dtg376.defenderhosting.com [205.177.182.160]
Trace complete.
compare with screenshot attached below:-
[attachment deleted by admin]