High Latency, Optimum Online

Technical Support
Prev 1 3 4 5 9 Next
Well, add me to the list. I have has issues since Tuesday night, so has my husband. Router and drivers are all fine. It's just a WOW thing. Ran trace... yuck!

Tracing route to 63.240.104.93 over a maximum of 30 hops

1 * * * Request timed out.
2 9 ms 8 ms 38 ms 67.59.227.33
3 11 ms 8 ms 10 ms opti34-141.nassau.cv.net [167.206.34.141]
4 12 ms 11 ms 10 ms 451be0c1.cst.lightpath.net [65.19.99.193]
5 * * * Request timed out.
6 11 ms 12 ms 27 ms xe-10-1-0.edge2.Newark1.Level3.net [4.79.190.201]
7 11 ms 15 ms 14 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
8 13 ms 13 ms 10 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
9 11 ms 10 ms 15 ms ae-72-72.csw2.NewYork1.Level3.net [4.69.148.38]
10 13 ms 11 ms 11 ms ae-2-70.edge3.NewYork1.Level3.net [4.69.155.81]
11 315 ms 317 ms 327 ms att-level3.newyork1.level3.net [4.68.63.142]
12 318 ms 315 ms 317 ms cr1.n54ny.ip.att.net [12.122.131.102]
13 327 ms 326 ms 325 ms cr1.phlpa.ip.att.net [12.122.5.242]
14 322 ms 319 ms 311 ms 12.122.107.13
15 389 ms 419 ms 418 ms 12.122.251.2
16 325 ms 326 ms 319 ms mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.240.65.14]
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.
Tracing route to 63.240.104.93 over a maximum of 30 hops

0 chris_acer [192.168.0.197]
1 * * *
Computing statistics for 0 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 chris_acer [192.168.0.197]

Trace complete.
No, the issue is NOT with Optimum Online, and not technically AT&T either, unless AT&T leases equipment and bandwidth from Level 3 Communications (which is certainly possible).

The trouble point for everyone is the hop at: att-level3.newyork1.level3.net and then the hops thereafter that point. usually in the 300-400ms ping range.

Based on it ending in level3.net and if you research the IP; it shows the IP belongs to Level 3 communications, not AT&T. Now the att-level3 could mean either AT&T is leasing stuff from Level 3, OR that is the point in the network where Level 3 and AT&T meets. Again even the funny thing about the node is that it is named newyork1 but the server is actually physically located in KANSAS. This is probably why some other states and other ISPs other than Optimum Online are seeing the issue. This just happens to be a major node that links us all into the AT&T network that leads to the WOW servers (or at least a partial cluster of them).

I am on Gilneas which is in the Vindication battle group which is in 1 of the 2 Blizzard server datacenters located in Chicago, IL. The other battle group Ruin is also housed at the same location. While Shadowburn and Rampage are located at a separate datacenter still in Chicago, IL.

Either way, it's not really Blizzard's problem since it's at the AT&T or Level 3 segment, but however, usually when the bigger players get involved in this case Blizzard and Optimum Online and they put pressure on Level 3 and/or AT&T it has more weight and pushes for a faster resolution to the issue.

On the other hand Optimum should have some ability to route around the problem this can't be the only server node in all of North America that will link us to AT&T network, which is why I said earlier to contact Optimum and make the issue known. The more people that complain about it, the more likely they are to TRY to do something.

When I called today (12/4) at 6PM eastern they (Long Island/Nassau - Optimum) had no knowledge of the issue but the tech took a large amount of information from me, several tracerts and I also even linked him to several of the forums on here that mentioned the issues. He seemed like he wanted to help, and said he would forward all information to his bosses so that they can take the next steps. Granted that could be absolutely nothing, but I at least give him credit for taking all the info I had to supply to him.


If the node is located in Kansas, I wonder if the snowstorms passing through some parts of the state are responsible for the problems.
Finally a blue is admitting that they are at least looking into this issue. It may be outside of blizz's control but at the end of the day blizz will lose customers over this if it isn't fixed. Sorry but us pions will get no where with our ISP's and considering people are having issues across canada and the US there isn't anything an individual can do.

Thanks Dankorii for letting us know blizz is looking into it. Much better than leaving us in the dark or telling us there is nothing blizz can do. I gave you some good feedback Dankorii. thanks again.
Blizz support ticket is not working for me. I tried to send them my trace. It won't go through. So Blizzard, see my post from above with the info!!!

Optimum says its not their problem. So frustrating! No one wants to help!

By the way I am in Huntington, NY (Long Island)
Glad to know it wasn't anything on my end at least, had to raid through the lag yesterday because we couldn't get a replacement.
Although it is a bit odd to see so many people playing on Long Island in this thread, where are you all hiding? :P

And here's to hoping this is fixed soon.
Tracing route to 12.129.209.68 over a maximum of 30 hops

1 3 ms 4 ms 5 ms Cisco02088 [192.168.2.1]
2 * * * Request timed out.
3 17 ms 10 ms 19 ms 67.59.240.165
4 19 ms 11 ms 17 ms ool-4353f209.dyn.optonline.net [67.83.242.9]
5 14 ms 19 ms 19 ms 65.19.119.197
6 * * * Request timed out.
7 19 ms 12 ms 16 ms xe-11-3-2.edge2.Newark1.Level3.net [4.28.5.117]
8 14 ms 19 ms 29 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
9 12 ms 14 ms 10 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
10 24 ms 16 ms 17 ms ae-82-82.csw3.NewYork1.Level3.net [4.69.148.42]
11 14 ms 18 ms 20 ms ae-3-80.edge3.NewYork1.Level3.net [4.69.155.145]
12 199 ms 199 ms 199 ms att-level3.newyork1.level3.net [4.68.63.142]
13 264 ms 263 ms 266 ms cr1.n54ny.ip.att.net [12.122.131.102]
14 256 ms 264 ms 279 ms cr2.cgcil.ip.att.net [12.122.1.2]
15 267 ms 269 ms 264 ms cr1.cgcil.ip.att.net [12.122.2.53]
16 262 ms 274 ms 264 ms cr2.dvmco.ip.att.net [12.122.31.85]
17 324 ms 281 ms 264 ms cr1.slkut.ip.att.net [12.122.30.25]
18 280 ms 266 ms 264 ms cr2.la2ca.ip.att.net [12.122.30.30]
19 259 ms 258 ms 256 ms gar20.la2ca.ip.att.net [12.122.128.181]
20 265 ms 265 ms 255 ms 12-122-254-234.attens.net [12.122.254.234]
21 261 ms 265 ms 269 ms 206.16.68.46
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.

Well what do you know AT&T New York. I'm located in Parsippany NJ
taught i update, MS its gradually going down, as the night goes on, its now at 140MS down from 400 all day
tracert route as of 1:20am eastern time

C:\Windows\system32>tracert 63.240.161.189

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms openrg.home [192.168.1.1]
2 11 ms 8 ms 7 ms 10.240.176.129
3 9 ms 7 ms 7 ms r2-ge2-1.in.asbnva16.cv.net [65.19.98.1]
4 11 ms 10 ms 9 ms rtr2-ge1-15.mhe.whplny.cv.net [67.83.232.5]
5 14 ms 13 ms 13 ms 65.19.121.41
6 * * * Request timed out.
7 12 ms 12 ms 72 ms xe-10-1-0.edge2.Newark1.Level3.net [4.79.190.201
]
8 12 ms 13 ms 14 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
9 12 ms 12 ms 12 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
10 13 ms 13 ms 14 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]

11 16 ms 12 ms 12 ms ae-4-90.edge3.NewYork1.Level3.net [4.69.155.209]

12 113 ms 104 ms 106 ms att-level3.newyork1.level3.net [4.68.63.142]
13 126 ms 125 ms 123 ms cr1.n54ny.ip.att.net [12.122.131.102]
14 123 ms 122 ms 126 ms cr2.cgcil.ip.att.net [12.122.1.2]
15 125 ms 122 ms 120 ms gar6.ipsin.ip.att.net [12.122.132.241]
16 126 ms 127 ms 141 ms 12.122.251.14
17 176 ms 121 ms 122 ms 63.240.130.202
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 * *
Same here Magikarp;

Since around 12:30ish (eastern) my ping has been gradually dropping, it is now hovering around 110-120ms which is vast improvement over earlier when I was in the 350-400 range, however it is still not back to normal which is usually in the 30-40ms range.

However, (hate to disappoint) but don't get too excited b/c it did the SAME EXACT thing last night. It got really bad after roughly 6PM on 12/3 and got "better" after 1am and has now repeated this same pattern today 12/4.

It seems to be a "capacity" issue (guessing) based on the abnormally high pings during "peak" hours and normal pings during "non-peak" hours. Not to say that storms or weather issues could be related as someone mentioned earlier but if it was truly weather related it wouldn't get better then get worse as peak time approaches again, then get better as we reach non-peak time again. Either there is some recent addition to the network that is saturating their bandwidth and causing major congestion on their network or there is a piece of hardware that is malfunctioning and is only showing issue during "stress" or "peak times.

Still hoping for a solution to this...
Ya I am also a optimum service user, been having problems since tuesday around 6 pm.
Its not great because I havent been able to raid at all, because my ms will be 400+. I called optimum and it they helped me run a tracert, and it shows the same as you guys. I have some issue with level 3 server, that is where the MS gets higher, I hope blizzard does something about this. I would like to raid tomorrow (thursday).
For those asking about FIOS... doesn't seem to go through level3 although some of the other AT&T servers line up.

1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 7 ms 8 ms L100.NWRKNJ-VFTTP-97.verizon-gni.net [98.109.75.1]
3 18 ms 8 ms 12 ms G1-3-3-0.NWRKNJ-LCR-21.verizon-gni.net [130.81.32.74]
4 9 ms 6 ms 12 ms ae0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.209.154]
5 48 ms 15 ms 16 ms 0.xe-9-0-0.BR2.NYC4.ALTER.NET [152.63.20.189]
6 16 ms 24 ms 14 ms 192.205.34.49
7 29 ms 31 ms 33 ms cr1.n54ny.ip.att.net [12.122.105.14]
8 34 ms 31 ms 29 ms cr2.cgcil.ip.att.net [12.122.1.2]
9 30 ms 31 ms 30 ms gar6.ipsin.ip.att.net [12.122.132.241]
10 32 ms 31 ms 32 ms 12.122.251.14
11 32 ms 33 ms 32 ms 63.240.130.206
12 * * * Request timed out.
13 * * * Request timed out.
Good news is my connection is back to its usual 75-80 ms both home and world. The troublesome IP address (4.68.63.142) is now responding at a FAR faster ping now, so I have to assume the problem is fixed for now. Hope the issues don't happen again tomorrow.

BTW, this is from Central New Jersey/Optimum Online.


Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 18 ms 10 ms 8 ms 67.59.226.141
4 10 ms 10 ms 9 ms ool-4353fa09.dyn.optonline.net [67.83.250.9]
5 12 ms 15 ms 12 ms 65.19.119.217
6 * * * Request timed out.
7 13 ms 11 ms 13 ms xe-10-1-0.edge2.Newark1.Level3.net [4.79.190.201]
8 11 ms 11 ms 11 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
9 12 ms 16 ms 12 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
10 12 ms 11 ms 11 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]
11 11 ms 11 ms 12 ms ae-4-90.edge3.NewYork1.Level3.net [4.69.155.209]
12 14 ms 14 ms 15 ms att-level3.newyork1.level3.net [4.68.63.142]
13 77 ms 75 ms 75 ms cr2.n54ny.ip.att.net [12.122.130.170]
14 77 ms 78 ms 93 ms cr2.wswdc.ip.att.net [12.122.3.38]
15 76 ms 79 ms 79 ms cr1.attga.ip.att.net [12.122.1.173]
16 84 ms 118 ms 85 ms cr2.dlstx.ip.att.net [12.122.28.174]
17 77 ms 79 ms 78 ms cr1.dlstx.ip.att.net [12.122.1.209]
18 77 ms 78 ms 76 ms cr1.phmaz.ip.att.net [12.122.28.182]
19 74 ms 73 ms 73 ms 12.123.158.5
20 76 ms 74 ms 75 ms 12-122-254-218.attens.net [12.122.254.218]
21 77 ms 75 ms 75 ms mdf002c7613r0002-gig-12-1.phx1.attens.net [63.241.130.202]
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.
Time to switch to Fios!

For those of you that says the latency is normalizing, what time of night is it? Thursday morning my ms was normal at 32. 5pm it went back to 336ms then by 9pm it was red and over 700.... is it just spiking during peak hours and going back down when no one is around or is it fixed?
Im from Brooklyn NY. My internet is fine its just WoW . :(

Tuesday at around 7-8 My friend said he had an update so i logged out of WoW i got the update then after that WoW was laggy as hell.
I posted in a previous thread about it, but here's my info.

Tracing route to 63.240.104.93 over a maximum of 30 hops

1 1 ms 3 ms 1 ms openrg.home [192.168.1.1]
2 * * * Request timed out.
3 11 ms 10 ms 11 ms 67.59.245.133
4 13 ms 14 ms 10 ms ool-4353f68d.dyn.optonline.net [67.83.246.141]
5 29 ms 13 ms 11 ms 65.19.119.193
6 * * * Request timed out.
7 22 ms 15 ms 16 ms xe-9-1-3.edge2.Newark1.Level3.net [4.30.130.237]
8 14 ms 17 ms 14 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
9 14 ms 13 ms 23 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
10 16 ms 21 ms 32 ms ae-62-62.csw1.NewYork1.Level3.net [4.69.148.34]
11 22 ms 18 ms 13 ms ae-1-60.edge3.NewYork1.Level3.net [4.69.155.17]
12 16 ms 24 ms 21 ms att-level3.newyork1.level3.net [4.68.63.142]
13 20 ms 22 ms 24 ms cr1.n54ny.ip.att.net [12.122.131.102]
14 23 ms 22 ms 25 ms cr1.phlpa.ip.att.net [12.122.5.242]
15 17 ms 18 ms 16 ms 12.122.107.13
16 28 ms 33 ms 26 ms 12-122-254-242.attens.net [12.122.254.242]
17 48 ms 24 ms 25 ms mdf001c7613r0003-gig-10-1.nyc3.attens.net [63.240.65.10]
18 * * * Request timed out.
19 * * * Request timed out.
20 *

I will copy and paste what I posted before as well.

"I contacted Optimum about this. They said that, well for me at least, the problem lies with AT&T over in San Diego. Apparently their servers are unresponsive or something, and that's what the cause of the problem is. May be the same for Thialina. I had to contact ATT, they asked me to send an email with the Trace Route so they can see what is going on. In any case...you folks over at Blizzard should also be taking a look at this...this is very frustrating considering I can't really go quest and play on any characters between the levels of 58-68."

So yeah, I guess I'm not the only one that was told AT&T is the problem.

My problem is a bit different from you all though, I wasn't only experiencing some terrbad lag. But also, I couldn't go into outlands. I kept getting the "Transfer Aborted: instance not found" error. Going to try it now and see what happens, seems like a lot of folks are contacting these guys about this now.

I'm from Bayonne, NJ btw.
It cant be on blizz's end because the other night i was lagging too hard on WoW so i figured id try a round of League of legends. Same thing, HUGE latency issues.......
Im from br

My favorite part is that my internet is literally !@#$ right now, not even JUST WoW.

The issue started yesterday, around 5-6 PM (EST)

I can't even %^-*ing load my browser, took 5 minutes to get back to this page and post this comment. I feel like Optimum is just !@#$ters. Constant issues with them.


Im from Brooklyn NY. My internet is fine its just WoW . :(

Tuesday at around 7-8 My friend said he had an update so i logged out of WoW i got the update then after that WoW was laggy as hell.


Im in Babylon and I raid with a guy from Queens. he has time warner and everything is fine. I have OptimumOnline (cablevision) and have the same problem as every other poster here.... is it by region/town? Brooklyn is 20 minutes without traffic. other have said they have time warner as well with issues. how is Queens un affected?
Hey all,

Thank you for providing the requested tracerts. Our admins have diagnosed the cause of this issue and are currently working with the ISPs involved in order to resolve this as soon as possible.
______________________________________________________
I'm available Monday through Friday from 11AM to 8PM Pacific Time
Support Contact Information

Got some feedback? https://www.surveymonkey.com/s/Dankorii

Join the Conversation

Return to Forum