hey blizzard hope u can fix this
Hey, can you do a trace to 24.105.62.129 for me real quick? I want to see where it goes. I have a ticket open with Level3 and heck at this point I’ll pretend you’re my customer just to give them more traces.
Woops, was on an alt.
Hi there,
Having issues since this morning with high latency on Zul’Jin(US). My ping usually sits around 30-50ms and now it’s stuck around 140-150ms.
ISP: Altima Telecom
I’m from Gatineau, QC ( Canada )
Here’s my WinMTR:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 1076 | 1076 | 0 | 0 | 2 | 0 |
| 199.241.132.1 - 0 | 1076 | 1076 | 4 | 13 | 96 | 10 |
| 10.170.192.58 - 1 | 1072 | 1071 | 7 | 13 | 34 | 18 |
| ip41265d25.globale.net - 76 | 267 | 65 | 0 | 16 | 29 | 16 |
| ip41265de5.globale.net - 89 | 236 | 26 | 0 | 16 | 21 | 17 |
| be4834.rcr21.ymq02.atlas.cogentco.com - 0 | 1076 | 1076 | 8 | 14 | 31 | 13 |
|hu0-4-0-1.ccr21.ymq01.atlas.cogentco.com - 0 | 1076 | 1076 | 7 | 14 | 34 | 13 |
| be2088.ccr21.alb02.atlas.cogentco.com - 0 | 1076 | 1076 | 13 | 19 | 45 | 19 |
| be2915.ccr41.jfk02.atlas.cogentco.com - 0 | 1076 | 1076 | 15 | 22 | 43 | 22 |
| be3362.ccr31.jfk04.atlas.cogentco.com - 0 | 1076 | 1076 | 16 | 22 | 47 | 23 |
|be2556.rcr11.b001587-1.jfk04.atlas.cogentco.com - 0 | 1076 | 1076 | 17 | 23 | 46 | 22 |
| 38.88.194.29 - 0 | 1076 | 1076 | 19 | 25 | 51 | 23 |
| ae1-br01-eqny8.as57976.net - 0 | 1072 | 1072 | 132 | 145 | 4629 | 138 |
| et-0-0-2-br02-eqch2.as57976.net - 1 | 1047 | 1042 | 0 | 57 | 4839 | 71 |
| be2-pe02-eqch2.as57976.net - 1 | 1068 | 1066 | 130 | 136 | 157 | 137 |
| chi-eqch2-ia-bons-04.as57976.net - 1 | 1057 | 1052 | 133 | 139 | 159 | 139 |
| 24.105.62.129 - 1 | 1065 | 1062 | 131 | 136 | 154 | 134 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
By the way, why is my route going from New York to Georgia then Amsterdam(Netherlands)? Wtf lol
Thank you.
Im in MS with cable one as well. I downloaded a vpn and can play fine. I suggest you do the same until this gets fixed. Nordvpn is offering a free 7 day trial and then after that you have to pay. It sucks but unless you get the 2 year sub, you’ll have to pay 11$ a month for it which almost doubles your wow sub…the things we do to play this game…lol
In southern Miss, also Cableone. Can barely play, the spikes get so bad. Gotten up to 6k world while my home is 50.
In Texas and also having the same issue. My ISP is NextLink. Been like this for the week. I’m actually still really enjoying the game but this is the kind of thing that will force me to unsub and it seems to be affecting a lot of users. ![:frowning:](https://d38bqls1q93fod.cloudfront.net/en/wow/images/emoji/twitter/frowning.png?v=6" ":frowning:")
Also in Texas, ever since the background patch for 8.1 started and finished on tuesday, the game has had incredible lag spikes. Particularly in raids, i will sit at 30 ping, and when the boss is pulled, it shoots to 5k ping, completely unplayable.
3 Likes
South Western Arkansas and also experiencing this.
This does appear to be connected to sharding as well. Some shards I’m getting perfection connection. Then as soon as I phase…700ms. I’m in Waxahachie TX, on NextLink. Please fix this ASAP. Connection issues will force people away from the game. I stopped playing Fortnite for similar issues. This has to be resolved.
4 Likes
I won’t recommend one myself, but one I saw mentioned by a user in Customer Support was this one.
Exactly Platos. Which is why about 1/3 of the time, I can get into a raid or BG with perfect latency. Other 70% of the time, it’s smooth til pull - then 6 - 21kms and 30seconds to a minute lag behind everyone else at 144 frames per second.
This also started about a week ago. No other game has this issue, which is why while it’s Cableone South Mississippi for many people, it’s definitely not JUST Cableone. Lag occurs at certain nodes or sharding events outside the ISP’s control and seems to be a Blizzard issue.
2 Likes
Funny story…was having problems in Orgrimmar tonight (Uther server). Logged onto an alt that was in the city and immediately hit my hearthstone to get to Dalaran (Legion) because there was a lot less lag and it was a safe spot…
Think about that for a minute ![:slight_smile:](https://d38bqls1q93fod.cloudfront.net/en/wow/images/emoji/twitter/slight_smile.png?v=6" ":slight_smile:")
Well Org is going to lag for other reasons, it’s a zone of constant influx as the Zuldazar Temple layout is trash, and people are constantly toggling Warmode off or on. Org is not a good place to measure ping / latency stability even without massive lag spikes.
I think I’m have the same issue as everyone else. I’m in Ohio with Cincinnati Bell.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| router.asus. com - 0 | 828 | 828 | 0 | 0 | 5 | 0 |
| dsl-xxx-xxx-97-1.fuse. net - 0 | 828 | 828 | 0 | 1 | 6 | 2 |
| ae1.ro-ptx-1.core.fuse. net - 0 | 828 | 828 | 1 | 2 | 9 | 1 |
| ae1.eve2.core.fuse. net - 0 | 828 | 828 | 1 | 2 | 43 | 1 |
| xe100.ash1.core.fuse. net - 0 | 828 | 828 | 13 | 13 | 33 | 13 |
| eqix-dc2.blizzard. com - 0 | 828 | 828 | 13 | 16 | 49 | 15 |
| ae1-br01-eqdc2.as57976. net - 0 | 828 | 828 | 58 | 84 | 1403 | 59 |
| xe-0-0-1-1-br01-eqat2.as57976. net - 0 | 828 | 828 | 58 | 81 | 1206 | 59 |
| xe-0-0-0-0-br01-eqda6.as57976. net - 8 | 635 | 587 | 58 | 105 | 1697 | 181 |
| et-0-0-2-br02-swlv10.as57976. net - 0 | 826 | 826 | 71 | 106 | 1676 | 198 |
| et-0-0-67-pe01-swlv10.as57976. net - 5 | 713 | 684 | 58 | 58 | 75 | 58 |
| las-swlv10-ia-bons-02.as57976. net - 0 | 828 | 828 | 57 | 58 | 62 | 59 |
| 137.221.105.2 - 5 | 709 | 679 | 58 | 58 | 61 | 58 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Still no word from blue I see…
This had better be fixed before patch day or I’m going to be really frustrated.
let wow die maybe
So I am not the most computer savvy person on the planet. The last time I thought I had a good understanding of what my machine was doing was when it used a floppy disc. But I do notice when something is consistent. Every time I have a lag spike the same node shows up in WinMTR.
So what exactly does this mean?
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
et-0-0-2-br01-eqch2.as57976. net - 1 | 492 | 490 | 60 | 87 | 4444 | 62 |
2 Likes
Just ran a dungeon with 1500 world ping… it was not fun
Please someone fix this.
Here’s my Looking Glass results, although I don’t know that they say anything since the tracert has only one hop. My ISP is BlueStream and I’m in South Florida.
PING:
PING 192.146.130.13 (192.146.130.13) 56(84) bytes of data.
— 192.146.130.13 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
08/12/2018 19:41:27 UTC
PING:
PING 192.146.130.13 (192.146.130.13) 56(84) bytes of data.
— 192.146.130.13 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3001ms
08/12/2018 19:41:27 UTC
TRACEROUTE:
traceroute to 192.146.130.13 (192.146.130.13), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.941 ms 1.912 ms 1.918 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
08/12/2018 19:41:27 UTC
TRACEROUTE:
traceroute to 192.146.130.13 (192.146.130.13), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.257 ms 0.266 ms 0.287 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
08/12/2018 19:41:27 UTC
PING:
PING 192.146.130.13 (192.146.130.13) 56(84) bytes of data.
— 192.146.130.13 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
08/12/2018 19:41:34 UTC
TRACEROUTE:
traceroute to 192.146.130.13 (192.146.130.13), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.271 ms 0.281 ms 0.290 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
08/12/2018 19:41:33 UTC
MTR:
Start: Sat Dec 8 19:41:27 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.5 0.5 0.3 1.7 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
08/12/2018 19:41:27 UTC
MTR:
Start: Sat Dec 8 19:41:28 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.3 0.5 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
08/12/2018 19:41:27 UTC
PING:
PING 192.146.130.13 (192.146.130.13) 56(84) bytes of data.
— 192.146.130.13 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
08/12/2018 19:41:39 UTC
TRACEROUTE:
traceroute to 192.146.130.13 (192.146.130.13), 15 hops max, 60 byte packets
1 Blizzard Blizzard 2.189 ms 2.198 ms 2.200 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
08/12/2018 19:41:39 UTC
MTR:
Start: Sat Dec 8 19:41:33 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.5 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
08/12/2018 19:41:33 UTC
MTR:
Start: Sat Dec 8 19:41:34 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
08/12/2018 19:41:34 UTC
unplayeable if u dont fix this is over