i see that tcl5-ic-2-ae0-0 node has a 50% pocket loss.
Yes you do but lets think about this for a minute... because your not the only one.
So this is a tracert or a tracert that then pings what Ips are in the tracert in any case you want the short answer to why 50% is show at tcl5-ic-2-ae0-0 but the most interesting thing is why no packet loss after that hop? Because you would think if the problem is at tcl5-ic-2-ae0-0 that packets are drop in getting to the next hop but it doesn't so there are two reasons for this the most said is tcl5-ic-2-ae0-0 does not want to reply that much or a ping rate limit for it to reply but note this is not the same as a ping thats being routed through tcl5-ic-2-ae0-0 and not direct to tcl5-ic-2-ae0-0 because you don't what to go to tcl5-ic-2-ae0-0 you want to go through it. The other reason all be it not important is if PingPlotter does a tracert that then pings the IPs directly so you might be thinking what the different between a tracert ping and a tracert that then pings the IPs directly? Well a tracert ping sends a ping with limited TTL or number of hops you must reach the intended target as in which it fails if the TTL is low and may get a relpy of the hop it couldn't forward it and so on but a tracert that then pings does the tracert ping then it pings them IP's directly but because that is not your intended target it may router your differently then what your intended target is.
Just thought I'd pop by to add to legacy1's observations, in that I've run a few checks on your Hub and network segment from this end and all checks out okay, no apparent issues or faults to cause any latency or ping problems.
One other thought, how are you connecting, wired or wireless? Ping and lag spikes are likely to more of an issue when connecting via wireless.
Thanks for that info legacy1 and Ralph_R for checking the UBR
Ralph_R - All my devices are Wired, The superhub 2ac is in modem mode with an mikrotik rb2011(forget the rest of the model number) Mainly my Xbox One/Android Tablet/PS4 however the PS4 isn't connected as i tend to disconnect the LAN cable if not in-use as it tends to like downloading things automatic (No WiFi has been setup on the PS4 and Xbox One itself)
I have also tested an D-Link DIR-615 what Virgin Media did supply but again i was still having the doggy routing pocket loss issues.however whenever avoid the tcl5-ic-2-ae0-0 route i have no routed pocket loss like playing Battlefield 4
Battlefield 4 Xbox One random IP sever
Tracing route to 184.108.40.206 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms MikroTik [192.168.3.254] 2 * * * Request timed out. 3 23 ms 13 ms 10 ms brnt-core-2a-xe-021-0.network.virginmedia.net [220.127.116.11] 4 * * * Request timed out. 5 13 ms 10 ms 8 ms brnt-bb-1c-ae1-0.network.virginmedia.net [18.104.22.168] 6 17 ms 9 ms 12 ms m686-mp2.cvx1-b.lis.dial.ntli.net [22.214.171.124] 7 30 ms 16 ms 11 ms 126.96.36.199 8 9 ms 9 ms 9 ms ldn-bb3-link.telia.net [188.8.131.52] 9 11 ms 10 ms 11 ms ldn-b1-link.telia.net [184.108.40.206] 10 9 ms 11 ms 10 ms rackspace-ic-305654-ldn-b1.c.telia.net [220.127.116.11] 11 * * * Request timed out. 12 22 ms 22 ms 25 ms 18.104.22.168 13 22 ms 14 ms 15 ms cored-core9.lon5.rackspace.net [22.214.171.124] 14 12 ms 12 ms 12 ms core9-aggr512b-7.lon5.rackspace.net [126.96.36.199] 15 19 ms 12 ms 14 ms 188.8.131.52
I know where your coming from Ralph_R, It might just be low priority, if this is then i have learned something new
Tracing route to 184.108.40.206 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms MikroTik [192.168.3.254] 2 * * * Request timed out. 3 8 ms 10 ms 9 ms brnt-core-2a-xe-031-0.network.virginmedia.net [220.127.116.11] 4 * * * Request timed out. 5 * * * Request timed out. 6 12 ms 25 ms 21 ms brhm-bb-1c-ae1-0.network.virginmedia.net [18.104.22.168] 7 * * 16 ms tcl5-ic-2-ae0-0.network.virginmedia.net [22.214.171.124] 8 20 ms 18 ms 17 ms m322-mp2.cvx3-a.ltn.dial.ntli.net [126.96.36.199] 9 29 ms 29 ms 29 ms be-72-0.ibr02.lts.ntwk.msn.net [188.8.131.52] 10 24 ms 33 ms 25 ms be-3-0.ibr02.dub30.ntwk.msn.net [184.108.40.206] 11 31 ms 22 ms 25 ms ae11-0.db5-96cbe-1b.ntwk.msn.net [220.127.116.11]
7 hop is not always giving theses * * * sometimes it will, sometimes it wont so might just be a false indication to pocket loss?