Menu
Reply
Joining in
  • 8
  • 0
  • 0
Registered: ‎25-05-2015
Message 11 of 107 (342 Views)

Re: Connection issues with Blizzard services

Once again, having the same problems like clockwork. 7pm onwards gives 500ms+ to any blizzard service.

Problems are occurring at:

9 84.116.135.46 (84.116.135.46) 8.698 ms 8.714 ms 8.703 ms

10 brnt-ic-1-ae24-0.network.virginmedia.net (62.254.42.173) 21.541 ms 17.366 ms 16.853 ms

 

Spoiler

TRACEROUTE:
traceroute to (), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.609 ms 0.637 ms 0.810 ms
2 * * *
3 37.244.9.100 (37.244.9.100) 0.681 ms 0.706 ms 0.804 ms
4 37.244.9.32 (37.244.9.32) 0.685 ms 0.787 ms 0.835 ms
5 7-1-23.ear2.Paris1.Level3.net (212.73.205.157) 1.070 ms 1.340 ms 1.621 ms
6 * * *
7 213.46.174.169 (213.46.174.169) 8.610 ms 8.648 ms 8.644 ms
8 * * *
9 84.116.135.46 (84.116.135.46) 8.698 ms 8.714 ms 8.703 ms
10 brnt-ic-1-ae24-0.network.virginmedia.net (62.254.42.173) 21.843 ms 21.905 ms 21.932 ms
11 * * *
12 glfd-core-2b-ae2-0.network.virginmedia.net (213.105.159.246) 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 37.244.9.100 (37.244.9.100) 0.673 ms 0.707 ms 0.774 ms
4 37.244.9.32 (37.244.9.32) 0.644 ms 0.672 ms 0.729 ms
5 7-1-23.ear2.Paris1.Level3.net (212.73.205.157) 1.011 ms 1.220 ms 1.485 ms
6 * * *
7 213.46.174.169 (213.46.174.169) 8.595 ms 8.634 ms 8.637 ms
8 * * *
9 84.116.135.46 (84.116.135.46) 9.233 ms 9.270 ms 9.271 ms
10 brnt-ic-1-ae24-0.network.virginmedia.net (62.254.42.173) 21.850 ms 21.902 ms 21.909 ms
11 * * *
12 glfd-core-2b-ae2-0.network.virginmedia.net (213.105.159.246) 22.523 ms 22.694 ms 22.775 ms
13 * * *
14 * * *
15 * * *


07/02/2017 19:33:48 UTC
--------------------

PING:
PING () 56(84) bytes of data.

--- ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 5000ms

 

07/02/2017 19:33:48 UTC
--------------------

PING:
PING () 56(84) bytes of data.

--- ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 4998ms

 

07/02/2017 19:33:48 UTC
--------------------

TRACEROUTE:
traceroute to (), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 2.529 ms 2.591 ms 2.662 ms
2 * * *
3 37.244.10.100 (37.244.10.100) 0.833 ms 0.868 ms 0.932 ms
4 37.244.10.32 (37.244.10.32) 0.831 ms 0.909 ms 0.984 ms
5 xe-9-1-3.edge6.Amsterdam1.Level3.net (213.19.197.253) 2.328 ms 2.359 ms 2.372 ms
6 ae-2-3201.ear1.London1.Level3.net (4.69.141.66) 7.441 ms 7.393 ms 7.661 ms
7 213.46.174.169 (213.46.174.169) 7.483 ms 7.446 ms 7.436 ms
8 * * *
9 84.116.135.42 (84.116.135.42) 7.555 ms 7.601 ms 7.621 ms
10 brnt-ic-1-ae24-0.network.virginmedia.net (62.254.42.173) 21.541 ms 17.366 ms 16.853 ms
11 * * *
12 glfd-core-2b-ae2-0.network.virginmedia.net (213.105.159.246) 17.737 ms 17.590 ms 17.549 ms
13 * * *
14 * * *
15 * * *


07/02/2017 19:33:52 UTC
--------------------

PING:
PING () 56(84) bytes of data.

--- ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 4998ms

 

07/02/2017 19:33:53 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.6 0.6 0.6 0.7 0.1
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.9.100 0.0% 10 0.9 0.9 0.6 1.8 0.3
4. 37.244.9.32 0.0% 10 0.8 0.8 0.6 1.9 0.4
5. 7-1-23.ear2.Paris1.Level3.net 0.0% 10 16.9 7.0 1.0 26.7 9.2
6. ae-1-3101.ear1.London1.Level3.net 50.0% 10 5085. 5448. 5085. 6061. 456.8
7. 213.46.174.169 0.0% 10 27.7 13.2 8.6 34.4 9.6
8. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
9. 84.116.135.46 0.0% 10 8.7 8.7 8.7 8.8 0.0
10. brnt-ic-1-ae24-0.network.virginmedia.net 0.0% 10 22.0 22.6 21.9 27.7 1.8
11. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12. glfd-core-2b-ae2-0.network.virginmedia.net 0.0% 10 22.7 22.8 22.6 23.1 0.1
13. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0


07/02/2017 19:33:48 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.6 0.6 0.5 0.7 0.1
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.9.100 0.0% 10 1.8 0.8 0.6 1.8 0.4
4. 37.244.9.32 0.0% 10 0.7 0.7 0.6 0.8 0.0
5. 7-1-23.ear2.Paris1.Level3.net 0.0% 10 20.2 2.9 1.0 20.2 6.0
6. ae-1-3101.ear1.London1.Level3.net 50.0% 10 5609. 5526. 5171. 5897. 280.9
7. 213.46.174.169 0.0% 10 8.7 8.6 8.5 8.7 0.0
8. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
9. 84.116.135.46 0.0% 10 8.6 8.7 8.6 8.9 0.1
10. brnt-ic-1-ae24-0.network.virginmedia.net 0.0% 10 25.8 32.0 21.8 73.2 16.7
11. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12. glfd-core-2b-ae2-0.network.virginmedia.net 0.0% 10 22.7 22.7 22.6 22.9 0.1
13. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0


07/02/2017 19:33:48 UTC
--------------------

TRACEROUTE:
traceroute to (), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.399 ms 0.479 ms 0.573 ms
2 * * *
3 37.244.10.100 (37.244.10.100) 0.796 ms 0.846 ms 0.912 ms
4 37.244.10.32 (37.244.10.32) 2.424 ms 2.461 ms 2.471 ms
5 xe-9-1-3.edge6.Amsterdam1.Level3.net (213.19.197.253) 0.547 ms 0.559 ms 0.565 ms
6 ae-2-3201.ear1.London1.Level3.net (4.69.141.66) 7.407 ms 7.388 ms 7.593 ms
7 213.46.174.169 (213.46.174.169) 7.489 ms 7.499 ms 7.507 ms
8 * * *
9 84.116.135.42 (84.116.135.42) 7.616 ms 7.661 ms 7.662 ms
10 brnt-ic-1-ae24-0.network.virginmedia.net (62.254.42.173) 64.161 ms 59.242 ms 58.303 ms
11 * * *
12 glfd-core-2b-ae2-0.network.virginmedia.net (213.105.159.246) 17.714 ms 17.665 ms 17.710 ms
13 * * *
14 * * *
15 * * *


07/02/2017 19:33:57 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.5 0.5 0.3 1.2 0.3
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.10.100 0.0% 10 1.2 0.9 0.8 1.2 0.1
4. 37.244.10.32 0.0% 10 1.0 1.0 0.8 2.5 0.5
5. xe-9-1-3.edge6.Amsterdam1.Level3.net 0.0% 10 0.6 0.6 0.5 0.6 0.0
6. ae-2-3201.ear1.London1.Level3.net 0.0% 10 8.8 7.6 7.4 8.8 0.4
7. 213.46.174.169 0.0% 10 7.5 7.6 7.4 8.6 0.4
8. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
9. 84.116.135.42 0.0% 10 7.8 7.7 7.6 7.8 0.1
10. brnt-ic-1-ae24-0.network.virginmedia.net 0.0% 10 24.4 22.6 16.9 40.7 7.7
11. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12. glfd-core-2b-ae2-0.network.virginmedia.net 0.0% 10 17.7 19.0 17.6 28.2 3.3
13. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0


07/02/2017 19:33:52 UTC
--------------------

PING:
PING () 56(84) bytes of data.

--- ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 4998ms

 

07/02/2017 19:33:59 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.7 0.6 0.3 3.0 0.9
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.10.100 0.0% 10 0.9 0.9 0.8 1.0 0.1
4. 37.244.10.32 0.0% 10 2.1 1.0 0.8 2.1 0.4
5. xe-9-1-3.edge6.Amsterdam1.Level3.net 0.0% 10 0.6 0.6 0.5 0.6 0.0
6. ae-2-3201.ear1.London1.Level3.net 0.0% 10 7.5 7.5 7.4 7.6 0.1
7. 213.46.174.169 0.0% 10 7.5 7.5 7.4 7.5 0.0
8. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
9. 84.116.135.42 0.0% 10 7.7 7.7 7.6 8.0 0.1
10. brnt-ic-1-ae24-0.network.virginmedia.net 0.0% 10 23.7 19.3 16.9 32.9 5.2
11. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12. glfd-core-2b-ae2-0.network.virginmedia.net 0.0% 10 17.6 18.2 17.6 22.8 1.6
13. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0


07/02/2017 19:33:54 UTC
--------------------

 

Reply
0 Kudos
Superuser
  • 13.03K
  • 668
  • 4.42K
Registered: ‎01-11-2009
Message 12 of 107 (325 Views)

Re: Connection issues with Blizzard services

[ Edited ]

@Haevlyn

I'm sorry but those tracert's don't show the problem.

Can you try downloading and running WinMTR so we can see an outbound trace from you to Blizzard?

Also I'm not seeing anything like that here - which makes me wonder if it's utilisation on your network segment. Smiley Sad  However looking at an outbound WinMTR trace would help us to see if that's the case.

Here's my stats from Birmingham

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |  292 |  292 |    1 |    3 |   51 |    3 |
|cpc35-sutt4-2-0-gw.19-1.cable.virginm.net -    1 |  289 |  288 |   10 |   17 |   70 |   11 |
|perr-core-2a-xe-112-0.network.virginmedia.net -    0 |  292 |  292 |    9 |   16 |   87 |   13 |
|                   No response from host -  100 |   58 |    0 |    0 |    0 |    0 |    0 |
| ams2-ic-1-ae0-0.network.virginmedia.net -    0 |  288 |  288 |   29 |   35 |  103 |   36 |
|                           80.249.208.83 -    0 |  292 |  292 |   26 |   33 |   93 |   37 |
|                            37.244.10.33 -    1 |  289 |  288 |   31 |   37 |  103 |   36 |
|                   No response from host -  100 |   58 |    0 |    0 |    0 |    0 |    0 |
|                          185.60.114.159 -    1 |  285 |  283 |   32 |   38 |  103 |   36 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Which is a pretty good tracert with no signs of pings approaching 500ms.  It should be noted that while the worst is 103, the average is still only 38ms.

@jackdowson  Could you post another WinMTR up as well?

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.

Ravenstar68

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.

Reply
0 Kudos
Tuning in
  • 15
  • 0
  • 1
Registered: ‎04-02-2017
Message 13 of 107 (318 Views)

Re: Connection issues with Blizzard services

As requested 

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                         routerlogin.net -    1 | 5305 | 5304 |    0 |    0 |   10 |    0 |
|                   No response from host -  100 | 1062 |    0 |    0 |    0 |    0 |    0 |
|exe2-core-2a-xe-032-0.network.virginmedia.net 1 | 5282 | 5275 |    7 |   18 |  128 |   13 |
|                   No response from host -  100 | 1062 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1062 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1062 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1062 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1062 |    0 |    0 |    0 |    0 |    0 |
| ams2-ic-1-ae0-0.network.virginmedia.net -    1 | 5290 | 5285 |    0 |   45 |  183 |   41 |
|                           80.249.208.83 -    1 | 5278 | 5270 |   28 |   38 |  157 |   34 |
|                            37.244.10.33 -    1 | 5282 | 5275 |    0 |   38 |  143 |   32 |
|                          185.60.112.157 -   17 | 3198 | 2669 |    0 |   38 |  130 |   31 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

 

Still packet loss ~17%.

Reply
0 Kudos
Superuser
  • 13.03K
  • 668
  • 4.42K
Registered: ‎01-11-2009
Message 14 of 107 (305 Views)

Re: Connection issues with Blizzard services

@jackdowson

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 185.60.112.157.  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.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |  665 |  665 |    1 |    2 |   58 |    3 |
|cpc35-sutt4-2-0-gw.19-1.cable.virginm.net -    1 |  657 |  655 |    8 |   19 |   78 |   33 |
|perr-core-2a-xe-112-0.network.virginmedia.net -    0 |  664 |  664 |    9 |   17 |   73 |   13 |
|                   No response from host -  100 |  133 |    0 |    0 |    0 |    0 |    0 |
| ams2-ic-1-ae0-0.network.virginmedia.net -    1 |  661 |  660 |   30 |   37 |   94 |   33 |
|                           80.249.208.83 -    1 |  657 |  655 |    0 |   35 |   94 |   28 |
|                            37.244.10.33 -    1 |  653 |  650 |   26 |   34 |   93 |   38 |
|                          185.60.112.157 -    1 |  657 |  655 |   26 |   33 |  101 |   28 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

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.

Reply
0 Kudos
Fibre optic
  • 362
  • 15
  • 81
Registered: ‎08-09-2015
Message 15 of 107 (297 Views)

Re: Connection issues with Blizzard services

[ Edited ]
Any use to you ? WinMTR Statistics
WinMTR statistics

Host%SentRecvBestAvrgWrstLast
RT-AC88U-1140149449200150
No response from host10010000000
midd-core-2a-xe-113-0.network.virginmedia.net0501501102014217
No response from host10010000000
No response from host10010000000
No response from host10010000000
ams2-ic-1-ae0-0.network.virginmedia.net0501501334317336
80.249.208.830501501273617534
37.244.10.330501501263716835
185.60.112.1570501501273616129



Running ASUS RT-AC88U with Asuswrt-Merlin firmware
Reply
0 Kudos
Superuser
  • 13.03K
  • 668
  • 4.42K
Registered: ‎01-11-2009
Message 16 of 107 (290 Views)

Re: Connection issues with Blizzard services

That one shows no issues whatsoever, in fact it's a better result then mine. - are you having problems now?  If not then the time to run WinMTR is when your actually seeing the issue.

 

________________________________________


Only use Helpful answer if your problems been solved.

Reply
0 Kudos
Fibre optic
  • 362
  • 15
  • 81
Registered: ‎08-09-2015
Message 17 of 107 (288 Views)

Re: Connection issues with Blizzard services

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



Running ASUS RT-AC88U with Asuswrt-Merlin firmware
Reply
0 Kudos
Tuning in
  • 15
  • 0
  • 1
Registered: ‎04-02-2017
Message 18 of 107 (285 Views)

Re: Connection issues with Blizzard services

[ Edited ]

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. Smiley Happy

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.

- Jack

Reply
0 Kudos
Superuser
  • 13.03K
  • 668
  • 4.42K
Registered: ‎01-11-2009
Message 19 of 107 (270 Views)

Re: Connection issues with Blizzard services

[ Edited ]

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. Smiley Sad  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.

Ravenstar68

BTW @Haevlyn

Not ignoring what you said earlier - when you said the problem is at:

9 84.116.135.46 (84.116.135.46) 8.698 ms 8.714 ms 8.703 ms

10 brnt-ic-1-ae24-0.network.virginmedia.net (62.254.42.173) 21.541 ms 17.366 ms 16.853 ms

Hop 9 is in Austria
Hop 10 is in the UK - so the latency difference between the 2 hops is normal given the distance travelled.

________________________________________


Only use Helpful answer if your problems been solved.

Reply
0 Kudos
Superuser
  • 9.37K
  • 361
  • 2.31K
Registered: ‎30-01-2013
Message 20 of 107 (261 Views)

Re: Connection issues with Blizzard services

[ Edited ]

ravenstar68 wrote:

1. To eliminate one possible cause.
2. To prevent issues from developing further as high upstream levels can impact your connection.

 @MUD_Wizard - Would you agree?


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.

He has high downstream power levels though, which usually means lower upstream power. Though it is possible, but unusual, to have high power on both.

High downstream power levels (depending on how high they are) just means there's a small chance his modem could de-sync over a long period of time.

It's not going to be the power levels causing a problem just at 7pm though.

p.s. Pretty sure I had some youtube issues around that time.

 

Reply
0 Kudos