Hey all,
It looks like our engineers are looking into this issue. We do not have any sort of ETA for the fix, but hopefully it’s not far off. Keep in mind that these fixes often require a bit of time to provide since it does require multiple companies to coordinate routing changes.
Hope the info helps! We will post any updates on this matter here.
Thanks so much for the update, Kaldraydis!
My latency is back to 7ms so seems fixed until the next time.
I can confirm mine is back to normal as well! Getting ~11 ms on Los Angeles-hosted servers and ~50 ms on Chicago-hosted servers, just like it should be. Thanks so much, technical support team and engineers.
I confirm that for me the spell activation lag, and high latency is now gone. My ms is back to normal ~8 ms world. Thank you.
So, I thought all was well… It was good for me for a few hours , but now it’s worse… My world MS like 150-200, and I’m having lag spikes with dropped frames. However, now instead of my home MS being elevated, it remains low less than 10, usually like 8.
Not sure if this is a different issue, new WinMTR…
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 250 | 250 | 0 | 0 | 3 | 0 |
| 47.155.230.1 - 0 | 250 | 250 | 0 | 2 | 35 | 2 |
| 172.102.101.192 - 0 | 250 | 250 | 2 | 4 | 11 | 6 |
| ae8---0.scr01.lsan.ca.frontiernet.net - 1 | 246 | 245 | 2 | 3 | 102 | 3 |
| ae0---0.cbr01.lsan.ca.frontiernet.net - 1 | 246 | 245 | 2 | 4 | 32 | 4 |
| lag-101.ear2.LosAngeles1.Level3.net - 83 | 58 | 10 | 3 | 4 | 7 | 3 |
| No response from host - 100 | 50 | 0 | 0 | 0 | 0 | 0 |
| BLIZZARD-EN.ear3.LosAngeles1.Level3.net - 0 | 250 | 250 | 2 | 8 | 71 | 4 |
| ae1-br01-eqla1.as57976.net - 0 | 249 | 249 | 8 | 145 | 1141 | 37 |
| et-0-0-2-br01-swlv10.as57976.net - 0 | 250 | 250 | 7 | 10 | 56 | 9 |
| et-0-0-31-pe01-swlv10.as57976.net - 0 | 250 | 250 | 7 | 12 | 87 | 15 |
| las-swlv10-ia-bons-02.as57976.net - 0 | 250 | 250 | 8 | 9 | 14 | 9 |
| 137.221.105.2 - 1 | 246 | 245 | 8 | 9 | 14 | 8 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud ProviderI think it may be a different issue. I just tested it out myself, playing 10 minutes each on both a Los Angeles-hosted server and a Chicago-hosted server. My latency is still normal and I noticed no lag spikes or dropped frames whatsoever - still getting my ~10 ms (Los Angeles) or ~50 ms (Chicago) for both home and world.
Hi there; I wanted to add my two bits as well… been having loot/spell cast lag that ends up disconnecting me since Thursday evening. Even doing all the error 319 suggestions did nothing to improve the play. No addons at all today…
Just ran a tracer and noticed a large latency in one of the IP’s, but I have no idea what to do next. Located near Vancouver, BC. Help? Game is annoyingly unplayable on a few different servers 
Tracing route to 137.221.105.2 over a maximum of 30 hops
1 1 ms <1 ms <1 ms SMITHERS [172.16.2.254]
2 12 ms 12 ms 12 ms 96.48.96.1
3 17 ms 11 ms 12 ms 64.59.147.185
4 17 ms 15 ms 16 ms 66.163.76.66
5 19 ms 18 ms 15 ms rc6wt-tge0-10-0-10.wa.shawcable. net [66.163.68.66]
6 49 ms 45 ms 59 ms ae1-br01-eqse2.as57976. net [137.221.73.33]
7 47 ms 47 ms 47 ms xe-0-0-0-1-br01-eqsv5.as57976. net [137.221.65.40]
8 50 ms 47 ms 47 ms et-0-0-29-br02-eqsv5.as57976. net [137.221.65.117]
9 46 ms 47 ms 45 ms xe-0-0-1-1-br02-eqla1.as57976. net [137.221.65.6]
10 1205 ms 439 ms 447 ms et-0-0-29-br01-eqla1.as57976. net [137.221.65.0]
11 50 ms 52 ms 52 ms et-0-0-2-br01-swlv10.as57976. net [137.221.65.69]
12 48 ms 47 ms 47 ms et-0-0-31-pe01-swlv10.as57976. net [137.221.83.67]
13 45 ms 47 ms 46 ms 137.221.105.2
Trace complete.
Sorry to hear you’re having issues, man. This thread was actually made for people in Southern California with Frontier Communications as their ISP. Sounds like you’re near Vancouver, so you probably want to create a separate thread.