http://www.dslreports.com/forum/r20796741 en Tue, 02 Dec 2008 05:27:15 EDT Tue, 02 Dec 2008 05:27:15 EDT http://www.dslreports.com/forum/remark,20803949 madmax2000 : Your saying you have latency issues on this hop, as you notice you are effected once it hits hop number 13, this dose not mean it is in sudden links network as the route going out to the network is under 60ms till it hits choopa networks in Newark.

You may want to contact the game server provider
to inform them you are having latency issues to their servers and it seems its on their edge router to level3 networks.

Once it hits choopa networks edge it has a high increase in response time as this could mean a high volume router or the priority on their edge router is set to a low level for icmp traffic for trace route/ping

9 27 ms 20 ms 16 ms vlan89.csw3.Washington1.Level3.net [4.68.17.190]

10 29 ms 17 ms 19 ms ae-83-83.ebr3.Washington1.Level3.net [4.69.134.1
69]
11 34 ms 31 ms 36 ms ae-4.ebr2.Newark1.Level3.net [4.69.132.102]
12 27 ms 22 ms 25 ms ae-21-56.car1.Newark1.Level3.net [4.68.99.165]
13 96 ms 93 ms 95 ms CHOOPA-LLC.car1.Newark1.Level3.net [4.79.189.182]]> http://www.dslreports.com/forum/remark,20803949 Thu, 17 Jul 2008 00:57:38 EDT http://www.dslreports.com/forum/remark,20798299 anklosaur : You probably won't get much help, but there is a customer service number here

»www.level3.com/about_us/contact_···dex.html

Normally, they would only accept inquiries from the direct peer. So, you complain to Suddenlink, they complain to Level 3 Communications. But you have to really work hard to get that kind of support. Normally the Suddenlink tech will say "It's Level 3, not us, nothing we can do." which is not true, but expedient. Good luck.]]> http://www.dslreports.com/forum/remark,20798299 Wed, 16 Jul 2008 01:16:50 EDT http://www.dslreports.com/forum/remark,20796741 Kenrin : seems like the next to the last hop is making my ping horrible to a lot of the gameservers located in that city. I've tried looking for a level3 email address to contact but did not find any. What to do?

tracert 208.167.247.103

Tracing route to 208.167.247.103 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.2.1
2 * * * Request timed out.
3 * 6 ms 8 ms s66-76-168-197.bssr.suddenlink.net [66.76.168.19
7]
4 7 ms 6 ms 6 ms s66-76-168-209.bssr.suddenlink.net [66.76.168.20
9]
5 18 ms 16 ms 15 ms s66-76-168-1.bssr.suddenlink.net [66.76.168.1]
6 18 ms 17 ms 20 ms 207.88.183.41.ptr.us.xo.net [207.88.183.41]
7 20 ms 18 ms 18 ms 65.106.3.185.ptr.us.xo.net [65.106.3.185]
8 17 ms 18 ms 17 ms te-7-1.car1.Washington3.Level3.net [4.71.204.25]

9 27 ms 20 ms 16 ms vlan89.csw3.Washington1.Level3.net [4.68.17.190]

10 29 ms 17 ms 19 ms ae-83-83.ebr3.Washington1.Level3.net [4.69.134.1
69]
11 34 ms 31 ms 36 ms ae-4.ebr2.Newark1.Level3.net [4.69.132.102]
12 27 ms 22 ms 25 ms ae-21-56.car1.Newark1.Level3.net [4.68.99.165]
13 96 ms 93 ms 95 ms CHOOPA-LLC.car1.Newark1.Level3.net [4.79.189.182
]
14 96 ms 96 ms 93 ms 208.167.247.103

Trace complete.]]> http://www.dslreports.com/forum/remark,20796741 Tue, 15 Jul 2008 19:58:47 EDT