Today I have had constant disconnections while in Heroes of the Storm, it generally unplayable.
I have upgraded all network adapter drivers, created all suggested inbound rules for my firewall, reset my router, refresh/renew my ip (and flushed dns), but to no avail. My laptop works fine, and does not experience this issue, so I don’t think its my networking hardware.
Here is the latest WinMTR when problems happens:
> |------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.0.0.1 - 6 | 356 | 336 | 2 | 140 | 4939 | 2 |
| 192.168.1.254 - 6 | 352 | 331 | 2 | 143 | 4939 | 4 |
|75-16-204-1.lightspeed.okcyok.sbcglobal.net - 8 | 338 | 313 | 20 | 191 | 4970 | 29 |
| 71.147.88.157 - 7 | 346 | 323 | 20 | 188 | 4968 | 21 |
| 71.147.64.40 - 77 | 113 | 26 | 0 | 156 | 1064 | 24 |
| 12.83.42.9 - 7 | 350 | 328 | 21 | 192 | 4968 | 24 |
| 12.122.100.105 - 7 | 344 | 323 | 27 | 233 | 4972 | 28 |
| 12.244.90.238 - 7 | 346 | 323 | 26 | 194 | 4973 | 28 |
| ae1-br01-eqda6.as57976.net - 8 | 341 | 317 | 43 | 244 | 4991 | 44 |
| et-0-0-4-br01-eqch2.as57976.net - 9 | 314 | 286 | 43 | 303 | 4989 | 46 |
| be1-pe01-eqch2.as57976.net - 8 | 340 | 316 | 43 | 212 | 4989 | 46 |
| 24.105.62.129 - 7 | 342 | 320 | 42 | 238 | 4989 | 44 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
I’m with Bell and today can’t play heroes because of high ping on central and western servers reaching 250 ping. I have a friend with the same issue and with the same internet provider. I hope this will be corrected tomorrow, cause game is unplayable. (Quebec, Canada)
1 Like
personally i couldn’t even log on, on the battle.net client even before i installed heroes of the storm today, on the heroes tab it says oops sorry we cant find what we wanted to show you. we’ll keep looking! check back later.
when i do try to log into heroes it loads up, attempts to connect, and then after about 30 seconds it always tells me you have been disconnected from battlenet server. and after trying for about 30min here it just loaded in correctly! idk if its an error on my pc or battle.net servers
BrunoDude Your issue appears to start at the router/modem: 10.0.0.1 - 6 | 356 | 336 | 2 | 140 | 4939 | 2 |
I would recommend to show your Internet Service Provider this information. As for other users in this thread, we are currently looking into a major routing issue impacting Bell ISP users.
Thanks.
2 Likes
Hello there, i’m from Europe and tried today to play some games on the NA servers and was getting like 300+ pings on both central and western servers, usually i get like 140 on central and 200 on west. Is this a known issue too?
IDK but I’m in Canada with Bell ISP and I’m on the line now demanding to speak with lvl 2, hes transferring me now, and I’m going to hopefully get a hard-update on the issue at hand… I at least want him to acknowledge for me that they are working on it. Hopefully the more calls they get regarding it will get more ressources dedicated to a fix - and if they find it not to be on their end, then all the better, need to move the resolution forward by removing possible causes!
Hey man i’m with bell too, thought it was only my internet are you getting 250+ ms pings too?
I’m getting from 250ms to 300ms in every HotS games. The ping on every other games or services are fine and i’m still getting my whole 1gbps speed on speedtest
I’m with Bell Canada on a 1gbps symetrical speed Fiber.
I’m talking to bell right now. issue seems to be with the telstarglobal. net
here is a tracert i ran in CMD.exe:
1 2 ms 2 ms 2 ms mynetwork [192.168.2.1]
2 17 ms 18 ms 18 ms 10.11.0.9
3 16 ms 16 ms 16 ms 10.178.206.62
4 17 ms 17 ms 17 ms 10.178.206.63
5 103 ms 95 ms 95 ms tcore4-toronto47_2-8-0-0.net.bell. ca [64.230.107.34]
6 90 ms 91 ms 87 ms tcore4-vancouver_hundredgige0-9-0-0.net.bell. ca [64.230.79.71]
7 89 ms 90 ms 87 ms tcore4-seattle_hundredgige0-5-0-0.net.bell. ca [64.230.79.94]
8 87 ms 136 ms 86 ms bx2-paloalto_xe7-0-0_0.net.bell. ca [64.230.186.54]
9 87 ms 87 ms 87 ms 198.32.176.64
10 95 ms 115 ms 103 ms i-92.paix-core02.telstraglobal. net [202.84.247.42]
11 308 ms 309 ms 307 ms i-10107.sydp-core03.telstraglobal. net [202.84.138.49]
12 306 ms 306 ms 307 ms i-0-0-0-1.sydp10.bi.telstraglobal. net [202.84.222.166]
13 306 ms 307 ms 307 ms unknown.telstraglobal. net [210.176.38.113]
14 261 ms 261 ms 262 ms et-0-0-48-br01-eqsy4.as57976. net [137.221.85.33]
15 260 ms 260 ms 260 ms 137.221.65.96
16 260 ms 259 ms 259 ms xe-0-0-1-1-br02-eqch2.as57976. net [137.221.65.42]
17 262 ms 262 ms 262 ms be2-pe01-eqch2.as57976. net [137.221.69.71]
18 261 ms 260 ms 262 ms 24.105.62.129
Yes, go on TWITTER all who are affected and tweet @Bell and @BlizzardCS and get them to acknowledge the issue and dedicate major ressources to the fix due to the scope and impact on their customers. MAKE them dedicate the resources for a faster fix by making it visible we are A LOT of people having this problem!!! DO IT NOW!
ALso post about it and upvote this reddit thread:
I’ve ran blizzard’s looking glass and it seems to be at least one faulty server. The ping goes from 50 to 250 for no apparent reason only on one hop.
TRACEROUTE:
traceroute to 76.67.158.81 (76.67.158.81), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.309 ms 0.306 ms 0.306 ms
2 37.244.22.2 (37.244.22.2) 0.517 ms 1.125 ms 1.126 ms
3 24.105.30.170 (24.105.30.170) 1.129 ms 1.130 ms 1.166 ms
4 137.221.66.6 (137.221.66.6) 1.717 ms 1.811 ms 1.928 ms
5 137.221.68.68 (137.221.68.68) 1.419 ms 1.435 ms 1.448 ms
6 137.221.68.32 (137.221.68.32) 1.260 ms 1.112 ms 1.384 ms
7 213.248.78.166 (213.248.78.166) 1.444 ms 1.352 ms 1.384 ms
8 dls-b21-link.telia. net (62.115.123.136) 32.502 ms 32.673 ms 32.663 ms
9 213.155.130.179 (213.155.130.179) 43.021 ms 43.036 ms 43.078 ms
10 213.155.130.176 (213.155.130.176) 53.636 ms 53.690 ms 54.933 ms
11 213.248.79.222 (213.248.79.222) 257.980 ms 258.473 ms 258.496 ms
12 * * *
13 * * *
14 * * *
15 * * *
24/10/2018 18:52:45 UTC
So just got off the phone with Bell. They denied anything being wrong on their end and told me to power cycle my modem! Sigh… Bell is the worst. Weird thing is it’s only blizzard games, playing CS go and Destiny 2 with no problem. I just noticed something else they are directing traffic to sydp-core03.telstraglobal. net which is in SYDNEY AUSTRALIA why would they direct network traffic from North America to Australia?
I am also on Bell internet a noticed a problem yesterday while playing on a Central US server, where ping started at 250+ms and not until roughly 22 minutes into the game did it drop back to normal 30ms ping. Today, however, it was just straight 250+ ping, kind of unplayable. I’m gonna be honest and say that I don’t know what most of the information on this thread means (I am not tech savvy), but the information which I understood for the most part I think is that unfortunately, aside from making this issue aware, there is nothing we can do on our end? From the HOTS client it seemed I was getting a better connection to Brazil servers over central US when living in Ontario (Brazil gave me roughly 150+ and Central US game me roughly 250+), and I wanted to see if anyone else also currently has better ping in Brazil.
Guys use a VPN through a VPN i haev no lag issues went from 300ms to 60 ms even a tracert shows the issue is routing problem, this is through a VPN:
1 31 ms 30 ms 30 ms 10.7.16.1
2 31 ms 30 ms 32 ms 23.237.120.17
3 30 ms 32 ms 33 ms be4678.rcr21.ord07.atlas.cogentco. com [38.140.127.81]
4 30 ms 32 ms 33 ms be2150.ccr42.ord01.atlas.cogentco. com [154.54.1.37]
5 33 ms 32 ms 33 ms be2766.ccr41.ord03.atlas.cogentco. com [154.54.46.178]
6 30 ms 30 ms 30 ms 38.104.102.29
7 30 ms 35 ms 33 ms ae1-br02-eqch2.as57976. net [137.221.69.35]
8 30 ms 30 ms 31 ms be2-pe02-eqch2.as57976. net [137.221.69.73]
9 35 ms 36 ms 33 ms chi-eqch2-ia-bons-04.as57976. net [137.221.66.15]
10 31 ms 32 ms 31 ms 24.105.62.129
Tracing route to 185.60.112.157 over a maximum of 30 hops
0 MainPc.home [192.168.1.15]
1 speedport.ip [192.168.1.1]
2 80.106.125.16
3 athe-asr99a-kory-asr9ka.backbone.otenet. net [79.128.241.213]
4 kolasr01-hu-0-5-0-0.ath.OTEGlobe.gr [62.75.3.13]
5 62.75.6.106
6 80.249.208.83
7 ae1-br01-eqam1.as57976 .net [137.221.78.33]
8 et-0-0-31-pe01-eqam1.as57976. net [137.221.78.67]
9 185.60.112.157
Computing statistics for 225 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 MainPc.home [192.168.1.15]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% speedport.ip [192.168.1.1]
0/ 100 = 0% |
2 14ms 0/ 100 = 0% 0/ 100 = 0% 80.106.125.16
0/ 100 = 0% |
3 14ms 0/ 100 = 0% 0/ 100 = 0% athe-asr99a-kory-asr9ka.backbone. otenet. net [79.128.241.213]
0/ 100 = 0% |
4 14ms 0/ 100 = 0% 0/ 100 = 0% kolasr01-hu-0-5-0-0.ath.OTEGlobe.gr [62.75.3.13]
0/ 100 = 0% |
5 — 100/ 100 =100% 100/ 100 =100% 62.75.6.106
0/ 100 = 0% |
6 — 100/ 100 =100% 100/ 100 =100% 80.249.208.83
0/ 100 = 0% |
7 54ms 0/ 100 = 0% 0/ 100 = 0% ae1-br01-eqam1.as57976. net [137.221.78.33]
0/ 100 = 0% |
8 51ms 0/ 100 = 0% 0/ 100 = 0% et-0-0-31-pe01-eqam1.as57976. net [137.221.78.67]
0/ 100 = 0% |
9 51ms 0/ 100 = 0% 0/ 100 = 0% 185.60.112.157
Isp says everything fine , i m on Europe, game is unplayable since Monday.
Tried anything you can imagine, changing and reseting 2 routers, i even formated the pc. I just need to know if its ISP issue or Blizzard
Blockquote
TRACEROUTE:
traceroute to 174.92.1.10 (174.92.1.10), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.670 ms 1.659 ms 1.658 ms
2 37.244.22.2 (37.244.22.2) 2.639 ms 2.646 ms 2.627 ms
3 24.105.30.166 (24.105.30.166) 2.624 ms 2.624 ms 2.622 ms
4 137.221.66.4 (137.221.66.4) 2.776 ms 5.220 ms 5.229 ms
5 137.221.68.68 (137.221.68.68) 2.732 ms 2.735 ms 2.734 ms
6 137.221.68.32 (137.221.68.32) 2.590 ms 1.450 ms 1.836 ms
7 213.248.78.166 (213.248.78.166) 1.834 ms 1.707 ms 1.685 ms
8 dls-b21-link.telia.net (62.115.123.136) 31.768 ms 31.803 ms 31.822 ms
9 213.155.130.179 (213.155.130.179) 45.955 ms 46.161 ms 46.172 ms
10 213.155.130.176 (213.155.130.176) 51.736 ms 53.224 ms 52.969 ms
11 213.248.79.222 (213.248.79.222) 258.170 ms 258.006 ms 257.993 ms
12 * * *
13 * * *
14 * * *
15 * * *
24/10/2018 20:48:03 UTC
PING:
PING 174.92.1.10 (174.92.1.10) 56(84) bytes of data.
— 174.92.1.10 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3007ms
24/10/2018 20:48:03 UTC
MTR:
Start: Wed Oct 24 20:48:03 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.2 0.4 0.0
2.|-- 37.244.22.2 0.0% 10 0.6 0.6 0.5 0.6 0.0
3.|-- 24.105.30.166 0.0% 10 1.0 1.2 0.8 2.4 0.3
4.|-- 137.221.66.4 0.0% 10 1.5 1.5 1.3 1.6 0.0
5.|-- 137.221.68.68 0.0% 10 1.4 1.5 1.3 3.2 0.6
6.|-- 137.221.68.32 0.0% 10 1.2 1.2 1.1 1.3 0.0
7.|-- 213.248.78.166 0.0% 10 1.6 1.5 1.3 1.8 0.0
8.|-- dls-b21-link.telia.net 0.0% 10 32.1 33.7 31.7 41.8 3.0
9.|-- 213.155.130.179 0.0% 10 42.2 42.2 42.0 43.5 0.3
10.|-- 213.155.130.176 0.0% 10 51.5 51.5 51.4 51.7 0.0
11.|-- 213.248.79.222 0.0% 10 258.1 258.1 258.0 258.5 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
16.|-- okvlon0102w-lp140-01-174-92-0-1.dsl.bell.ca 0.0% 10 258.5 258.5 258.5 258.6 0.0
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
24/10/2018 20:48:03 UTC
By the way guys I connected to Windscribe VPN (application) and able to now play again. Just connect to best location and off you go back to normal ping.
Yea i did too back to 30 ms ping
Still got the problem at the moment.
Here is my test with Lookin Glass tester.
With Bell:
TRACEROUTE:
traceroute to 65.93.156.249 (65.93.156.249), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.290 ms 0.279 ms 0.315 ms
2 37.244.22.130 (37.244.22.130) 1.859 ms 1.985 ms 2.116 ms
3 24.105.30.150 (24.105.30.150) 1.148 ms 1.215 ms 1.226 ms
4 137.221.66.2 (137.221.66.2) 1.604 ms 1.672 ms 1.716 ms
5 137.221.68.70 (137.221.68.70) 1.521 ms 1.542 ms 1.544 ms
6 137.221.68.34 (137.221.68.34) 1.208 ms 1.536 ms 1.503 ms
7 213.248.78.166 (213.248.78.166) 1.477 ms 2.993 ms 2.998 ms
8 dls-b21-link.telia.net (62.115.123.136) 31.775 ms 31.884 ms 31.894 ms
9 213.155.130.179 (213.155.130.179) 41.936 ms 41.945 ms 41.999 ms
10 213.155.130.176 (213.155.130.176) 51.529 ms 51.629 ms 51.288 ms
11 213.248.79.222 (213.248.79.222) 258.640 ms 258.828 ms 258.807 m
12 * * *
13 * * *
14 * * *
15 * * *
With VPN:
TRACEROUTE:
traceroute to 209.222.19.251 (209.222.19.251), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.324 ms 0.313 ms 0.311 ms
2 37.244.22.2 (37.244.22.2) 0.541 ms 0.647 ms 0.764 ms
3 24.105.30.166 (24.105.30.166) 0.755 ms 0.811 ms 0.862 ms
4 137.221.66.0 (137.221.66.0) 1.661 ms 1.691 ms 1.758 ms
5 137.221.68.70 (137.221.68.70) 68.396 ms 68.398 ms 68.397 ms
6 137.221.65.5 (137.221.65.5) 68.351 ms 68.342 ms 68.314 ms
7 137.221.65.9 (137.221.65.9) 68.286 ms 68.249 ms 68.225 ms
8 137.221.71.32 (137.221.71.32) 68.139 ms 68.070 ms 68.231 ms
9 nyiix.gi3-6.cr1.nyc1.choopa.net (198.32.160.157) 69.416 ms 70.036 ms 70.010 ms
10 vl42-br2.pnj1.choopa.net (108.61.2.89) 68.942 ms 77.913 ms 77.516 ms
11 ethernet1-2-2-c7-12-b4-1.pnj1.choopa.net (108.61.2.34) 69.450 ms 69.412 ms 69.231 ms
12 209.222.19.251.adsl.inet-telecom.org (209.222.19.251) 68.872 ms 68.899 ms 68.852 ms
TRACEROUTE:
traceroute to 174.95.104.183 (174.95.104.183), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.354 ms 0.333 ms 0.319 ms
2 37.244.22.130 (37.244.22.130) 0.673 ms 0.693 ms 0.835 ms
3 24.105.30.166 (24.105.30.166) 0.799 ms 0.856 ms 0.935 ms
4 137.221.66.4 (137.221.66.4) 1.733 ms 1.746 ms 1.764 ms
5 137.221.68.72 (137.221.68.72) 4.900 ms 4.907 ms 4.893 ms
6 137.221.68.34 (137.221.68.34) 1.085 ms 1.179 ms 1.237 ms
7 213.248.78.166 (213.248.78.166) 1.630 ms 1.536 ms 3.041 ms
8 dls-b21-link.telia.net (62.115.123.136) 33.035 ms 32.474 ms 32.442 ms
9 213.155.130.179 (213.155.130.179) 42.269 ms 42.628 ms 41.964 ms
10 213.155.130.176 (213.155.130.176) 51.536 ms 51.630 ms 51.680 ms
11 213.248.79.222 (213.248.79.222) 258.669 ms 258.703 ms 258.697 ms
12 * * *
13 * * *
14 * * *
15 * * *
24/10/2018 22:17:44 UTC
PING:
PING 174.95.104.183 (174.95.104.183) 56(84) bytes of data.
— 174.95.104.183 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
24/10/2018 22:17:44 UTC
MTR:
Start: Wed Oct 24 22:17:44 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 1.7 0.3 14.5 4.4
2.|-- 37.244.22.130 0.0% 10 0.6 0.5 0.5 0.7 0.0
3.|-- 24.105.30.166 0.0% 10 0.8 1.1 0.8 2.4 0.3
4.|-- 137.221.66.4 0.0% 10 1.6 1.6 1.5 1.7 0.0
5.|-- 137.221.68.72 0.0% 10 1.3 4.8 1.3 35.6 10.8
6.|-- 137.221.68.34 0.0% 10 1.3 1.3 1.1 1.7 0.0
7.|-- 213.248.78.166 0.0% 10 2.8 1.9 1.4 2.8 0.5
8.|-- dls-b21-link.telia.net 0.0% 10 31.6 32.0 31.5 33.2 0.3
9.|-- 213.155.130.179 0.0% 10 42.0 42.8 41.9 47.4 1.5
10.|-- 213.155.130.176 0.0% 10 51.6 51.6 51.5 51.9 0.0
11.|-- 213.248.79.222 0.0% 10 258.6 258.7 258.6 258.9 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
16.|-- toroon2717w-lp140-04-174-95-104-1.dsl.bell.ca 0.0% 10 261.7 261.7 261.6 261.8 0.0
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
24/10/2018 22:17:44 UTC