High Latency, Optimum Online

Technical Support
Prev 1 2 3 4 9 Next
Tracing route to 63.240.104.93 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 13 ms 8 ms 10.240.161.49
3 12 ms 11 ms 7 ms 433be095.cst.lightpath.net [67.59.241.149]
4 11 ms 8 ms 9 ms rtr2-ge1-13.mhe.prnynj.cv.net [67.83.245.133]
5 11 ms 11 ms 11 ms 64.15.7.57
6 * * * Request timed out.
7 12 ms 9 ms 14 ms xe-9-1-2.edge2.Newark1.Level3.net [4.31.45.173]
8 10 ms 11 ms 16 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
9 13 ms 11 ms 11 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
10 10 ms 18 ms 11 ms ae-82-82.csw3.NewYork1.Level3.net [4.69.148.42]
11 35 ms 14 ms 9 ms ae-3-80.edge3.NewYork1.Level3.net [4.69.155.145]
12 316 ms 314 ms * att-level3.newyork1.level3.net [4.68.63.142]
13 327 ms 320 ms 315 ms cr1.n54ny.ip.att.net [12.122.131.102]
14 319 ms * 324 ms cr1.phlpa.ip.att.net [12.122.5.242]
15 314 ms 314 ms 314 ms 12.122.107.13
16 327 ms 324 ms 341 ms 12-122-254-242.attens.net [12.122.254.242]
17 330 ms 328 ms 326 ms mdf001c7613r0003-gig-10-1.nyc3.attens.net [63.240.65.10]
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 Mike-PC [192.168.1.2]
1 192.168.1.1
2 10.240.161.49
3 433be095.cst.lightpath.net [67.59.241.149]
4 rtr2-ge1-13.mhe.prnynj.cv.net [67.83.245.133]
5 65.19.119.197
6 * * *
Computing statistics for 125 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Mike-PC [192.168.1.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 11ms 90/ 100 = 90% 90/ 100 = 90% 10.240.161.49
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% 433be095.cst.lightpath.net [67.59.241.149]
0/ 100 = 0% |
4 11ms 0/ 100 = 0% 0/ 100 = 0% rtr2-ge1-13.mhe.prnynj.cv.net [67.83.245.133]
0/ 100 = 0% |
5 12ms 0/ 100 = 0% 0/ 100 = 0% 65.19.119.197

Trace complete.
Ysera. This all started after i got an update from the desktop launcher yesterday.

Tracing route to 199.107.6.200 over a maximum of 30 hops

1 1 ms <1 ms <1 ms openrg.home [Router]
2 8 ms 9 ms 9 ms Router
3 10 ms 9 ms 9 ms Router
4 13 ms 14 ms 11 ms rtr2-ge1-2.mhe.hcvlny.cv.net [67.83.220.5]
5 15 ms 14 ms 15 ms 451be0c9.cst.lightpath.net [65.19.99.201]
6 * * * Request timed out.
7 15 ms 20 ms 14 ms xe-11-3-2.edge2.Newark1.Level3.net [4.28.5.117]

8 16 ms 21 ms 17 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
9 13 ms 13 ms 13 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
10 16 ms 15 ms 15 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]

11 13 ms 13 ms 14 ms ae-4-90.edge3.NewYork1.Level3.net [4.69.155.209]

12 319 ms 317 ms 319 ms att-level3.newyork1.level3.net [4.68.63.142]
13 315 ms * 319 ms cr1.n54ny.ip.att.net [12.122.131.102]
14 317 ms 320 ms 318 ms cr1.phlpa.ip.att.net [12.122.5.242]
15 320 ms 317 ms 320 ms 12.122.107.13
16 457 ms 347 ms 341 ms 12-122-254-242.attens.net [12.122.254.242]
17 338 ms 437 ms 431 ms mdf001c7613r0003-gig-10-1.nyc3.attens.net [63.24
0.65.10]
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.
Zul'jin tracerouted to realm IP from north jersey

Tracing route to 195-12-232-70.customer.teliacarrier.com [195.12.232.70]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 130 ms 139 ms * 67.59.246.9
4 12 ms 13 ms 12 ms ool-4353f989.dyn.optonline.net [67.83.249.137]
5 14 ms 12 ms 12 ms 65.19.119.197
6 20 ms 19 ms 12 ms 64.15.3.226
7 * * * Request timed out.
8 11 ms 12 ms 11 ms nyk-bb1-link.telia.net [213.155.130.246]
9 111 ms 113 ms 187 ms prs-bb1-link.telia.net [80.91.253.121]
10 117 ms 133 ms 116 ms prs-b8-link.telia.net [213.155.131.9]
11 * * * Request timed out.
12 * * * Request timed out.
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.
Im currently on the phone with Optimum. It is an ATT issue. Blizzard apparently "rents" handoff servers from ATT, and if you look at your trace routes, this is where the issues begin as it leaves your ISP. Usually around hop 12.

So, with that in mind, here is the number for ATT that he tech guy gave me:

1-800-400-1447

It truly isnt our ISP, or Blizzard, but the idiots in between. Any old time players will tell you this happened about 4 or 5 years ago too and ATT was the culprit then as well.

Hope this helps. If its still like this tomorrow I'll be calling them as well.
Same prob here, for the past 2 nights my latency slowly starts climbing at 8 pm eastern. Im using Optimum online on long island. Heres my Tracert

Tracing route to 206.17.111.92 over a maximum of 30 hops

1 1 ms 5 ms <1 ms SEANSWIRELESS [192.168.1.1]
2 * * * Request timed out.
3 11 ms 9 ms 8 ms 67.59.234.181
4 14 ms 10 ms 12 ms rtr4-ge1-10.mhe.hcvlny.cv.net [167.206.39.137]
5 44 ms 17 ms 15 ms 451be0cd.cst.lightpath.net [65.19.99.205]
6 * * * Request timed out.
7 19 ms 16 ms 16 ms xe-9-1-2.edge2.Newark1.Level3.net [4.31.45.173]
8 17 ms 18 ms 16 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
9 17 ms 16 ms 15 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
10 17 ms 17 ms 32 ms ae-72-72.csw2.NewYork1.Level3.net [4.69.148.38]
11 16 ms 58 ms 15 ms ae-2-70.edge3.NewYork1.Level3.net [4.69.155.81]
12 318 ms 332 ms 317 ms att-level3.newyork1.level3.net [4.68.63.142]
13 324 ms 323 ms 324 ms cr2.n54ny.ip.att.net [12.122.130.170]
14 335 ms 327 ms 322 ms cr1.cb1ma.ip.att.net [12.122.31.126]
15 324 ms 321 ms 327 ms 12.122.145.73
16 336 ms 321 ms 321 ms 12.122.251.98
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.
Same deal. past 2 nights. Opt online user Westchester NY. Lets get this thing fixed plz
Central NJ, Optimum Online. When we called them they said that it was known issue with Battle.net and that we should contact Blizz. Hope this gets fixed soon.

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 9 ms 29 ms 29 ms 67.59.230.33
4 11 ms 9 ms 9 ms r3-ge1-1.mhe.prnynj.cv.net [67.83.249.13]
5 12 ms 13 ms 10 ms 64.15.7.37
6 * * * Request timed out.
7 34 ms 20 ms 11 ms xe-9-1-2.edge2.Newark1.Level3.net [4.31.45.173]
8 14 ms 13 ms 11 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
9 15 ms 10 ms 19 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
10 12 ms 13 ms 13 ms ae-72-72.csw2.NewYork1.Level3.net [4.69.148.38]
11 14 ms 53 ms 12 ms ae-2-70.edge3.NewYork1.Level3.net [4.69.155.81]
12 310 ms 313 ms 312 ms att-level3.newyork1.level3.net [4.68.63.142]
13 336 ms 340 ms 340 ms cr1.n54ny.ip.att.net [12.122.131.102]
14 342 ms 339 ms 336 ms cr2.cgcil.ip.att.net [12.122.1.2]
15 328 ms * 330 ms gar6.ipsin.ip.att.net [12.122.132.241]
16 333 ms 452 ms 332 ms 12.122.251.14
17 336 ms 351 ms 338 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 * * * 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.
gaaaaaaaaaahhhh
Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1 [192.168.1.1]
2 * * * Request timed out.
3 8 ms 9 ms 24 ms 67.59.234.213
4 13 ms 13 ms 11 ms rtr2-ge1-16.mhe.prnynj.cv.net [67.83.252.5]
5 13 ms 12 ms 12 ms 64.15.7.57
6 * * * Request timed out.
7 12 ms 11 ms 12 ms xe-9-1-2.edge2.Newark1.Level3.net [4.31.45.173]
8 15 ms 11 ms 12 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
9 29 ms 11 ms 12 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
10 13 ms 12 ms 28 ms ae-62-62.csw1.NewYork1.Level3.net [4.69.148.34]
11 12 ms 12 ms 11 ms ae-1-60.edge3.NewYork1.Level3.net [4.69.155.17]
12 317 ms 313 ms 317 ms att-level3.newyork1.level3.net [4.68.63.142]
13 410 ms 383 ms * cr1.n54ny.ip.att.net [12.122.131.102]
14 384 ms 386 ms * cr2.cgcil.ip.att.net [12.122.1.2]
15 383 ms 382 ms 380 ms cr1.cgcil.ip.att.net [12.122.2.53]
16 384 ms 383 ms 383 ms cr2.dvmco.ip.att.net [12.122.31.85]
17 386 ms 381 ms 400 ms cr1.slkut.ip.att.net [12.122.30.25]
18 399 ms 379 ms 399 ms cr2.la2ca.ip.att.net [12.122.30.30]
19 384 ms 403 ms 398 ms gar20.la2ca.ip.att.net [12.122.128.181]
20 380 ms 379 ms 395 ms 12-122-254-234.attens.net [12.122.254.234]
21 381 ms 380 ms 379 ms 206.16.68.54
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.
Brooklyn, NY, issue persisting, Optimum just told me tonight that it's Blizzard's problem, Blizzard telling us it's not their problem, let's play phone tag. Someone call me so I can curse at you and take my frustration out.
I also just contacted optimum -- central NJ customer as well :)

They stated it is a known issue: (duh)

The further stated that it is NOT an issue with any systems/servers on optimum (cablevisions) end....it is a "third party" issue. When I mentioned 'level3' as a possible culprit the tech was not aware of any issue with them , but instead said from what they can see it is an issue at blizzards' end ...she specifically mentioned world of warcraft ; but it is clear that it encompasses more than just the wow servers ....i am sure all of you noticed the very slow load times on all battle.net based websites as well....

I have been having these issues for 24 hours, only during evening hours, both last night and tonight (presently) ...averaging anywhere from 400 to over 1,000 ms latency.

I did contact optimum LAST night (12/3/2013) ; and specifically mentioned stability/latency issues with world of warcraft ; and they were not aware of any specific wow/blizzard related issues then , so clearly this has been something that is a fairly new issue as far as optimum is concerned.

When optimum stated that it was a third party issue, and based on this I can assume that they are not going to pursue anything further on their end without some incentive....

I hope that blizzard is actively working on this issue , and is partnering with the appropriate companies to get this fixed ASAP.... i am sure this is affecting MANY WOW customers as well, seeming that optimum is a prominent internet provider in the new York Metro area.... :)

...and to whine a bit more.... I have two WOW accounts i actively use; and this is the second night that raiding has been impossible for me ; i have resorted to carousing around ORG , increasing methane levels in the air, and causing minor earthquakes each step i take.
Im in new york and yeah the lag is terrible. Please fix this soon Blizzard, the game is unplayable.
Suffolk County, Long Island NY
Called Optimum - they said it has been deemed a World of Warcraft problem.

Tracing route to 206.16.235.43 over a maximum of 30 hops

1 41 ms 1 ms 9 ms Cisco62616 [192.168.1.1]
2 * * * Request timed out.
3 12 ms 39 ms 19 ms 67.59.234.145
4 14 ms 26 ms 32 ms rtr3-ge1-11.mhe.hcvlny.cv.net [167.206.33.129]
5 21 ms 26 ms 22 ms 451be0c5.cst.lightpath.net [65.19.99.197]
6 * * * Request timed out.
7 30 ms 19 ms 19 ms xe-10-1-0.edge2.Newark1.Level3.net [4.79.190.201]
8 30 ms 22 ms 26 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
9 31 ms 17 ms 29 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
10 14 ms 24 ms 29 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]
11 25 ms 24 ms 28 ms ae-4-90.edge3.NewYork1.Level3.net [4.69.155.209]
12 335 ms 328 ms 323 ms att-level3.newyork1.level3.net [4.68.63.142]
13 339 ms 349 ms 330 ms cr2.n54ny.ip.att.net [12.122.130.170]
14 338 ms 360 ms * cr2.wswdc.ip.att.net [12.122.3.38]
15 324 ms 328 ms 438 ms gar3.ascva.ip.att.net [12.122.113.89]
16 327 ms 329 ms 329 ms 12.122.251.198
17 327 ms 322 ms 336 ms 63.240.197.186
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.
I am glad its not just me and my equipment. I'm here in Huntington, LI with Optimum online with the same exact problem. infamous line 12! We can all rest easy (somewhat) that the problem is not us.

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 9 ms 23 ms 38 ms 67.59.227.57
4 10 ms 10 ms 9 ms rtr1-ge1-13.mhe.hcvlny.cv.net [167.206.34.129]
5 13 ms 12 ms 12 ms 451be071.cst.lightpath.net [65.19.99.113]
6 * * * Request timed out.
7 14 ms 14 ms 27 ms xe-9-1-2.edge2.Newark1.Level3.net [4.31.45.173]
8 12 ms 10 ms 28 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
9 14 ms 11 ms 13 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
10 27 ms 12 ms 27 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]
11 44 ms 16 ms 62 ms ae-4-90.edge3.NewYork1.Level3.net [4.69.155.209]
12 315 ms 317 ms 319 ms att-level3.newyork1.level3.net [4.68.63.142]
13 363 ms 334 ms 327 ms cr1.n54ny.ip.att.net [12.122.131.102]
14 339 ms 336 ms 332 ms cr2.cgcil.ip.att.net [12.122.1.2]
15 326 ms 328 ms * gar6.ipsin.ip.att.net [12.122.132.241]
16 332 ms 334 ms * 12.122.251.18
17 349 ms 353 ms 334 ms 63.240.130.206
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.
Same but in Pheonix, Az. Game completely unplayable w/Cox as internet provider.
Brooklyn,NY. Optimum online

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 9 ms 9 ms 10 ms 67.59.233.57
4 12 ms 11 ms 11 ms dstswr2-ge3-12.rh.nyk3ny.cv.net [67.83.221.14]
5 13 ms 23 ms 14 ms 451be0c1.cst.lightpath.net [65.19.99.193]
6 * * * Request timed out.
7 10 ms 13 ms 10 ms xe-10-1-0.edge2.Newark1.Level3.net [4.79.190.201]
8 14 ms 13 ms 13 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
9 13 ms 11 ms 13 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
10 14 ms 11 ms 13 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]
11 11 ms 11 ms 15 ms ae-4-90.edge3.NewYork1.Level3.net [4.69.155.209]
12 317 ms 327 ms 313 ms att-level3.newyork1.level3.net [4.68.63.142]
13 330 ms 336 ms 337 ms cr1.n54ny.ip.att.net [12.122.131.102]
14 333 ms 337 ms 337 ms cr2.cgcil.ip.att.net [12.122.1.2]
15 336 ms 411 ms 340 ms gar6.ipsin.ip.att.net [12.122.132.241]
16 398 ms 334 ms 334 ms 12.122.251.18
17 332 ms 336 ms 337 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 * * * 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.
Same issue - no connection issues outside of WoW. Austin, TX - Time Warner Cable.
Im currently on the phone with Optimum. It is an ATT issue. Blizzard apparently "rents" handoff servers from ATT, and if you look at your trace routes, this is where the issues begin as it leaves your ISP. Usually around hop 12.

So, with that in mind, here is the number for ATT that he tech guy gave me:

1-800-400-1447

It truly isnt our ISP, or Blizzard, but the idiots in between. Any old time players will tell you this happened about 4 or 5 years ago too and ATT was the culprit then as well.

Hope this helps. If its still like this tomorrow I'll be calling them as well.


Quoting this for emphasis. If my cell wasn't dead right now, I'd call them myself
I'm In Holbrook, for you other LI'ers here.

Technically, if what the tech at said Optimum is correct, it IS Blizzard's issue. They rent the servers from ATT. As paying customers, you would think they would get on the horn with ATT and get this taken care of. Kinda like what we are doing with our ISP and Blizzard.

But since they won't, we have to. The 800 number for ATT again is:

1-800-400-1447
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.

Join the Conversation

Return to Forum