TRACEROUTE: traceroute to (), 15 hops max, 60 byte packets 1 Blizzard (Blizzard) 0.609 ms 0.637 ms 0.810 ms 2 * * * 3 220.127.116.11 (18.104.22.168) 0.681 ms 0.706 ms 0.804 ms 4 22.214.171.124 (126.96.36.199) 0.685 ms 0.787 ms 0.835 ms 5 7-1-23.ear2.Paris1.Level3.net (188.8.131.52) 1.070 ms 1.340 ms 1.621 ms 6 * * * 7 184.108.40.206 (220.127.116.11) 8.610 ms 8.648 ms 8.644 ms 8 * * * 9 18.104.22.168 (22.214.171.124) 8.698 ms 8.714 ms 8.703 ms 10 brnt-ic-1-ae24-0.network.virginmedia.net (126.96.36.199) 21.843 ms 21.905 ms 21.932 ms 11 * * * 12 glfd-core-2b-ae2-0.network.virginmedia.net (188.8.131.52) 22.773 ms 22.662 ms 22.517 ms 13 * * * 14 * * * 15 * * *
07/02/2017 19:33:48 UTC --------------------
TRACEROUTE: traceroute to (), 15 hops max, 60 byte packets 1 Blizzard (Blizzard) 0.642 ms 0.691 ms 0.833 ms 2 * * * 3 184.108.40.206 (220.127.116.11) 0.673 ms 0.707 ms 0.774 ms 4 18.104.22.168 (22.214.171.124) 0.644 ms 0.672 ms 0.729 ms 5 7-1-23.ear2.Paris1.Level3.net (126.96.36.199) 1.011 ms 1.220 ms 1.485 ms 6 * * * 7 188.8.131.52 (184.108.40.206) 8.595 ms 8.634 ms 8.637 ms 8 * * * 9 220.127.116.11 (18.104.22.168) 9.233 ms 9.270 ms 9.271 ms 10 brnt-ic-1-ae24-0.network.virginmedia.net (22.214.171.124) 21.850 ms 21.902 ms 21.909 ms 11 * * * 12 glfd-core-2b-ae2-0.network.virginmedia.net (126.96.36.199) 22.523 ms 22.694 ms 22.775 ms 13 * * * 14 * * * 15 * * *
TRACEROUTE: traceroute to (), 15 hops max, 60 byte packets 1 Blizzard (Blizzard) 2.529 ms 2.591 ms 2.662 ms 2 * * * 3 188.8.131.52 (184.108.40.206) 0.833 ms 0.868 ms 0.932 ms 4 220.127.116.11 (18.104.22.168) 0.831 ms 0.909 ms 0.984 ms 5 xe-9-1-3.edge6.Amsterdam1.Level3.net (22.214.171.124) 2.328 ms 2.359 ms 2.372 ms 6 ae-2-3201.ear1.London1.Level3.net (126.96.36.199) 7.441 ms 7.393 ms 7.661 ms 7 188.8.131.52 (184.108.40.206) 7.483 ms 7.446 ms 7.436 ms 8 * * * 9 220.127.116.11 (18.104.22.168) 7.555 ms 7.601 ms 7.621 ms 10 brnt-ic-1-ae24-0.network.virginmedia.net (22.214.171.124) 21.541 ms 17.366 ms 16.853 ms 11 * * * 12 glfd-core-2b-ae2-0.network.virginmedia.net (126.96.36.199) 17.737 ms 17.590 ms 17.549 ms 13 * * * 14 * * * 15 * * *
TRACEROUTE: traceroute to (), 15 hops max, 60 byte packets 1 Blizzard (Blizzard) 0.399 ms 0.479 ms 0.573 ms 2 * * * 3 188.8.131.52 (184.108.40.206) 0.796 ms 0.846 ms 0.912 ms 4 220.127.116.11 (18.104.22.168) 2.424 ms 2.461 ms 2.471 ms 5 xe-9-1-3.edge6.Amsterdam1.Level3.net (22.214.171.124) 0.547 ms 0.559 ms 0.565 ms 6 ae-2-3201.ear1.London1.Level3.net (126.96.36.199) 7.407 ms 7.388 ms 7.593 ms 7 188.8.131.52 (184.108.40.206) 7.489 ms 7.499 ms 7.507 ms 8 * * * 9 220.127.116.11 (18.104.22.168) 7.616 ms 7.661 ms 7.662 ms 10 brnt-ic-1-ae24-0.network.virginmedia.net (22.214.171.124) 64.161 ms 59.242 ms 58.303 ms 11 * * * 12 glfd-core-2b-ae2-0.network.virginmedia.net (126.96.36.199) 17.714 ms 17.665 ms 17.710 ms 13 * * * 14 * * * 15 * * *
With regards high power levels. While it's unlikely given your previous WinMTR result that they are causing the issue - Virgin will want to bring them down for two reasons.
1. To eliminate one possible cause. 2. To prevent issues from developing further as high upstream levels can impact your connection.
Edit @Haevlyn - Please note - I'm not dismissing your problem, but looking at those particular tracert's I can't see any evidence of an issue on the route back, so we need to see what the route out to Blizzard shows. @MUD_Wizard - Would you agree?
Only use Helpful answer if your problems been solved.
So far you are the only person who's responded to my requests for WinMTR results. Which is frustrating.
I could have just turned round and said to everyone, I've not got a problem, it's your issue to everyone.
However what I'm trying to do is get information which might help narrow down the issue that I can present to Virgin. The reason I'm doing this is because I believe what people are saying and I really want to help solve the problem. Which is why I consider it
a) Significant that I'm seeing different results. b) Believe the WinMTR results from Virgin to Blizzard might display some common traits.
Note I've done a similar thing before, when people were having problems connecting to Virgin's mail servers from a specific part of the country, asking the right questions allowed me to narrow it down to a specific albeit fairly large geographical area.
This issue is not going to be solved overnight but it's going to take longer to solve if people aren't willing to cooperate and provide information that has been asked for.
@Haevlyn - With this in mind could you please provide the requested WinMTR trace from your PC to 188.8.131.52. I want to see if you are showing packet loss in the same place.
My previous trace was to a different address so here's mine to the requested address.
I'm not showing any significant packet loss (2 - 3 packets out of 650 is negligible. This leads me to think that while there may be an issue, it's not country wide.
@Samantha_L Could you ask the Network team to look at the difference between the 2 results? When we're seeing routing that leaves the Virgin network seemingly through the same nodes, but only seeing 17% packet loss on one of them, that leads me to think the issue lies deep in the Virgin network as opposed to outside it.
Only use Helpful answer if your problems been solved.
It's ok @ravenstar68, I really appreciate your help with this. I really do understand it can be frustrating not getting the information needed, as it is affecting more than just one person, it is only right that everyone pulls together to get things fixed.
Don't worry, I'm not expecting an overnight response! I'm actually really glad that someone can help with this online - considering I am not the account holder and the landlord not helping with the situation. it's really good that people are still willing to listen and delve in to resolve it. I understand you may not be working for VM, but you do have communication with them here so if anything people should be bending over backwards to get you the information you need instead of just ignoring the situation and hoping it just goes away.
It's funny you say about being in a local area - I swear I saw on a post somewhere on these boards that there are others from Plymouth having the same issue as well... maybe it's more local than I first thought... the latency issues might be something completely different, considering that latency and packet loss are two different things. Still, what do I know, I am probably completely wrong haha!
Again, thanks for passing the information on so the situation can be looked into. Something else to quickly note - I loaded up Heroes of the Storm for the first time earlier on, and that started disconnecting as well! So there definitely is a pattern emerging somewhere.
pyrotenax wrote: No , no problems. I was responding to your request for additional data and thought you might need some results from different areas of the country, to compare good/bad routes
Thanks for your assistance. I did make a request for WinMTR results in another thread where people noted they were having problems. As yet all I've seen is "I'm having the same problem too!" responses. Which doesn't help get to the bottom of things.
I play Diablo III and I've not had any problems with latency or disconnects, apart from one in the small hours the other morning, which I think was probably Blizzard doing server maintenance rather than down to Virgin.
I definitely need some outbound WinMTR results from affected people when they're having the issues so I can compare the results.