audious
join:2008-06-03
| reply to ansky08
Re: Lag, Disconnecting in World of Warcraft
Perhaps we're not informing the right people of this ongoing issue. I intend on calling customer support and contacting supervisors when I get home. We've provided more than enough trace routes to blizzard and OOL, and no one seems to be any closer to a solution. |
|
ansky08
join:2005-07-11
New Milford, NJ
| been having lag spike issues for about 3 weeks now. some nights are OK, some nights are just downright terrible.
ordered Verizon DSL - huge step down in speed, but if it's reliable, it is the clear winner.
kind of stinks to disconnect during Kil'jaeden multiple times |
|
audious
join:2008-06-03
| reply to ansky08
Time Warner Clients are getting the same bad hop.
Tracing route to us.logon.worldofwarcraft.com [12.129.232.116]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 86 ms 38 ms 68 ms gig-5-1-nycmnyw-rtr2.nyc.rr.com [24.29.97.77]
4 47 ms 39 ms 64 ms pos-0-0-nycmnyw-rtr1.nyc.rr.com [24.29.101.241]
5 77 ms 94 ms 97 ms pos-6-2-nycmnyrdc-rtr1.nyc.rr.com [24.29.119.29]
6 80 ms 77 ms 97 ms gig1-0-0-nwrknjmd-rtr1.nyc.rr.com [24.29.130.182
]
7 57 ms 36 ms 86 ms te-4-3.car1.Newark1.Level3.net [4.79.188.113]
8 63 ms 106 ms 105 ms ae-31-55.ebr1.Newark1.Level3.net [4.68.99.158]
9 95 ms 86 ms 71 ms ae-2.ebr1.NewYork1.Level3.net [4.69.132.97]
10 39 ms 54 ms 37 ms ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74]
11 57 ms 81 ms 49 ms ae-33-89.car3.NewYork1.Level3.net [4.68.16.133]
12 * * * Request timed out.
13 113 ms 115 ms 115 ms tbr1.n54ny.ip.att.net [12.123.0.90]
14 113 ms 114 ms 113 ms cr2.n54ny.ip.att.net [12.122.16.149]
15 119 ms 120 ms 129 ms cr2.wswdc.ip.att.net [12.122.3.38]
16 137 ms 153 ms 135 ms cr1.attga.ip.att.net [12.122.1.173]
17 171 ms 141 ms 163 ms cr2.dlstx.ip.att.net [12.122.28.174]
18 148 ms 141 ms 149 ms cr2.la2ca.ip.att.net [12.122.28.178]
19 154 ms 154 ms 154 ms tbr2.la2ca.ip.att.net [12.122.19.206]
20 154 ms 160 ms 190 ms 12.127.3.189
21 124 ms 144 ms 134 ms 12.122.255.74
22 135 ms 141 ms 135 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.12
9.193.242]
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.
---------------------------------------------------------------------------------- ----------------------------------------------
Tracing route to us.logon.worldofwarcraft.com [12.129.224.110]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 26 ms 11 ms 19 ms gig-5-1-nycmnyw-rtr2.nyc.rr.com [24.29.97.77]
4 24 ms 26 ms 20 ms pos-5-0-nycmnyrdc-rtr2.nyc.rr.com [24.29.119.26]
5 22 ms 29 ms 20 ms tenge-0-0-0-nycsnyoo-rtr1.nyc.rr.com [24.29.119.
102]
6 36 ms 10 ms 14 ms te-4-1.car3.NewYork1.Level3.net [4.78.182.45]
7 38 ms 43 ms 42 ms ggr2-p360.n54ny.ip.att.net [192.205.33.93]
8 149 ms 142 ms 140 ms tbr1.n54ny.ip.att.net [12.123.0.90]
9 145 ms 139 ms 131 ms cr2.n54ny.ip.att.net [12.122.16.149]
10 147 ms 135 ms 144 ms cr2.wswdc.ip.att.net [12.122.3.38]
11 159 ms 155 ms 151 ms cr1.attga.ip.att.net [12.122.1.173]
12 173 ms 163 ms 160 ms cr2.dlstx.ip.att.net [12.122.28.174]
13 155 ms 179 ms 164 ms cr2.la2ca.ip.att.net [12.122.28.178]
14 148 ms 162 ms 157 ms tbr2.la2ca.ip.att.net [12.122.19.214]
15 160 ms 157 ms 159 ms 12.127.3.189
16 135 ms 120 ms 126 ms 12.122.255.74
17 118 ms 123 ms 121 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.12
9.193.246]
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. |
|
audious
join:2008-06-03
| reply to ansky08
Here is a thread from LAST YEAR. Seems this isn't the first time this nonsense is happening.
»forums.worldofwarcraft.com/threa···19&sid=1
I'm furious. |
|
ansky08
join:2005-07-11
New Milford, NJ
| if Verizon is reliable once it arrives, I'm cancelling OOL and not looking back. You'd think in this day and age, with hundreds of complaints, something would get done in a reasonable amount of time. Companies pointing fingers at each other doesn't solve the problem. |
|
JDCMAN
join:2006-02-23
Somers, NY | reply to ansky08
Look, complain to Cablevision, complain to WoW, and it couldn't hurt to write a nasty email to level3 (or wherever the hop goes bad). The squeaky wheel gets the oil, you know. |
|
mute11
join:2008-06-05
Floral Park, NY
| I'd suggest joining this yahoo group and getting the issue noticed there, as well. It's a support group frequented by some very high level Cablevision employees, like the CTO.
»finance.groups.yahoo.com/group/lioptonline/ |
|
Pizz
Hi
join:2000-10-27
Astoria, NY
 ·Verizon Online DSL
 ·RoadRunner Cable
| reply to ansky08
This is from a ATT Tech who works at the LA Noc. It showed the problem, and blizzard *gasp* actually looked into the issue, and my latency is fine again.
Do a end to end ping with the port of the server being used - 3724 - if the ping comes back fine, than its not their server's problem. But if it comes back with very high latency, its a problem on their end. Usually it's a peering problem with Cogent and their ISP ATT.
Also, certain peers incoming on a backbone that isnt 'paid', will get lowest priority during peak-times. So if cogent doesnt have a good relationship with ATT (I.E. Mutual peering or paid) latency like this will occur. |
|
mute11
join:2008-06-05
Floral Park, NY | I wouldn't expect this to be the latter situation, unless a contract just expired, as this is a new issue dating back only about a month. Hell, if this had been the case from day one I doubt anyone would still be playing from the affected areas. |
|
audious
join:2008-06-03 | reply to ansky08
So who isn't paying their bills on time? Blizzard? Optimum? The fact is WE ARE, to both companies.
We want answers. |
|
Lightmgl
join:2007-03-01
Montville, NJ
4 edits | reply to ansky08
Just wanted to add into this that it is not only World of Warcraft. I have been experiencing the exact same symptoms, generally during peak hours (6pm to 11pm est) on all of Nexon's games. Nexon is based in Los Angeles, and while I don't have traceroutes on hand at the moment, the ones I have done in the past showed massive packetloss and 3000-5000 pings on Internap and ATT Los Angeles nodes when the packetloss occurs.
Dunno if its directly related to the WoW issue or just similar, but this could be an issue with lag and packetloss to the entire Los Angeles region? I know alot of the Blizzard servers used to route through Internap along with ATT. There were issues back in January like this and supposedly Blizzard took care of it on their end somehow. It seems now both ATT and Internap are giving people trouble through a couple of ISPS (Time Warner, Optimum, and Roadrunner) as there have been threads on the WoW forums the last few days about it. I wonder if Blizzard's "fix" in January was to remove Internap from the equation as I go through Cogentco now and I did not used to. The whole system out there has something wrong.
These issues started appoximatly 1 month ago, prior to then there were no issues. |
|
Pizz
Hi
join:2000-10-27
Astoria, NY | reply to ansky08
can you try running a tracert to www.everquest.com and post the results, im curious how you're routed. Their servers are on the west coast as well. |
|
dantheman815
join:2008-06-10
Kings Park, NY
| reply to ansky08
Bump Heres my Tracert:
Tracing route to 206.16.23.106 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.1
2 7 ms 18 ms 15 ms 10.29.128.1
3 11 ms 7 ms 11 ms dstswr2-vlan2.rh.stjmny.cv.net [167.206.39.162]
4 10 ms 11 ms 13 ms rtr4-ge1-10.mhe.hcvlny.cv.net [167.206.39.137]
5 10 ms 9 ms 12 ms rtr4-tg11-3.wan.hcvlny.cv.net [64.15.4.37]
6 * * * Request timed out.
7 * * * Request timed out.
8 11 ms 14 ms 11 ms vl3491.ccr04.jfk02.atlas.cogentco.com [154.54.7.
9]
9 16 ms 31 ms 17 ms te8-2.ccr02.dca01.atlas.cogentco.com [66.28.4.12
6]
10 20 ms 29 ms 17 ms vl3493.mpd01.dca02.atlas.cogentco.com [154.54.7.
230]
11 17 ms 27 ms 17 ms vl3497.mpd01.iad01.atlas.cogentco.com [154.54.5.
66]
12 25 ms 18 ms 18 ms 192.205.35.105
13 60 ms 63 ms 58 ms tbr2.wswdc.ip.att.net [12.123.8.134]
14 63 ms 62 ms 61 ms cr2.wswdc.ip.att.net [12.122.16.93]
15 59 ms 62 ms 77 ms cr1.attga.ip.att.net [12.122.1.173]
16 59 ms 62 ms 60 ms cr2.dlstx.ip.att.net [12.122.28.174]
17 63 ms 64 ms 62 ms tbr2.dlstx.ip.att.net [12.122.18.238]
18 59 ms 57 ms 58 ms br2.dlstx.ip.att.net [12.123.16.213]
19 58 ms 60 ms 58 ms mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255
.78]
20 58 ms 58 ms 58 ms mdf002fbi8ks0001-eth-1-3.dal1.attens.net [63.241
.192.122]
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. |
|
Anon1267
@optonline.net
| reply to ansky08
Tracing route to us.logon.worldofwarcraft.com [12.129.232.112]
over a maximum of 30 hops:
1 6 ms 5 ms 5 ms 10.103.32.1
2 5 ms 5 ms 6 ms dstswr1-vlan2.rh.prnynj.cv.net [67.83.242.33]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 9 ms 7 ms 7 ms vl3496.mpd03.jfk02.atlas.cogentco.com [154.54.6.49]
8 15 ms 13 ms 13 ms te7-3.mpd01.dca01.atlas.cogentco.com [154.54.3.45]
9 44 ms 39 ms 39 ms te7-3.mpd01.iah01.atlas.cogentco.com [154.54.2.246]
10 74 ms 74 ms 73 ms te7-4.mpd01.lax01.atlas.cogentco.com [154.54.2.198]
11 76 ms 75 ms 74 ms vl3492.mpd01.lax05.atlas.cogentco.com [154.54.3.10]
12 76 ms 75 ms 74 ms gr1-a350s3.sffca.ip.att.net [192.205.35.5]
13 75 ms 75 ms 76 ms tbr2.la2ca.ip.att.net [12.123.222.46]
14 75 ms 75 ms 74 ms 12.127.3.189
15 74 ms 75 ms 76 ms 12.122.255.74
16 77 ms 75 ms 75 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]
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. |
|
Quba
join:2003-08-20
Elizabeth, NJ
| reply to ansky08
yes unfortunately, this problem is not only with WOW, as it is happening with all of OOL's routing at this time. It appears CongestedCo lacks superior hardware and really stresses routers during peak hours. Im really glad that i came onto the forums because it's been a fight between me and OOL for the last 2 weeks. Lol, i've had more than 7 phone techs take logs of my intermittent lag and about 3 house visits, in which OOL keeps sending the SAME incompetent tech. I guess the best thing we can do is keep calling and pointing out that there is a routing issue. ALL I WANNA DO IS FRAG, WHY! |
|
NotCVsFault
@optonline.net
| reply to ansky08
All,
If you read the official WoW forums you'll see that it is not just OOL that is having this issue.
OOL has investigates all provided trace routes, and will continue to, but still sees the issue with AT&T and Cogentco.
They're working on it, trust me.. lots of the people who you complain to also play WoW.
There has been an innormous amount of complains with this, as you all can understand, it's major. But it's not just OOL, it's also Verizon, Time Warner, Cox Cable. Do the research and you'll see.
Even though it might not be OOL's "fault", they are still trying to work for a resolution to solve atleast their customers.
I would stop being so "hostile" towards OOL, as if it was them who caused all ISP's to have the same issue. |
|
ansky08
join:2005-07-11
New Milford, NJ | reply to ansky08
surprisingly, last night, I did not get the crazy latency and disconnects. knock on wood - hopefully things are wrapping up |
|
audious
join:2008-06-03 | Yes, last night was fine.
Did we get rerouted?
Did they feed the hamster? |
|
Quba
join:2003-08-20
Elizabeth, NJ
| incorrect, i was having huge disconnect problems with Ventrilo Chat as well as Counter-Strike. I live in Union County, NJ and after finding that i was still recieving packet loss and D/c.. i came to the conclusion of running a line quality test.
»/linequality/nil/2394630
It's nice to find out im 150ms to my FIRST hop.
its not OOLs fault? seems like a bunch of bullsnap to me. |
|
frdrizzt
join:2008-05-03
Farmingville, NY | Sounds like you're having problems unrelated to this topic. You may want to create your own or post to the direct forum if you're having packet loss problems. |
|
