High world latency big lagg when in raids

Support Technical Support
121

I ran this while doing world quests just now.

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.0.1 1 312 311 0 0 4 0
10.119.32.1 1 312 311 0 8 12 7
192.168.30.89 1 312 311 0 9 104 11
lag-133.ear1.Dallas1.Level3.net 2 297 292 0 32 578 29
No response from host 100 64 0 0 0 0 0
BLIZZARD-EN.ear3.Dallas1.Level3.net 1 312 311 0 29 46 30
ae1-br01-eqda6.as57976.net 0 311 311 44 49 129 47
et-0-0-4-br01-eqch2.as57976.net 1 311 310 0 72 3079 3079
be1-pe02-eqch2.as57976.net 5 264 251 46 47 57 46
chi-eqch2-ia-bons-04.as57976.net 0 311 311 47 48 56 47
24.105.62.129 5 268 257 47 48 61 49
122

Not only do we have the TF lotery, we now get to roll the dice on joining an instance on whether or not it’ll shard us to a playable server :smiley: Good sh!t bliz. Also, f#ck your new profanity filter.

123

Hey folks,

We’ve made some tweaks and worked with a couple of the ISPs (Primarily Fidelity and its subsidiaries) that were previously having issues which seems to have improved things for them, but we still have work to do on this.

In the mean time, some players in this thread have mentioned that setting up their phone as a mobile hotspot and connecting through that, or using a Virtual Private Network (VPN) client lets them work around things. We don’t support this kind of thing directly since each VPN/phone is different. We also don’t consider it a “fix”, but it may improve your play if you want to look up how to do that.

On that note - if anybody’s on a Fidelity ISP and still having problems, new traceroutes would be helpful. For the rest of you, thanks for the info so far - keep it coming!

1 Like
124

Thank you for keeping us updated. I just had to leave my guild’s Ulduar Timewalking raid because of the unplayable lag spikes when we would pull bosses.

125

Which ISPs are working with you?

126

(Good call, updated.)

2 Likes
127

is Nextlink on that list? Tons of people in Texas have posted saying they are having issues.

3 Likes
128

If you are on Fidelity please let me know directly. I will be more than happy to work with you. I take this game as seriously as you do, been here since BC.

129

I have Fidelity. I will log on and see if it’s any better.

130

How is it faring?

131

no change still craptastic

132

but on the plus side ms only got up to 3k this time in a dungeon , it was at 5k. But just world questing an lvling it was a playablw 130.

133

Sherman/Denison Area in Texas, also using Cableone. Absolutely unplayable lag.

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

— 24.116.90.92 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

09/12/2018 10:56:32 UTC

TRACEROUTE:
traceroute to 24.116.90.92 (24.116.90.92), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.574 ms 0.566 ms 0.566 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

09/12/2018 10:56:32 UTC

MTR:
Start: Sun Dec 9 10:56:32 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 10:56:32 UTC

I have called Cableone several times and they always tell me there is nothing wrong on their end.

134

Still having issues. Tried soloing Blackwing Lair this morning. World latency shot up to 2000 and locked up Wow. The major difference this time was that WinMTR which I was running the whole time showed no problems like it was before for me. So maybe the connection issues have been improved, but there is something else going on.

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.1.1 - 0 | 366 | 366 | 0 | 1 | 7 | 1 |

| 192.168.200.1 - 0 | 366 | 366 | 1 | 1 | 15 | 2 |

| mh1-dsl-72-49-51-1.fuse. net - 0 | 366 | 366 | 31 | 33 | 52 | 31 |

| ae1.cn-ptx-1.core.fuse. net - 0 | 366 | 366 | 31 | 34 | 70 | 34 |

| ae1.cin1.core.fuse. net - 0 | 366 | 366 | 31 | 34 | 71 | 32 |

| xe104.ash1.core.fuse. net - 0 | 366 | 366 | 55 | 58 | 74 | 56 |

| eqix-dc2.blizzard. com - 0 | 366 | 366 | 57 | 59 | 85 | 58 |

| ae1-br01-eqdc2.as57976. net - 0 | 366 | 366 | 61 | 71 | 268 | 71 |

| et-0-0-2-br01-eqch2.as57976. net - 0 | 366 | 366 | 60 | 65 | 136 | 64 |

| be1-pe02-eqch2.as57976. net - 0 | 366 | 366 | 60 | 61 | 77 | 61 |

| chi-eqch2-ia-bons-04.as57976. net - 0 | 366 | 366 | 60 | 63 | 83 | 61 |

| 24.105.62.129 - 0 | 366 | 366 | 60 | 63 | 90 | 66 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

135

If by Fidelity you are referring to Fidelity Communications based in Sullivan, MO, that is my ISP. I’ve been having the same issues as everyone else here for roughly a week connecting to Thrall (US Central I believe) from Lebanon, MO, without using a VPN which also works around it for me. And by issues, I mean high ping both in the world and particularly in Uldir, spiking up in the thousands and causing pauses of 5 seconds or more at times. Here’s my tracert:

Tracing route to 24.105.62.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 19 ms 25 ms 14 ms 10.60.0.1
3 14 ms 14 ms 20 ms lbnnmoncs1-te0000.fidnet.co.m [216.229.74.72]
4 18 ms 19 ms 17 ms LBNNMO2-BE1.fidnet.co.m [216.229.73.89]
5 22 ms 17 ms 20 ms kscymo1-be3-1100.fidnet.co.m [216.229.74.111]
6 17 ms 20 ms 17 ms 10ge9-5.core1.mci3.he.ne.t [184.105.55.1]
7 27 ms 28 ms 29 ms 100ge8-1.core2.chi1.he.ne.t [184.105.81.210]
8 190 ms 36 ms 28 ms eqix-ix-ch1.blizzard.co.m [208.115.136.85]
9 76 ms 140 ms 243 ms ae1-br02-eqch2.as57976.ne.t [137.221.69.35]
10 39 ms 53 ms 45 ms be2-pe02-eqch2.as57976.ne.t [137.221.69.73]
11 47 ms 46 ms * chi-eqch2-ia-bons-04.as57976.ne.t [137.221.66.15]
12 39 ms 38 ms 40 ms 24.105.62.129

Trace complete.

[Side note: your new forums rules about “cannot post links” just made that much harder than it should have been, I had to break every .net and .com in the tracert just to post it, pretty poor foresight there…]

136

Yeah, that’s what I have.

137

We had one router that wasn’t changed yet and that one was done at 11AM. Any better?

138

You are still having serious issues? That trace is after we routed around Level3 so people could get on. Everyone I have spoken with after has said it was working better.

139

Definitely still having issues. Just dropped the VPN connection back to regular to check and logged into 6817 ping.

140

Fidelity customer here… I cannot speak to in game issues at the moment, but still cannot view any battle.net pages. Let me know if i can provide any detail that may be of help.