What does it look like now? We made a few more tweaks that should be getting you out of Fidelity quicker.
That’s really odd, I have been working with another player located in Lebanon and his was working better… We’ve made a few more tweaks since this morning. Might check it again when you get a chance.
Still no access to battle.net sites…
**tracert:**
Tracing route to us.battle.net [24.105.29.40]
over a maximum of 30 hops:
1 15 ms 38 ms 54 ms 72-172-211-1.fidnet.com [72.172.211.1]
2 12 ms 12 ms 13 ms nwhnmo1-te00039.fidnet.com [216.229.74.52]
3 15 ms 14 ms 14 ms stlsmo2-te0005.fidnet.com [216.229.74.54]
4 99 ms 26 ms 25 ms v516.core1.stl1.he.net [184.105.18.185]
5 20 ms 20 ms 20 ms 100ge5-1.core2.chi1.he.net [184.105.213.237]
6 21 ms 21 ms 21 ms 206.108.115.62
7 100 ms 92 ms 95 ms ae1-br02-eqch2.as57976.net [137.221.69.35]
8 67 ms 72 ms 76 ms et-0-0-3-br02-eqla1.as57976.net [137.221.65.4]
9 66 ms 66 ms 73 ms be2-pe02-eqla1.as57976.net [137.221.68.73]
10 65 ms 65 ms 65 ms lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
11 84 ms 106 ms 111 ms 10.104.5.40
12 66 ms 66 ms 66 ms 24.105.29.40
Trace complete.
**pathping:**
Tracing route to us.battle.net [24.105.29.40]
over a maximum of 30 hops:
0 DESKTOP-NKD6FKA [192.168.0.100]
1 72-172-211-1.fidnet.com [72.172.211.1]
2 nwhnmo1-te00039.fidnet.com [216.229.74.52]
3 stlsmo2-te0005.fidnet.com [216.229.74.54]
4 v516.core1.stl1.he.net [184.105.18.185]
5 100ge5-1.core2.chi1.he.net [184.105.213.237]
6 206.108.115.62
7 ae1-br02-eqch2.as57976.net [137.221.69.35]
8 et-0-0-3-br02-eqla1.as57976.net [137.221.65.4]
9 be2-pe02-eqla1.as57976.net [137.221.68.73]
10 lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
11 10.104.5.40
12 24.105.29.40
Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-NKD6FKA [192.168.0.100]
0/ 100 = 0% |
1 24ms 0/ 100 = 0% 0/ 100 = 0% 72-172-211-1.fidnet.com [72.172.211.1]
0/ 100 = 0% |
2 30ms 0/ 100 = 0% 0/ 100 = 0% nwhnmo1-te00039.fidnet.com [216.229.74.52]
0/ 100 = 0% |
3 32ms 0/ 100 = 0% 0/ 100 = 0% stlsmo2-te0005.fidnet.com [216.229.74.54]
0/ 100 = 0% |
4 30ms 0/ 100 = 0% 0/ 100 = 0% v516.core1.stl1.he.net [184.105.18.185]
0/ 100 = 0% |
5 43ms 0/ 100 = 0% 0/ 100 = 0% 100ge5-1.core2.chi1.he.net [184.105.213.237]
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% 206.108.115.62
0/ 100 = 0% |
7 44ms 0/ 100 = 0% 0/ 100 = 0% ae1-br02-eqch2.as57976.net [137.221.69.35]
0/ 100 = 0% |
8 89ms 0/ 100 = 0% 0/ 100 = 0% et-0-0-3-br02-eqla1.as57976.net [137.221.65.4]
0/ 100 = 0% |
9 81ms 0/ 100 = 0% 0/ 100 = 0% be2-pe02-eqla1.as57976.net [137.221.68.73]
0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
0/ 100 = 0% |
11 40ms 0/ 100 = 0% 0/ 100 = 0% 10.104.5.40
8/ 100 = 8% |
12 83ms 8/ 100 = 8% 0/ 100 = 0% 24.105.29.40
Trace complete.
I am from Oklahoma but also use Fidelity …I am also suffering from lag when I am in raid groups.
I’m in Arkansas with OzarksGo as my ISP and I’ve been having huge lag running old raids by myself. I’ve also had lag on Diablo 3. A tracert of 37.221.105.2 times out at the same node with the 130.244.2.142 address.
Edit: I’ve had this lag out in the world too, just not as bad as in raids.
Bleezus, im not a customer of yours, but after speaking with my ISP, they seem completely baffled as to what is even going on, although they clearly have identified the problem, they say they are looking for a fix. Cant ISPs just route all traffic around that node?
That support Article is not loading on ANY of my web browsers can someone on the forums explain to me what to do?
Can someone PLEASE tell me how to “Go through a VPN”
You’re not alone. There are many Cableone users both in Texas and south Mississippi having this issue. However, when Cableone is contacted they will tell you it’s outside their network and their control. Since all my other online games play perfectly fine other than WoW, it’s probably not Cableone.
Here’s a copy of my traceroot and mtr. As mentioned before I live in Idaho and use Rise Broadband. I got this off the Battle Net Looking Glass website.
TRACEROUTE:
traceroute to 209.196.95.13 (209.196.95.13), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.306 ms 0.307 ms 0.309 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
09/12/2018 22:00:07 UTC
TRACEROUTE:
traceroute to 209.196.95.13 (209.196.95.13), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.302 ms 0.307 ms 0.312 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
09/12/2018 22:00:07 UTC
TRACEROUTE:
traceroute to 209.196.95.13 (209.196.95.13), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.846 ms 0.848 ms 0.854 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
09/12/2018 22:00:07 UTC
TRACEROUTE:
traceroute to 209.196.95.13 (209.196.95.13), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.247 ms 0.255 ms 0.264 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
09/12/2018 22:00:14 UTC
MTR:
Start: Sun Dec 9 22:00:07 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 0.7 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
09/12/2018 22:00:07 UTC
MTR:
Start: Sun Dec 9 22:00:07 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
09/12/2018 22:00:07 UTC
MTR:
Start: Sun Dec 9 22:00:07 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.5 0.3 0.2 0.5 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
09/12/2018 22:00:07 UTC
MTR:
Start: Sun Dec 9 22:00:14 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.6 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
09/12/2018 22:00:13 UTC
Just checked again, seems to be no change. Also cannot even load Blizzard forums apparently without connecting to VPN. Here’s a winmtr of what I’m seeing to Blizzard Central, and it has me wondering if there’s an issue here in town or closer to me at any rate:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| 192.168.1.1 - 0 | 187 | 187 | 0 | 0 | 11 | 0 |
| 10.60.0.1 - 0 | 187 | 187 | 9 | 19 | 179 | 13 |
| lbnnmoncs1-te0000.fidnet. com - 0 | 187 | 187 | 10 | 22 | 185 | 15 |
| LBNNMO2-BE1.fidnet. com - 0 | 187 | 187 | 11 | 22 | 186 | 15 |
| kscymo1-be3-1100.fidnet. com - 0 | 187 | 187 | 15 | 27 | 191 | 19 |
| 10ge9-5.core1.mci3.he. net - 0 | 187 | 187 | 15 | 26 | 190 | 17 |
| 100ge8-1.core2.chi1.he. net - 0 | 187 | 187 | 25 | 39 | 277 | 27 |
| eqix-ix-ch1.blizzard. com - 0 | 187 | 187 | 26 | 38 | 211 | 27 |
| ae1-br02-eqch2.as57976. net - 0 | 187 | 187 | 26 | 42 | 218 | 29 |
| be2-pe02-eqch2.as57976. net - 0 | 187 | 187 | 36 | 51 | 277 | 39 |
| chi-eqch2-ia-bons-04.as57976. net - 6 | 151 | 142 | 38 | 52 | 278 | 44 |
| 24.105.62.129 - 0 | 187 | 187 | 37 | 52 | 281 | 44 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Can someone PLEASE tell me how to do this?
Very small ISP “peoples telecom” east of Dallas Texas
Ok here is my trace routes I could get… GM can you post the details of exactly how you want them done here as well as your link to how to run them never loaded for me and I went to reddit to get someone to copy and paste there for the instructions in your blue post above.
Removed periods so I can post because it wouldn’t let me post with links…
Tracing route to 137.221.105.2 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms router.asus com [192.168.50.1]
2 16 ms 16 ms 17 ms 167.89.248.1
3 * 18 ms 17 ms 67.221.141.198
4 20 ms 19 ms 20 ms eqix-da1.blizzard com [206.223.118.237]
5 45 ms 75 ms 44 ms ae1-br01-eqda6.as57976 net [137.221.74.33]
6 48 ms 47 ms 48 ms et-0-0-2-br02-swlv10.as57976 net [137.221.65.67]
7 45 ms 47 ms 46 ms et-0-0-67-pe01-swlv10.as57976 net [137.221.83.71]
8 44 ms 44 ms 44 ms 137.221.105.2Trace complete.
Blockquote
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms router.asus com [192.168.50.1]
2 16 ms 16 ms 16 ms 167.89.248.1
3 25 ms 31 ms 34 ms 67.221.141.198
4 20 ms 19 ms 20 ms eqix-da1.blizzard com [206.223.118.237]
5 41 ms 39 ms 44 ms ae1-br01-eqda6.as57976 net [137.221.74.33]
6 41 ms 40 ms 40 ms et-0-0-4-br01-eqch2.as57976 net [137.221.65.38]
7 39 ms 39 ms * be1-pe01-eqch2.as57976 net [137.221.69.67]
8 42 ms 42 ms 40 ms chi-eqch2-ia-bons-02.as57976 net [137.221.66.11]
9 40 ms 40 ms 41 ms 24.105.62.129Trace complete.
A Fidelity user from Lebanon Mo, here and just got done running 2 timewalkers. My world ms never got above 50. So it seems all good at least for me. Thanks for all the info and help all!
Just did some rebooting of things and actually seem to be logging in to normal ping now, looks good for the time being. The real test will come Tuesday when I start playing the game for real again lol.
Hey folks,
We just did another tweak about 20-25 minutes ago, are we seeing any improvements?
1 Like
I’d have to say yes, that’s about the time I finally noticed normal ping without a VPN, and i can load Blizzard website stuff again finally.
1 Like
Well, that is what we have done. We are no longer sending traffic towards Blizzard over our Level3 connections but one of our other upstream carriers totally bypassing it.
1 Like
JUST completed a warfront with ZERO lag, must be fixed whatever it was.
All righty, we were getting pretty good results here too - if you continue to have problems, let’s just move this all to the main thread on this - it’ll help us find any further issues.