Camanon
@optonline.net
| reply to ansky08
Re: Lag, Disconnecting in World of Warcraft
I'm getting the spikes (packetloss) between Long Island Optimum and two desinations: a Cogent datacenter in DC and Blizzard's AT&T in LA.
Cogent in Virginia:
tracert 38.100.11.1
Tracing route to gi9-12.mpd01.iad03.atlas.cogentco.com [38.100.11.1]
over a maximum of 30 hops:
1 11 ms 9 ms 12 ms 10.240.160.121
2 8 ms 9 ms 8 ms dstswr1-vlan2.rh.stjmny.cv.net [167.206.39.161]
3 * * * Request timed out.
4 21 ms 14 ms 11 ms rtr3-tg10-3.wan.hcvlny.cv.net [64.15.4.9]
5 * * * Request timed out.
6 * * * Request timed out.
7 10 ms 10 ms 9 ms te9-2.ccr04.jfk02.atlas.cogentco.com [130.117.0.53]
8 26 ms 14 ms 17 ms te2-1.ccr02.dca01.atlas.cogentco.com [154.54.6.13]
9 16 ms 31 ms 17 ms te4-1.mpd01.dca02.atlas.cogentco.com [154.54.2.182]
10 20 ms 18 ms 25 ms gi9-12.mpd01.iad03.atlas.cogentco.com [38.100.11.1]
Trace complete.
...
Reply from 38.100.11.1: bytes=32 time=17ms TTL=245
Reply from 38.100.11.1: bytes=32 time=16ms TTL=245
Reply from 38.100.11.1: bytes=32 time=17ms TTL=245
Reply from 38.100.11.1: bytes=32 time=19ms TTL=245
Request timed out.
Request timed out.
Reply from 38.100.11.1: bytes=32 time=19ms TTL=245
Reply from 38.100.11.1: bytes=32 time=22ms TTL=245
Reply from 38.100.11.1: bytes=32 time=25ms TTL=245
...
AT&T in LA:
tracert 12.129.193.246
Tracing route to mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]
over a maximum of 30 hops:
1 8 ms 7 ms 7 ms 10.240.160.121
2 10 ms 9 ms 16 ms dstswr1-vlan2.rh.stjmny.cv.net [167.206.39.161]
3 * * * Request timed out.
4 8 ms 9 ms 7 ms rtr4-tg10-3.wan.hcvlny.cv.net [64.15.4.33]
5 * * * Request timed out.
6 * * * Request timed out.
7 12 ms 11 ms 12 ms vl3492.mpd03.jfk02.atlas.cogentco.com [154.54.7.13]
8 161 ms 221 ms 219 ms te8-3.mpd01.dca01.atlas.cogentco.com [154.54.5.98]
9 43 ms 43 ms 50 ms te2-2.mpd01.iah01.atlas.cogentco.com [154.54.2.146]
10 77 ms 79 ms 153 ms te4-4.mpd01.lax01.atlas.cogentco.com [154.54.5.102]
11 77 ms 83 ms 83 ms vl3493.mpd01.lax05.atlas.cogentco.com [154.54.6.230]
12 78 ms 76 ms 81 ms gr1-a350s3.sffca.ip.att.net [192.205.35.5]
13 79 ms 78 ms 83 ms tbr2.la2ca.ip.att.net [12.123.222.30]
14 76 ms 78 ms 87 ms 12.127.3.189
15 78 ms 77 ms 77 ms 12.122.255.74
16 83 ms 78 ms 78 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]
Trace complete.
...
Reply from 12.129.193.246: bytes=32 time=77ms TTL=240
Reply from 12.129.193.246: bytes=32 time=78ms TTL=240
Reply from 12.129.193.246: bytes=32 time=78ms TTL=240
Reply from 12.129.193.246: bytes=32 time=83ms TTL=240
Reply from 12.129.193.246: bytes=32 time=78ms TTL=240
Reply from 12.129.193.246: bytes=32 time=77ms TTL=240
Request timed out.
Request timed out.
Reply from 12.129.193.246: bytes=32 time=78ms TTL=240
Reply from 12.129.193.246: bytes=32 time=79ms TTL=240
Reply from 12.129.193.246: bytes=32 time=91ms TTL=240
...
The two "Request timed out" are concurrent.
The tracert's don't show the actual problem, just the current routes. Both are currently exhibiting symptoms where they cause 5-8 seconds of packetloss every 5 minutes or so. This has been happening on and off, to greater and lesser degrees of severity, for the past 3 weeks.
Assuming CV and Cogent are peering in NY I'm not sure how AT&T is the problem, or at least the only problem. |
|
TheWiseGuy
Dog And Butterfly
Premium,MVM
join:2002-07-04
Yonkers, NY
| You can use a more thorough tracert utility to help find where the problem is located. Here are 2 freeware utilities, that will allow you to configure them to run for more than 3 packets per hop and may help determine where the problem is for WoW. Given the size of the Internet I would not be surprised if at any point in time there was more then one problem occurring somewhere with a router. The final link is to the Internet traffic report which also gives some info on where problems are occurring.
»www.pingplotter.com/freeware.html
»www.foundstone.com/us/resources/···rout.htm
»www.internettrafficreport.com/namerica.htm
--
Warning, If you post nonsense and use misinformation and are here to argue based on those methods, you will be put on ignore. |
|
rebecca191
join:2008-05-18
Fairfield, CT
1 edit | reply to ansky08
Camanon - I've seen it spike high at cablevisionm, cogentco, and attens, so there may be a problem with how all 3 are routing.  Cogentco appears to dropping 10% of my packets ATM but everything's pinging lower then it was earlier today. |
|
digi
@optonline.net
| reply to Akka
Unfortunately, this problem is still a problem. The threads on blizzard's wow forums still have people reporting problems by the hour.
Tracert below, also please keep in mind that the problem is highly intermittent (in between lag events my in-game server latency is 150ms) and it's pretty unlikely that this tracert is illustrating any packet loss.
Tracing route to 206.17.111.123 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.1
2 11 ms 9 ms 8 ms 10.95.192.1
3 7 ms 9 ms 7 ms dstswr2-vlan2.rh.wrrnnj.cv.net [67.83.251.162]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 11 ms 13 ms 13 ms vl3491.ccr04.jfk02.atlas.cogentco.com [154.54.7.
9]
9 17 ms 21 ms 17 ms te8-2.ccr02.dca01.atlas.cogentco.com [66.28.4.12
6]
10 17 ms 17 ms 16 ms te7-3.mpd01.dca02.atlas.cogentco.com [154.54.6.2
6]
11 18 ms 15 ms 18 ms vl3497.mpd01.iad01.atlas.cogentco.com [154.54.5.
66]
12 19 ms 17 ms 19 ms 192.205.35.105
13 30 ms 32 ms 31 ms tbr1.wswdc.ip.att.net [12.122.80.58]
14 29 ms 28 ms 30 ms cr2.wswdc.ip.att.net [12.122.16.61]
15 31 ms 31 ms 30 ms cr2.n54ny.ip.att.net [12.122.3.37]
16 29 ms 32 ms 28 ms cr1.cb1ma.ip.att.net [12.122.31.126]
17 29 ms 30 ms 30 ms tbr1.cb1ma.ip.att.net [12.122.20.130]
18 30 ms 47 ms 34 ms 12.127.5.93
19 30 ms 31 ms 29 ms 12-122-254-14.attens.net [12.122.254.14]
20 176 ms 203 ms 200 ms mdf001c7613r0003-gig-10-1.bos1.attens.net [12.13
0.0.170]
21 * * * Request timed out.
|
|
Camanon
@optonline.net
| reply to rebecca191
Using PingPlotter:
Target Name: gi9-12.mpd01.iad03.atlas.cogentco.com
IP: 38.100.11.1
Date/Time: 6/5/2008 5:52:38 PM to 6/5/2008 5:57:39 PM
Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 299 0 0.0 5 28 8 [10.240.160.121]
2 299 0 0.0 5 32 9 dstswr1-vlan2.rh.stjmny.cv.net [167.206.39.161]
3 299 299 100.0 0 0 0 [-]
4 299 0 0.0 6 216 15 rtr3-tg10-3.wan.hcvlny.cv.net [64.15.4.9]
5 299 299 100.0 0 0 0 [-]
6 299 299 100.0 0 0 0 [-]
7 299 10 3.3 8 217 14 te9-2.ccr04.jfk02.atlas.cogentco.com [130.117.0.53]
8 299 11 3.7 14 340 28 te2-1.ccr02.dca01.atlas.cogentco.com [154.54.6.13]
9 299 8 2.7 15 275 28 te4-1.mpd01.dca02.atlas.cogentco.com [154.54.2.182]
10 299 7 2.3 15 233 21 gi9-12.mpd01.iad03.atlas.cogentco.com [38.100.11.1]
I'm not sure what the hop before 130.117.0.53 (te9-2.ccr04.jfk02.atlas.cogentco.com) is, but it's clear that the issue is happening at or before that router - perhaps the CV/Cogent handoff?
Any Optimum tech able to further investigate, surely you'd have a better idea what the hops between 64.15.4.9 (trouble free) and 130.117.0.53 (problematic) are? If you need any further information please don't hesitate to ask, though given the trace I'd think that OOL has sufficient data to locate the issue.
rebecca191: your spikes on the later hops can be caused by problems occurring before you reach them. |
|
rebecca191
join:2008-05-18
Fairfield, CT
1 edit | Camanon - yeah, I'm thinking it's something with Cognetco that is causing the problem. Although ocasionally I'll see a spike before it gets there, 99% of the time the lag seems to start there. Please take a look at Cogentco connections if anyone from OOL is reading this thread.
Mainly the problems start from rtr4-tg11-2.wan.whplny.cv.net [64.15.8.25] to vl3495.ccr04.jfk02.atlas.cogentco.com [154.54.6.45]
Also seeing lag spikes then at the following congentco IPs as well:
te3-3.ccr02.dca01.atlas.cogentco.com [154.54.5.246]
te4-3.mpd01.dca02.atlas.cogentco.com [154.54.7.2]
vl3496.mpd01.iad01.atlas.cogentco.com [154.54.5.46]
Not sure if it's getting worse there or just continuing the problem from the initial packet loss/lag spike from 64.15.8.25 to 154.54.6.45 |
|
digi
@optonline.net
| reply to digi
I ran two simultaneous pings to two different destinations along my tracert above until I found a spot where packets continue to pass normally on one and are lost downstream on another. As you can (hopefully) see in the attachment, the packets are lost between 67.83.251.162 (hop 3) and 192.205.35.105 (hop 12). Unfortunately none of the intermediate hops (cogent's routers) respond to pings, so I can't run the same test to narrow it down. However, its obvious from this that the problem occurs *before* att and after ool. As you can see, the period of dropped packets is very short (3-4 seconds max) and the occurrence of these 'lag events' is few and far between (every 5 or 10 minutes), so it will be difficult to pick up on many diagnostic tools. |
|
rebecca191
join:2008-05-18
Fairfield, CT
1 edit | reply to ansky08
I just got off the phone with OOL. It's definitley happening at Cogentco. The tech watched my route for a few mins and then he found the phone number the offending IPs belong to but... he said he can't call. WTF? do I have to speak to a higher up at OOL to have them call this number? |
|
digi
@optonline.net
| I sent an e-mail to cogent which I'm sure will have all the effect of pissing into the wind, what with me being just some guy with a g-mail account. At least now they'll be aware of the problem, however, if their spam filter doesn't just trash it ;p |
|
rebecca191
join:2008-05-18
Fairfield, CT | reply to ansky08
I have their phone number around here somewhere, I just don't see the point in calling them since I'm not their customer. |
|
digi
@optonline.net | Yes, any phone call to tech support would get as far as 'what's your account number'. |
|
rebecca191
join:2008-05-18
Fairfield, CT | I'm trying to get a tech at OOL who has the authority to open a ticket or report the problem to Cogentco. |
|
digi
@optonline.net | any luck? do you have the IP of the offending router or is it more than one? |
|
rebecca191
join:2008-05-18
Fairfield, CT
1 edit | Basically every Cogentco router was giving me high pings when a spike happened, but the tech I had spoken to initially wasn't sure if they were all having problems or it was just a continuation of the lag from the very first hop to Cogentco.
It starts at 154.54.6.45 on my traces.
The people on the phone I've tried talking to claim they have no responsibility and aren't routing me to Cogentco - then who is? Why is there no communication between the techs here and the people when you call OOL? Who is right - is it being worked on, or not? |
|
digi
@optonline.net
| I haven't gotten a response from my e-mail so I'm assuming cogent is going to ignore me. The dumb thing is that even if they acknowledge the packet loss, its probably too low to violate any kind of terms of service, so they likely wouldn't be under any obligation to fix it anyway.
I suppose if they say they're not routing you through cogent there might be another intermediary (one of those that doesn't respond to tracert and therefore doesn't show up). I can't imagine that they don't have any control over where their packets get routed -- after all, if that faulty router actually went down they would find a way to get the packets through.
Have you threatened to change service providers? That's what I'll ultimately have to do when I call them. |
|
rebecca191
join:2008-05-18
Fairfield, CT | Or they could just be dumb phone tech people. Hard to say. |
|
NiZZ
@optonline.net
| reply to ansky08
Tracing route to 12.129.233.127 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 12.129.233.127
2 * * * Request timed out.
3 33 ms 45 ms 42 ms opti33-162.nassau.cv.net [167.206.33.162]
4 36 ms 34 ms 28 ms rtr4-ge1-11.mhe.hcvlny.cv.net [167.206.33.133]
5 32 ms 32 ms 34 ms rtr3-tg11-3.wan.hcvlny.cv.net [64.15.4.13]
6 * * * Request timed out.
7 * * * Request timed out.
8 37 ms 31 ms 33 ms vl3496.mpd03.jfk02.atlas.cogentco.com [154.54.6.49]
9 52 ms 49 ms 51 ms te7-3.mpd01.dca01.atlas.cogentco.com [154.54.3.45]
10 67 ms 89 ms 71 ms te7-3.mpd01.iah01.atlas.cogentco.com [154.54.2.246]
11 101 ms 98 ms 98 ms te7-4.mpd01.lax01.atlas.cogentco.com [154.54.2.198]
12 99 ms 126 ms 99 ms vl3492.mpd01.lax05.atlas.cogentco.com [154.54.3.10]
13 106 ms 99 ms 162 ms gr1-a350s3.sffca.ip.att.net [192.205.35.5]
14 111 ms 100 ms 122 ms tbr2.la2ca.ip.att.net [12.123.222.30]
15 105 ms 111 ms 99 ms 12.127.3.189
16 104 ms 122 ms 115 ms 12.122.255.74
17 101 ms 101 ms 122 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.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.
The lag is really destroying any chance I have at playing. This is really stupid......... |
|
frdrizzt
join:2008-05-03
Farmingville, NY
 ·Optimum Online
| Cablevision had done a lot of tests with the information given, and has confirmed by the networking team that the issue is off their network, and they advise you to contact Blizzard/World of Warcraft for further troubleshooting.
Just updating you on the info CV has provided for us. Don't shoot the messanger. |
|
digi
@optonline.net
| On the other hand, this is the response I received just today from the trouble ticket I filed yesterday with OOL:
"Thank you for contacting Optimum Online regarding your question about online gaming. We apologize for any inconvenience this may have caused you and will be happy to assist.
Thank you for your email. I have attached the information to your account and escalated this over to our Communications Desk for further review."
Since I haven't received an update on this ticket I can only assume that it is still being worked on. This kind of highlights the worst part of this entire experience, which is that we're consistently getting two different answers from OOL. |
|
digi
@optonline.net
| reply to frdrizzt
For anyone else still concerned about this problem, OOL is in fact still looking into it despite their somewhat ominous sounding immediate response. They really are a pretty good service provider. Names have been changed to protect the innocent, and I apologize for the wall of text below, but I think it really clears the matter up of what they are and aren't doing.
---
OOL: I see, what would you like to add to the ticket?
digi: i'm just looking for a status update on it if available, is it still open and being investigated?
OOL: As of this time the issue is still open. It has been confirmed by our Networking team that the issue is with the World of War Craft site. Please contact World of Warcraft for further troubleshooting. That is the latest update that I have sir. I truly apologize for the inconvenience.Can I assist with anything else regarding Optimum Online?
digi: In my troubleshooting I have found that the problem is before the warcraft site, on an intermediary router owned by Cogent Communications
digi: obviously I have already contacted the owners of warcraft and they confirmed that the problem is not on their network
digi: i've heard a few different responses from friends who have filed trouble tickets with OOL ; some of them say that OOL has stopped working on the problem, can you confirm that an alternate routing solution is still being investigated by your engineers?
OOL: That is fine but we do not control the router owned by Cogent Communications. We can only comment on anything on the Cablevision network. You can contact the World of Warcraft site and they can contact Cogent Communications. Again I truly apologize for the inconvenience.Can I assist with anything else regarding Optimum Online?
digi: i'm sorry, but unfortunately I pay world of warcraft for gaming services and I pay you guys for network connectivity
OOL: We provide your Internet connection. Are you able to access the Internet?
digi: I understand that OOL has control over which intermediary routers my packets are routed through to reach an end destination, and if OOL is routing my packets through a router with a known defect then I feel it is your responsibility to rectify the situation if possible
digi: i haven't had any problems whatsoever with my service, and I understand it isn't your hardware that has the problem
OOL: Again I truly apologize for the inconvenience. Can I assist with anything else regarding Optimum Online?
digi: but if you guys can't help me rectify it i'll have to start looking for another service provider that will
digi: i'm sure you understand the situation
digi: do you have a supervisor that you can refer me to?
OOL: I understand and I truly apologize for the inconvenience. Would like like to speak to a Supervisior?
digi: yes, please -- thanks mario, I know this issue is a pain in the ass
OOL: Hello sir, my name is Mrs. X and I am a supervisor in Technical Support.
digi: hi there
OOL: Hello I understand you have a question about the connectivity of World of War Craft. Is that correct?
digi: that's right, i have an open ticket
OOL: I see that we have an outage posted for this issue and it was determined that the lack connectivity is on a network that does not belong to Cablevision.
OOL: The issue resides on the side of Blizzard.
digi: that's right, it seems to be a problem with an intermediate router owned by Cogent Communications
digi: i don't think that's entirely accurate, the problem seems to be before the packets hit blizzard's network
digi: cogent is the intermediary between OOL and ATT (blizzard's service provider)
OOL: Cogentco piggy backs to the ATT network and this is where the issue resides.
digi: right, in Cogent's hardware
digi: I don't believe Cogent is associated with Blizzard's service provider, are they?
OOL: I was just researching this just prior to this conversation and for any course of action that we can take to assist customers in this.
OOL: No,
digi: are you guys working on an alternate route to bypass the defective routers, or currently in communication with Cogent?
OOL: Blizzard uses ATT for the provider and the backbone for the connection is with Cogentco. Cogentco consistently has issues .
digi: right
digi: so I'm as right to contact you about this as Blizzard is to contact ATT
digi: since the problem is on a third party router not associated with either of our service providers
OOL: We have been working to get this resolved. The information that I am passing to you is from another supervisor that also plays WOW.
digi: okay, so you guys are still working on it?
OOL: I can promise you that we are working on this.
digi: that's really all I'm trying to find out
digi: hehe okay, good
digi: you don't have an estimated timeframe, do you?
OOL: There are currently around 150 people in this call center that all play and are being affected as well.
digi: it really is a pretty annoying problem
OOL: For the timeframe, unfortunately, I do not have an exact answer.
OOL: It is a very annoying problem and can sympathize with you in this matter.
digi: that's fine, like I said I was just trying to get to the bottom of the situation and make sure that something is still being done
OOL: I understand and I know that everyone here involved is working their hardest to come to a resolution.
digi: thank you for your time
OOL: You are more than welcome and I hope that this is resolved as quickly as possible for you and everyone else.
digi: yeah me too -- thanks again, and take care |
|
