For Those with Time Warner Cable( Lag Issue)

[Raist]

In my region, we've been able to show there are problems specifically with the TWC/RR gateways... many users have been going after them through their own support channels. I finally managed to get a promise of escalation into our residential gateway (98.25.64.1) a few weeks back, but haven't heard anything back yet. For the most part, the game is playable just fine... it just randomly decides it's going to be a crappy night and start giving the 2000ms+ response times and timing out due to the @#$@#$ overloaded, oversold market that TWC just refuses to address properly. Take a look at this lovely trace I just took:

Tracing route to 199.91.189.25 over a maximum of 30 hops

  1     2 ms    <1 ms    <1 ms  LPTSRV [10.10.100.1]
  2  2515 ms     *      807 ms  cpe-098-025-064-001.sc.res.rr.com [98.25.64.1]
  3    14 ms    11 ms    13 ms  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4    24 ms    27 ms    35 ms  xe-7-0-0.rlghncpop-rtr1.southeast.rr.com [24.93.64.40]
  5    31 ms    31 ms    31 ms  107.14.19.44
  6    30 ms    34 ms    30 ms  ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
  7    80 ms    71 ms    72 ms  te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.54.10.209]
  8    85 ms    81 ms    76 ms  be2113.mpd21.dca01.atlas.cogentco.com [154.54.6.170]
  9    90 ms    87 ms    86 ms  be2150.mpd21.jfk02.atlas.cogentco.com [154.54.31.130]
 10    94 ms    95 ms    93 ms  be2095.ccr21.bos01.atlas.cogentco.com [154.54.30.38]
 11    69 ms    69 ms    69 ms  be2142.ccr21.ymq02.atlas.cogentco.com [154.54.0.42]
 12    49 ms    48 ms    48 ms  38.122.42.34
 13    47 ms    99 ms    49 ms  192.34.76.10
 14    46 ms    47 ms    51 ms  199.91.189.242
 15    52 ms    48 ms    46 ms  199.91.189.25

As you can see, our persistence has gotten them to clean up the route fairly well with Cogentco's pathing on the northern end of our routes... it's just getting them to address the problem within the TWC infrastructure now. That first gateway's responses are consistently all over the map no matter when they are pinged or however else anyone tests against them, and it's not just the residential one either... and not just when trying to get to our XIV servers. On the TWC forums, we've been able to show it happening on Business Class gateways as well, and when trying to get to various sites in multiple locations (JustinTV, Twitch, Google, Yahoo, Blizzard servers in different locations)... it is a BIG problem specific to TWC/RR that THEY need to address.

Note that this was all being addressed through contact with our ISP by the way, not through SE. Even you guys not with RR/TWC should really push towards getting the ball rolling with your ISP, as they are the ones that can enter into new peering agreements where it is needed to help relieve the congestion issues getting to SE's networks. You WILL need to push for escalation to get it past your local people that are going to repeatedly tell you your connection is just fine--it is an issue that happens past your pole and has nothing to do with your localized connection (which is all many of them can look at). It resides further outward either deeper in their additional network segments or in their partners' segments. So THEY need to be going after the problem within in their pool of resources to track it down properly and push for a resolution to that problem once found, whether that is found to be an in-house issue or one with a transit/peering partner like Cogent, TATA, Levle3, or i-WEB.

For various reasons (not just the fact we pay them for their service, but also related to how they can both investigate and affect issues in your route), our ISP's are our best advocate to help get that portion of our problems fixed so anything weird that may be happening at SE's end isn't further compounded by problems in somewhere like Chicago, Asheburn, or LA that are completely out of SE's influence (but still under the influence of our ISP's, as they compensate those guys for carrying our signal through those regions).

[Ed_N_Ants]

***********************************UPDATE UPDATE UPDATE*************************************

So in practice one would need to understand if an IPS contracts with these facilities to path your connection through them or not. This I do not know if ips contract their services. If they do, than technically they have an obligation to push these companies to fix their issue, but the issue solely relies on the facility themselves. You efforts should be googling the company with the high ping and contacting them directly stating they there is issues with their facility causing bad connections. I followed up with a tech support that arrives on schedules and their sole purpose is hardware related issues and anything that occurs to make sure your connection with your ISP is running smooth. When it leaves your house to go out it makes sure that is smooth, but once it starts running into facilities it technically isn't their fault in the fact that facility probably has issues that need to be fixed. So please find ways to contact these companies for NC it would be atlas.cognectco and tell them they need to fix this issue. If they do not fix this(would have to do more research), it would fall on TWC or your ISP to contact this company or find other services to use and stop contracting with them. If this occurs.

That's false information... Your ISP provider can only control their network not anyone else's... They are not obligated to contact any other provider for a defective network... Sometimes however they will contact the other networking companies out of courtesy but they are by no mean's obligated too... They are however obligated to fix issues on their networks, such as packet loss...

[Raist]

That's false information... Your ISP provider can only control their network not anyone else's... They are not obligated to contact any other provider for a defective network... Sometimes however they will contact the other networking companies out of courtesy but they are by no mean's obligated too... They are however obligated to fix issues on their networks, such as packet loss...

But they do have means to push for action because of the agreements with their transit and peering partners. Your ISP pays for access to these exchanges and routes with these partners (or at the very least has a quid-pro-quo agreement of sorts). Those partners are not accountable to you, as you are not their customer. But.. they are accountable to your ISP, who IS their customer. Then, in turn, your ISP is responsible to you. So, you are basically going up the chain.

[DontTouchMyHoHos]

That's false information... Your ISP provider can only control their network not anyone else's... They are not obligated to contact any other provider for a defective network... Sometimes however they will contact the other networking companies out of courtesy but they are by no mean's obligated too... They are however obligated to fix issues on their networks, such as packet loss...

That is saying restraunts are viable for the bad food they pay for to provide a service for people if they had you shitty food all the time.

[DontTouchMyHoHos]

The level 3 suppervisor has left and if you guys tracert to the server once. It doesnt guaratenee the issue will show. It is spikes, so you may not hit it your first time. I had to do 3 tracerts to get the readings, but before that I showed him 5 times of consistent ms above 200. This issue also occurs with my tracert for league of legends. During the only level 3 supervisor visist I've had in the months I have been pushing it, he is the only one I have had. Before hadn I posted an email to a state wide email to raise this issue from a lady over the phone, during this time he gave me a nation wide email for twc which I will not be posting for you guys to flood with tracerts until they show that nothing is being done. None of the visist that happened today was over the phone and his intention when he showed up was to replace my modem, but once I showed up what was actually going on, we had a talk for awhile and he made some phone calls to show people as well.

When you contract someone to do work for you to provide a service, you are obligated to make sure the service works. Hence why so many people sue EA.

[DontTouchMyHoHos]

Anyone with this issue I would like you all to send me tracerts to this email donttouchmyhohos@gmail.com, but when you conduct your tracert add this to put it into a notepad form. I will send a few of the worst tracerts up to them, but you must be using TWC and you must be in the US. If your overseas, well idk how you dont expect higher pings, unless they are going through the atlas.cogentco servers, but it is kinda of hard to argue your case being over seas. (tracert xxx.xxx.xxx.xx) > "USERPROFILE%\desktop\Tracert.log" replace the x's with the ip you are tracerting before you put this into the cmd window so you can copy paste.

[Raist]

giving this thread a bump to support HoHo's efforts... Jitter at our 98.25.64.1 gateway isn't as bad as last night, but it's still there (not timing out, but still wants to ramp up to the 500-800ms times periodically.) So I imagine others will be feeling it it tonight as things get busy later. Perhaps this thread will get more people involved if we can keep it on the front page.

Giving them until the end of the month to complete the promised investigation into our gateways for South Carolina. If I don't hear anything encouraging from this "investigation" by then I guess I'll start pestering the guys in Herndon again... Good luck with your guys where you are.

[DontTouchMyHoHos]

bumping for justice so I can get other tracerts from you guys

[DontTouchMyHoHos]

I need more tracert's guys to give to time warner. Read my first post.