375 replies to this topic

[Kin3ticX]

More strange behavior from 192.99.40.105 with 1 byte and 10 byte packets

Edited by Kin3ticX, 30 October 2018 - 04:42 PM.

[Clit Beastwood]

Kin3ticX, on 30 December 2014 - 10:16 AM, said:

Still not sure which hop is actually triaging gaming packets giving us the 300-600 ping problem during prime time. Traceroutes and pings are not conclusively revealing the problem hop. Sometimes simply quitting and reconnecting to a game jukes it out back to normal, sometimes not. This means there is a router out there which has resources availible but is denying priority to certain kinds of traffic from certain providers. It could even be a traffic feud or something.

So i'm still not sure whether its Timwarner/RRunner, Telia, or OVH somewhere.

tried back to back with sslvpn (privateinternetaccess) and without, those last couple hops are slow on twc and not on sslvpn - maybe they're modifying the headers or something

[BellatorMonk]

One of the many reasons I have not dropped a dime on the game since being a Founder. 416 ping tonight making playing CW useless to even bother competing against Lurm and ppc boats.

traceroute to mwomercs.com (192.99.109.192), 30 hops max, 38 byte packets
1 * * *
2 tge7-3.snaxtxfp01h.texas.rr.com (24.28.131.153) 13.121 ms 14.153 ms 11.611 ms
3 tge0-10-0-12.snaptx1901r.texas.rr.com (24.175.33.96) 12.051 ms 16.010 ms 14.878 ms
4 agg22.snavtxuu02r.texas.rr.com (24.175.32.160) 15.534 ms 14.622 ms 12.203 ms
5 agg23.hstqtxl301r.texas.rr.com (24.175.32.156) 18.726 ms 20.753 ms 21.522 ms
6 107.14.19.94 (107.14.19.94) 21.163 ms 20.603 ms 18.104 ms
7 ae-0-0.cr0.dfw10.tbone.rr.com (66.109.6.39) 20.434 ms 24.436 ms 107.14.19.216 (107.14.19.216) 22.414 ms
8 ae1.pr1.dfw10.tbone.rr.com (107.14.17.234) 24.153 ms 107.14.19.97 (107.14.19.97) 26.819 ms ae2.pr1.dfw10.tbone.rr.com (107.14.17.236) 71.698 ms
9 dls-bb1-link.telia.net (213.248.93.189) 20.350 ms 21.939 ms 23.009 ms
10 nyk-bb1-link.telia.net (213.155.133.176) 69.924 ms 68.706 ms 70.312 ms
11 nyk-b2-link.telia.net (213.155.130.28) 66.392 ms 67.313 ms *
12 * * *
13 192.99.146.84 (192.99.146.84) 416.594 ms 442.772 ms 461.364 ms
14 198.27.73.231 (198.27.73.231) 125.168 ms 126.713 ms 122.910 ms
15 mwomercs.com (192.99.109.192) 124.111 ms !C 119.822 ms !C 130.057 ms !C

[Inathero]

Kin3ticX, on 30 December 2014 - 01:48 PM, said:

What is strange is that our hops are completely different until we hit bhs-g1-6k.qc.ca and we both have the same problem. Could you post a tracert to 192.99.40.105?

test done at 1:46 PM PST


192.99.40.105 is one of the game servers, it goes through different parts of the OVH network.





evening test

I know you weren't asking me, but this is my traceroute to 192.99.40.105



35 ms average jumps to 85 ms average to 130 ms along this trip

[SoggyGorilla]

Ok guys just got my first update from twc about my ticket. looks like they made a formal request to telia to investigate the latency and improve peering. here is a copy paste, with names and such protected and altered.

[To: xxxxxxxx-csc@teliaxxxxx.com; NOC.Austin.PacWest-Texas

Subject: RE: [peering-request] --- lagging with playing https://mwomercs.com/game



Telia NOC..



Here is the info that was originally supplied. Our customer is complaining of latency issues when connecting to the server.



Here is the traceroute.



I have highlighted the troubled hops that are showing latency.



Thanks.

Telia NOC,

Could you investigate a latency issue between your network and OVH Systems. This issue is affecting our customers network connection to https://mwomercs.com/game (2.99.109.129). Thanks.

Edited by SoggyGorilla, 31 December 2014 - 08:50 PM.

[LordSkippy]

Kin3ticX, on 30 December 2014 - 01:48 PM, said:

[color=#959595]What is strange is that our hops are completely different until we hit bhs-g1-6k.qc.ca and we both have the same problem. Could you post a tracert to 192.99.40.105?[/color]

tracert 192.99.40.105
Tracing route to ns7000226.ip-192-99-40.net [192.99.40.105]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  r2d2 [172.16.10.1]
  2    13 ms	 8 ms	 8 ms  192.168.0.1
  3    26 ms    28 ms    31 ms  cpe-68-203-0-1.austin.res.rr.com [68.203.0.1]
  4    40 ms    29 ms    30 ms  cpe-68-203-0-1.austin.res.rr.com [68.203.0.1]
  5    29 ms    31 ms    37 ms  tge7-4.ausgtxlg02h.texas.rr.com [66.68.4.77]
  6    35 ms    39 ms    39 ms  tge0-11-0-24.ausxtxir02r.texas.rr.com [24.175.41.6]
  7    49 ms    29 ms    37 ms  be22.ausxtxir02r.texas.rr.com [24.175.43.215]
  8    26 ms    39 ms    41 ms  agg22.hstqtxl301r.texas.rr.com [24.175.41.48]
  9    23 ms    51 ms    39 ms  ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
10    40 ms    37 ms    49 ms  107.14.19.218
11    33 ms    44 ms    40 ms  107.14.19.97
12    43 ms    36 ms    49 ms  dls-bb1-link.telia.net [213.248.93.189]
13    86 ms    79 ms    83 ms  nyk-bb1-link.telia.net [213.155.130.64]
14    82 ms    91 ms    77 ms  nyk-b2-link.telia.net [213.155.130.28]
15	 *	    *	    *	 Request timed out.
16   133 ms   139 ms   139 ms  192.99.146.84
17   232 ms   130 ms   134 ms  bhs-s4-6k.qc.ca [198.27.73.144]
18   133 ms   139 ms   139 ms  ns7000226.ip-192-99-40.net [192.99.40.105]
Trace complete.

[BellatorMonk]

Guess what...300-500ms pings during matches...hooray (topping 700ms after this initial post)

traceroute to mwomercs.com (192.99.109.192), 30 hops max, 38 byte packets
1 * * *
2 tge7-3.snaxtxfp01h.texas.rr.com (24.28.131.153) 13.634 ms 14.060 ms 10.540 ms
3 tge0-10-0-12.snaptx1901r.texas.rr.com (24.175.33.96) 11.177 ms 20.135 ms 11.831 ms
4 agg22.snavtxuu02r.texas.rr.com (24.175.32.160) 13.231 ms 23.190 ms 14.376 ms
5 agg23.hstqtxl301r.texas.rr.com (24.175.32.156) 22.416 ms 15.962 ms 14.933 ms
6 107.14.19.94 (107.14.19.94) 16.528 ms 19.025 ms 20.361 ms
7 107.14.19.218 (107.14.19.218) 22.981 ms 42.327 ms 51.037 ms
8 ae1.pr1.dfw10.tbone.rr.com (107.14.17.234) 20.330 ms ae0.pr1.dfw10.tbone.rr.com (107.14.17.232) 23.206 ms ae1.pr1.dfw10.tbone.rr.com (107.14.17.234) 22.831 ms
9 dls-bb1-link.telia.net (213.248.93.189) 20.807 ms 22.859 ms 27.671 ms
10 nyk-bb1-link.telia.net (213.155.133.176) 66.663 ms 63.362 ms 64.797 ms
11 nyk-b2-link.telia.net (213.155.130.28) 66.807 ms 109.198 ms 65.084 ms
12 * * *
13 192.99.146.84 (192.99.146.84) 323.289 ms 330.948 ms 334.108 ms
14 198.27.73.231 (198.27.73.231) 121.255 ms 120.649 ms 123.443 ms
15 mwomercs.com (192.99.109.192) 121.253 ms !C 122.267 ms !C 124.936 ms !C

Edited by BellatorMonk, 02 January 2015 - 09:35 PM.

[adamts01]

Fixed it. Kinda. I live in Texas and have time warner and have been experiencing random super high ping. My games would go from normal of 110ms to 600ms. I'm not too computer savvy so maybe this wasn't the best way to go about it but it worked for me. I downlowded the vpn PrivateTunnel https://www.privatetunnel.com/ and used their server in Mantreal and now my ping is 70ms in game and I also verified this using a tracert. It took 14 hops instead of 16. It does fluctuate but the game is 100% playable. They have a free 100Mb trial, games use 30Mb each and I ended up buying 50Gb for $12. Thats over 1,600 games, worth it for me. This program doesn't seem to be specifically for gaming so maybe there's a better one out there. idk. I got t-boned on my motorcycle and this game is the most fun thing I'm able to do so this has been driving me crazy. So glad it's working again. I really hope this can help other people with their connections.

[LordSkippy]

adamts01, on 03 January 2015 - 09:05 AM, said:

I downlowded the vpn

There was discussions about different VPN services a few pages ago. Some recommended one called ping zapper. I have a VPN service that has a few outlets in Canada. The problem with using a VPN is that if needs to take a different route to your VPN service than the default route. If they both end up going through the same node that is causing the issue, then it won't do you any good. If it does route around the bad node, then it can improve your ping, if there aren't bad or worse nodes, or a lot more hops, along the way.

It is very much a "Your Mileage May Vary" solution, and one we shouldn't have to be forced to do. Someone needs to clean up their node in the chain, and it looks like it's Telia NOC.

[Kin3ticX]

adamts01, on 03 January 2015 - 09:05 AM, said:

Fixed it. Kinda. I live in Texas and have time warner and have been experiencing random super high ping. My games would go from normal of 110ms to 600ms. I'm not too computer savvy so maybe this wasn't the best way to go about it but it worked for me. I downlowded the vpn PrivateTunnel https://www.privatetunnel.com/ and used their server in Mantreal and now my ping is 70ms in game and I also verified this using a tracert. It took 14 hops instead of 16. It does fluctuate but the game is 100% playable. They have a free 100Mb trial, games use 30Mb each and I ended up buying 50Gb for $12. Thats over 1,600 games, worth it for me. This program doesn't seem to be specifically for gaming so maybe there's a better one out there. idk. I got t-boned on my motorcycle and this game is the most fun thing I'm able to do so this has been driving me crazy. So glad it's working again. I really hope this can help other people with their connections.

Sorry to hear that. I hope the recovery goes well.

followup on the TWC issues continuing. Damn telia!
It 10:PM pst and I have a 500 ping ingame and heres some screencaps
Getting closer and closer to throwing money at a VPN.

Edited by Kin3ticX, 30 October 2018 - 04:42 PM.

[Jon Cunningham]

SoggyGorilla, on 31 December 2014 - 08:50 PM, said:

Ok guys just got my first update from twc about my ticket. looks like they made a formal request to telia to investigate the latency and improve peering. here is a copy paste, with names and such protected and altered.

[To: xxxxxxxx-csc@teliaxxxxx.com; NOC.Austin.PacWest-Texas

Subject: RE: [peering-request] --- lagging with playing https://mwomercs.com/game



Telia NOC..



Here is the info that was originally supplied. Our customer is complaining of latency issues when connecting to the server.



Here is the traceroute.



I have highlighted the troubled hops that are showing latency.



Thanks.

Telia NOC,

Could you investigate a latency issue between your network and OVH Systems. This issue is affecting our customers network connection to https://mwomercs.com/game (2.99.109.129). Thanks.

Yeah - thanks to your complaint to TWC and other users on TWC, we've been able to make some serious headway on the TWC issue. They now have an open ticket in their NOC for this issue and I've been able to touch base with some network engineers.

Hoping to provide a good news update soon.

[Clit Beastwood]

Jon Cunningham, on 05 January 2015 - 08:24 AM, said:

Yeah - thanks to your complaint to TWC and other users on TWC, we've been able to make some serious headway on the TWC issue. They now have an open ticket in their NOC for this issue and I've been able to touch base with some network engineers.

Hoping to provide a good news update soon.

My hero! :swoon:

In all seriousness, if there's any data you want gathered or any tests you want run, etc. absolutely feel free to PM me. I've all but given up on CW drops, I don't want to saddle my team with a potential DC so I've pretty much stuck to (rubberbandy) pugs and testing grounds target practice. And Alien Isolation - that game's intense!

Edited by Fierostetz, 05 January 2015 - 08:49 AM.

[Sgt Minuteman]

I used to get 23-60ms pings in game and for about 3-4 months now, the pings sometimes make the game unplayable for me. I have had no changes in my ISP (TWC).Could you please check into central US servers in Central US/ Texas if you don't have any?

Titanfall even lets you connect to servers,based on location in USA, I use Southwest servers .

I get 23ms pings in Battlefield 3 & 4 consistently and play experience is much better (aside from in game bugs in netcode issues in BF4)

Thanks!!

One game I was at 960ms ping, and it slowly came down to 600ms, I just was stuttering on screen like watching a game of MWO with flash cards!

BellatorMonk, on 02 January 2015 - 08:29 PM, said:

Guess what...300-500ms pings during matches...hooray (topping 700ms after this initial post)

traceroute to mwomercs.com (192.99.109.192), 30 hops max, 38 byte packets
1 * * *
2 tge7-3.snaxtxfp01h.texas.rr.com (24.28.131.153) 13.634 ms 14.060 ms 10.540 ms
3 tge0-10-0-12.snaptx1901r.texas.rr.com (24.175.33.96) 11.177 ms 20.135 ms 11.831 ms
4 agg22.snavtxuu02r.texas.rr.com (24.175.32.160) 13.231 ms 23.190 ms 14.376 ms
5 agg23.hstqtxl301r.texas.rr.com (24.175.32.156) 22.416 ms 15.962 ms 14.933 ms
6 107.14.19.94 (107.14.19.94) 16.528 ms 19.025 ms 20.361 ms
7 107.14.19.218 (107.14.19.218) 22.981 ms 42.327 ms 51.037 ms
8 ae1.pr1.dfw10.tbone.rr.com (107.14.17.234) 20.330 ms ae0.pr1.dfw10.tbone.rr.com (107.14.17.232) 23.206 ms ae1.pr1.dfw10.tbone.rr.com (107.14.17.234) 22.831 ms
9 dls-bb1-link.telia.net (213.248.93.189) 20.807 ms 22.859 ms 27.671 ms
10 nyk-bb1-link.telia.net (213.155.133.176) 66.663 ms 63.362 ms 64.797 ms
11 nyk-b2-link.telia.net (213.155.130.28) 66.807 ms 109.198 ms 65.084 ms
12 * * *
13 192.99.146.84 (192.99.146.84) 323.289 ms 330.948 ms 334.108 ms
14 198.27.73.231 (198.27.73.231) 121.255 ms 120.649 ms 123.443 ms
15 mwomercs.com (192.99.109.192) 121.253 ms !C 122.267 ms !C 124.936 ms !C

[Clit Beastwood]

Sgt Minuteman, on 05 January 2015 - 05:59 PM, said:

I used to get 23-60ms pings in game and for about 3-4 months now, the pings sometimes make the game unplayable for me. I have had no changes in my ISP (TWC).Could you please check into central US servers in Central US/ Texas if you don't have any?

Titanfall even lets you connect to servers,based on location in USA, I use Southwest servers .

I get 23ms pings in Battlefield 3 & 4 consistently and play experience is much better (aside from in game bugs in netcode issues in BF4)

Thanks!!

One game I was at 960ms ping, and it slowly came down to 600ms, I just was stuttering on screen like watching a game of MWO with flash cards!

I called the only ISP in my area other than TWC, they do business class only, but I was going to spend the 200/month to get a 50 mbit business line instead of my current 320mbit TWC connection... until I found out they lease their lines and bandwidth from TWC. :sigh: after spending a couple grand on mwo across multiple accounts, I just don't even want to play anymore. I *will* say that my hitreg and packet loss was great before the MWO server move, and I've had hitreg issues ever since then... Only now it's paired with rubberbanding and jitter. Doesn't seem to affect any other game other than world of tanks.


Heh - love it. I called TWC a while back and talked to a TIER 3 SUPPOR WONDERGOD. I sent them documentation showing the breakdowns in their peering with telia. They offered to send someone out to my house to check out the equipment :facepalm: Yes, the first hop from my computer to my modem and from the modem to los angeles are fine, but a few states away, there's latency caused by the modem installed in my living room. Yes, that's it exactly.

Edited by Fierostetz, 06 January 2015 - 10:24 AM.

[Jon Cunningham]

Sorry to hear about that Fierostetz.

The throttling that Kinetic appears to have some evidence for is pretty unacceptable for us, we definitely want to get it sorted as fast as we can. Working hard on it. : (

[Dagorlad13]

Kin3ticX, on 04 January 2015 - 10:16 PM, said:

Sorry to hear that. I hope the recovery goes well.

followup on the TWC issues continuing. Damn telia!
It 10:PM pst and I have a 500 ping ingame and heres some screencaps
Getting closer and closer to throwing money at a VPN.

Yes, this is exactly what I see just about every third game over the last month, before that I always had 80ms-100ms ping. Now, the lowest my ping gets is 117ms. I am not willing to suscribe to a VPN service just to get the same performance I had a month or two ago. My trace routes usually show slowdowns near the Canadian border.

[Kin3ticX]

Jon Cunningham, on 06 January 2015 - 03:38 PM, said:

Sorry to hear about that Fierostetz.

The throttling that Kinetic appears to have some evidence for is pretty unacceptable for us, we definitely want to get it sorted as fast as we can. Working hard on it. : (

This is a learning as I go thing. Question. I read that traffic paths are actually asymmetric meaning that the traceroute tool only shows the transmit path. Could we all be getting qos'd or throttled on the return rather than the transmit? I looked at an old traceroute you sent me coming from OVH and there is a another company in play. Tata Communications.

Thanks for all the help again

Edited by Kin3ticX, 06 January 2015 - 05:42 PM.

[JSmith7784]

I also have TWC and I'm located in western NY. Before the server move I had a constant ping between 30-40 and my hit registration seemed pretty good. After the move I now have a ping that is always above 50 and sometimes stays near 70. I now get spikes, lag, warping and some days my hit registration seems to be about 50%. I'll see the hit effects and then watch no damage register on the target screen. Very annoying. Not sure what the deal is with the new server. I just know it has made things worse for my gaming experience. I use a wired connection and usually get about 34 down and 5 up running from my modem thru my router then to my desktop. Running directly from the modem I get the same results/ping so I know my equipment isn't the issue. I use both personally owned Motorola 6141 and dlink DIR-615 router. All have updated firmware.

[Trevor Belmont]

I'm also on Time Warner and having this problem (in Texas). I used to get ping between 60-80, now it's always 140 or higher. I had one match last night at 460 ping. The mechs would just be marching in place for 5 seconds then suddenly move.

[Clit Beastwood]

Kin3ticX, on 06 January 2015 - 05:37 PM, said:

This is a learning as I go thing. Question. I read that traffic paths are actually asymmetric meaning that the traceroute tool only shows the transmit path. Could we all be getting qos'd or throttled on the return rather than the transmit? I looked at an old traceroute you sent me coming from OVH and there is a another company in play. Tata Communications.

Thanks for all the help again

Well the easiest way would be to have someone run a traceroute to one of us from the datacenter - for me my first hop is 76.89.128.1, so if someone there did a traceroute back :shrug: John I don't suppose there's a chance of someone doing a traceroute to 76.89.128.1 from the data center and posting the results, is there?


What OS are you on? Every OS comes with a traceroute tool but they're not all the same, some use ICMP and some use UDP, I think there are a few that even use TCP.

More interesting results - my performance is much better with SSL VPN (not perfect, but better) - if I set up my VPN to tunnel without encryption or move it to a port other than 443 its back to bad (aka probably throttled).

Edited by Fierostetz, 07 January 2015 - 09:35 AM.