Frontier latency problems

Technical Support
I guess i spoke too soon. Its horrible again tonight.
There seems to be a lag spike and jitter with this hop

11 117 ms 123 ms 120 ms 192.205.37.65

12 165 ms 201 ms 214 ms cr1.sffca.ip.att.net [12.122.86.198]

It seems the connection to AT&T is bad. You can not only see it jumps from 120ms to 165ms, but also 165-215ms spread.
Just tried to do a dungeon and 3 of the 5 people were having really bad latency and lag spikes.
problem seems to still be resolved ever since the restart on 9/21 for me anyways
Yet another Frontier user. this one in north central PA, stuck with massive latency, the amusing thing about this is when I log in and start in Orgrimmar I am getting between 30 and 60 ms of latency, but if I try to go anywhere else I've watched it scream up to 9700 ms before totally timing me out. Returning to Orgrimmar makes me drop to a whopping 4365 ms of lag.

Traceroute to Exodar server:

1 2 ms 3 ms 2 ms (Home DSL router)
2 10 ms 8 ms 8 ms Local Community
3 10 ms 11 ms 12 ms 74.43.38.65
4 42 ms 24 ms 23 ms xe--0-0-0---0.cor01.asbn.va.frontiernet.net [74.40.3.25]
5 59 ms 23 ms 21 ms ae1---0.cbr01.asbn.va.frontiernet.net [74.40.2.174]
6 257 ms 1976 ms 437 ms ix-7-2-0-0.tcore2.AEQ-Ashburn.as6453.net [c]
7 45 ms 37 ms 39 ms 192.205.34.245
8 59 ms 61 ms 59 ms cr2.wswdc.ip.att.net [12.122.84.82]
9 53 ms 56 ms 62 ms cr2.n54ny.ip.att.net [12.122.3.37]
10 153 ms 58 ms 60 ms cr1.cb1ma.ip.att.net [12.122.31.126]
11 54 ms 55 ms 55 ms 12.122.145.73
12 * 489 ms 463 ms 12.122.251.98
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
4 days and no response from a blue
Sadly, we're a minority that's not going to get much attention right now. There's a ton of other disasters they're dealing with as they try to get things up and running for Pandaria.
Tracing route to 206.18.98.180.tms-idc.com [206.18.98.180]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.254.254
2 23 ms 24 ms 23 ms 184-8-160-1.dr03.blfd.wv.frontiernet.net [184.8.
160.1]
3 25 ms 24 ms 24 ms ge--0-1-3---0.arr01.blfd.wv.frontiernet.net [74.
40.49.129]
4 26 ms 27 ms 28 ms 74.40.4.21
5 57 ms 56 ms 76 ms ae4---0.cor02.chcg.il.frontiernet.net [74.40.1.5
3]
6 57 ms 57 ms 85 ms ae1---0.cor01.asbn.va.frontiernet.net [74.40.2.1
94]
7 56 ms 57 ms 107 ms ae1---0.cbr01.asbn.va.frontiernet.net [74.40.2.1
74]
8 63 ms 63 ms 76 ms ix-7-2-0-0.tcore2.AEQ-Ashburn.as6453.net [206.82
.139.109]
9 65 ms 73 ms 58 ms 192.205.34.245
10 63 ms 64 ms 67 ms cr2.wswdc.ip.att.net [12.122.84.82]
11 * 60 ms 75 ms cr1.cgcil.ip.att.net [12.122.18.21]
12 60 ms 61 ms 63 ms gar2.clboh.ip.att.net [12.122.133.197]
13 72 ms 61 ms 71 ms 12.122.251.22
14 69 ms 59 ms 61 ms 63.240.130.214
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
bump. Can we get a blue post please???
Ok I do NOT know if they fixed the problem or I did, but I recall getting some flyer about ipv6 a few weeks ago from Frontier, so I saw that option and turned it on under the in game system - network options. Shut down completely, turned the router off and back on and logged in and I am smoking up the speed charts compared to what it was before. Good luck.
Unfortunately that didn't work for me. Blue post please?? it's been 5 days.
I might have just hit the same sweet time you mentioned earlier, it wouldn't even connect this morning until I turned the ipv6 off. But during the time it was working really well last night the latency info had IPv4 listed.
COntacted Frontier tech support again. He did remote assistance and looked at the trace routes. Said this was on Blizzards end. That it was on blizzards servers where it was being dropped. He even said he played wow and eve online.

This is the third time I've contacted frontier tech support and all 3 times i was told the same thing.

I contacted blizzard twice, i was told to reinstall wow once and to contact my ISP the other time.
Got a response from a ticket i had in. Saying pretty much blizz is working with their peering partners to get it fixed and there isnt much they can do, but they are trying to resolve it.

I really dont think this will be fixed any time soon, but it would be nice to get a blue post. It's been close to a week since this thread was made.
bump
Still lagging pretty bad, not as bad as it was though. Any updates?
Seriously, this is getting a little ridiculous guys.

183 ms (home)
17342 ms (world)

End of a battleground tonight, was reading 27K+ world at times during the fight

197 ms (home)
6722 ms (world)

Sitting perfectly still in Orgrimmar

A bit more info : I did the netstat -an thing and I got back a wall of numbers. Which sort of has me confused as I thought there should only be 5 or so ...2 for Blizz, 2 for Im and 1 for Browser, but I might be mistaken

One of the Wall of numbers grabbed my attention since it came up with NetName: SPECIAL-IPV4-LOOPBACK-IANA-RESERVE
That term "loopback" really screamed out at me

What's making me really suspicious that it's something in game is that chat continues to function normally, both in battlegrounds, parties, instances, and guild even though I am pullling 6K to 8K latency.
Still lagging, 71 home 1800 world. I really dont think they plan on fixing this. No responses from a blue.
bump
I'm in Martinsburg WV, and Frontier is having issues period. I literally am only getting 100-200 kbps download speed between 6:30 and 11:00 pm. This problem is not on Blizzard's end but is because Frontier has not updated anything in this area after Verizon pulled out. The last 2 weeks it's gotten really bad.

http://www.dslreports.com/forum/r27560644-Congestion-at-CO-again.-

Join the Conversation

Return to Forum