TRACEROUTE: traceroute to 188.8.131.52 (184.108.40.206), 15 hops max, 60 byte packets 1 Blizzard (Blizzard) 0.487 ms 0.598 ms 0.716 ms 2 * * * 3 220.127.116.11 (18.104.22.168) 0.739 ms 0.797 ms 0.840 ms 4 22.214.171.124 (126.96.36.199) 10.940 ms 11.055 ms 11.111 ms 5 188.8.131.52 (184.108.40.206) 12.251 ms 12.260 ms 12.263 ms 6 220.127.116.11 (18.104.22.168) 10.808 ms 10.816 ms 10.899 ms 7 22.214.171.124 (126.96.36.199) 10.871 ms 10.871 ms 10.905 ms 8 * * * 9 * * * 10 leic-core-2a-ae4-0.network.virginmedia.net (188.8.131.52) 32.597 ms 32.731 ms 32.756 ms 11 * * * 12 * * * 13 * * * 14 * * * 15 * * *
Thanks for you help Kippies, as you say it would be nice to set up a BQM.
Welcome to our forum, I am sorry you are having problems with your connection. We will take a look.
The hub upstream power levels are a bit too high so best we let an engineer take a look please, I will send you a forum private message (Top right) to arrange an appointment.
Also it looks like the area peak time traffic has increased recently and exceeded our thresholds. Apologies as this may impact your gaming at peak times. Our planning team are aware and we would like to carry out some upgrade work reference F004649457 with an estimated review date of 14 SEP 2016. I have updated your account so if we have your correct mobile number you should hopefully now get SMS updates about it. One of the forum team will be in contact in the next few days to discuss further.
The traceroutes you supplied by the way do not prove a problem I am afraid as frequently routers will not respond to pings while handling live traffic well. It is quite difficult to traceroute to Blizzard as they like to safeguard their IP range from attack however they do provide a toolbox that lets you traceroute from them back to you, I have found this to be quite useful in the past if you fancy a play Blizzard Network Diagnostic Tool