375 replies to this topic

[Clit Beastwood]

Alekzander Smirnoff, on 20 December 2014 - 01:49 PM, said:

OK, so I installed pingzapper, my latency is still the same around 40 ms with it on or off. Now my other question is, I'm in Kentucky, and the servers are (I'm assuming here) in Vancouver or near by there. I'm going to also make the assumption that you assign the server setting to where the server actually is, because I've not read anything about how to set that one. Right now it funneled my traffic out of New York, NY and whatever route it took from there I was still getting "disconnected from game server." I'm going to flip it over to West which dumps it out in Los Angelas, CA and see what happens.

Set it to the location nearest you, or just leave it at automatic - it'll ping all the servers and select the best one for you at that moment. By picking an endpoint far away, you're not going to fix anything because your traffic from you to the vpn site won't be tunneled.

[Alekzander Smirnoff]

Just to be clear, on what I actually meant. Here (steam link since its quicker than making some upload account).

[Clit Beastwood]

Alekzander Smirnoff, on 20 December 2014 - 05:19 PM, said:

Just to be clear, on what I actually meant. Here (steam link since its quicker than making some upload account).

Select the server closest to you
By server it means the Vpn server you connect to

[Pizza Knight]

Bhael Fire, on 11 December 2014 - 10:27 AM, said:

I'm on TWC as well in Texas. I used to get 80-90 pings. Now it's never lower than 120...and often around 400-600 every other match now. When it's that high, the game is unplayable unless I disconnect and then rejoin the match — which sometimes resets the ping down to around 120.

I'm in Texas on TWC and getting the exact same problem. My pings are now usually around 120 and too often it jumps to 400-700 which is unplayable. Very annoying. Can something be done about this or is it time to find something else to do????

Edited by Pizza Night, 20 December 2014 - 08:43 PM.

[Alekzander Smirnoff]

Fierostetz, on 20 December 2014 - 06:11 PM, said:

Select the server closest to you
By server it means the Vpn server you connect to

Ok, because I was assuming the auto selection below that red circle was where the vpn tunnel ended and traffic was then routed from that point on up to mwo's server. Because the starting point of the ssl tunnel is me, not their vpn server, which as i see it, is the ssl exit point.

Edited by Alekzander Smirnoff, 20 December 2014 - 11:25 PM.

[Clit Beastwood]

Alekzander Smirnoff, on 20 December 2014 - 11:23 PM, said:

Ok, because I was assuming the auto selection below that red circle was where the vpn tunnel ended and traffic was then routed from that point on up to mwo's server. Because the starting point of the ssl tunnel is me, not their vpn server, which as i see it, is the ssl exit point.

Yeah don't overthink it wherever possible just use auto, despite hours of tweaking auto works better

[Alekzander Smirnoff]

Yar! I did see a marked improvement in not having game server disconnects while using it which is the most important part and the $4 for a 30 day test run was chump change so I might throw down for a year on it. Might as well send a "suggestion" in to them to slip a MWO button on their game list.

[Inathero]

Pizza Night, on 20 December 2014 - 08:42 PM, said:

I'm in Texas on TWC and getting the exact same problem. My pings are now usually around 120 and too often it jumps to 400-700 which is unplayable. Very annoying. Can something be done about this or is it time to find something else to do????

exact same issue

here's my traceroute:

C:\Users\User>tracert mwomercs.com
Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:
  1	62 ms	13 ms	15 ms  cpe-72-183-224-1.elp.res.rr.com [72.183.224.1]
  2	10 ms	17 ms	11 ms  te7-3.elpwtx0301h.texas.rr.com [24.92.98.177]
  3	21 ms	17 ms	61 ms  tge0-9-0-4.elpttxha01r.texas.rr.com [24.175.60.110]
  4	28 ms	31 ms	32 ms  agg25.dllatxl301r.texas.rr.com [24.175.60.220]
  5	44 ms	30 ms	48 ms  ae-4-0.cr0.dfw10.tbone.rr.com [66.109.6.88]
  6	30 ms	60 ms	43 ms  ae2.pr1.dfw10.tbone.rr.com [107.14.17.236]
  7	37 ms	75 ms   136 ms  dls-bb1-link.telia.net [213.248.93.189]
  8   111 ms   109 ms	79 ms  nyk-bb1-link.telia.net [213.155.130.64]
  9	77 ms	88 ms	76 ms  nyk-b2-link.telia.net [213.155.130.28]
10	 *	  180 ms	 *	 nwk-1-6k.nj.us [178.32.135.212]
11   239 ms   132 ms   179 ms  bhs-g1-6k.qc.ca [198.27.73.205]
12   163 ms   131 ms   131 ms  198.27.73.231
13   128 ms   131 ms   132 ms  mwomercs.com [192.99.109.192]
Trace complete.

The tenth hop is always the worst

[LordSkippy]

TWC in Austin, TX here. Same symptoms as others, was getting 80ms pings a month or so ago, now getting 110+ms pings with spikes into the 400-600ms pings. When the 400-600ms ping spikes happen, they can last for over 20 minutes.

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:
 
  1	<1 ms	<1 ms	<1 ms  r2d2 [172.16.10.1]
  2	 8 ms	 5 ms	 9 ms  192.168.0.1
  3	28 ms	27 ms	22 ms  cpe-68-203-0-1.austin.res.rr.com [68.203.0.1]
  4	31 ms	29 ms	29 ms  cpe-68-203-0-1.austin.res.rr.com [68.203.0.1]
  5	38 ms	29 ms	19 ms  tge7-4.ausgtxlg02h.texas.rr.com [66.68.4.77]
  6	39 ms	43 ms	50 ms  tge0-11-0-24.ausxtxir02r.texas.rr.com [24.175.41.6]
  7	19 ms	33 ms	29 ms  be22.ausxtxir02r.texas.rr.com [24.175.43.215]
  8	28 ms	39 ms	40 ms  agg22.hstqtxl301r.texas.rr.com [24.175.41.48]
  9	27 ms	40 ms	39 ms  ae-2-0.cr0.hou30.tbone.rr.com [66.109.6.108]
10	38 ms	39 ms	39 ms  107.14.19.218
11	27 ms	39 ms	41 ms  ae0.pr1.dfw10.tbone.rr.com [107.14.17.232]
12	38 ms	36 ms	33 ms  dls-bb1-link.telia.net [213.248.93.189]
13	71 ms	87 ms	83 ms  nyk-bb2-link.telia.net [213.155.137.28]
14	73 ms	79 ms	89 ms  nyk-b2-link.telia.net [213.155.130.30]
15	 *		*		*	 Request timed out.
16	 *	  473 ms   489 ms  bhs-g1-6k.qc.ca [198.27.73.205]
17   138 ms   134 ms   135 ms  198.27.73.231
18   120 ms   123 ms   139 ms  mwomercs.com [192.99.109.192]
 
Trace complete.

[Inathero]

Is the issue time warner, or is it an issue with telia?

Pingplotter:

Edited by Inathero, 22 December 2014 - 09:39 PM.

[SoggyGorilla]

after 10 calls and 5 hours on the phone, the Time Warner service reps in the Philippians escalated me to the customer service team in america. They opened a network backbone ticket for the issue and are going to begin investigating the issue starting next week after the holiday. hopefully we can get something fixed soon.

[LordSkippy]

SoggyGorilla, on 23 December 2014 - 12:35 PM, said:

after 10 calls and 5 hours on the phone, the Time Warner service reps in the Philippians escalated me to the customer service team in america. They opened a network backbone ticket for the issue and are going to begin investigating the issue starting next week after the holiday. hopefully we can get something fixed soon.

Thank you for hanging in with the phone calls, hopefully something will come from it.

[Alekzander Smirnoff]

SoggyGorilla, on 23 December 2014 - 12:35 PM, said:

after 10 calls and 5 hours on the phone, the Time Warner service reps in the Philippians escalated me to the customer service team in america. They opened a network backbone ticket for the issue and are going to begin investigating the issue starting next week after the holiday. hopefully we can get something fixed soon.

Give this man cbills!

[Trotil]

Thanks, Soggy, much appreciated!

[Inathero]

any updates?

we all know here that we have issue with telia.net when checking out mwomercs.com , however that occasional spike at 500-600ms? That's not a mwomercs.com server, that's another server.

I did a ping test during one of those matches, and it was saying 120ms average for mwomercs.com, but my ingame ping was above 600ms

how can I check which server my client goes per match? should I brute force it with wireshark or what

[Kin3ticX]

We should get together, research a good VPN, and wire around this crap. Looks like they are about $10 dollars a month on average.

Already tried the WTFast trial and it is not compatible with MWO.

Edited by Kin3ticX, 29 December 2014 - 10:02 PM.

[SoggyGorilla]

Right now im getting 600+ms ping. and its every night between 10pm and 2am Central Time. I grab my cell phone and download an android app that lets me ping and its 84ms. so that tells me its a time warner problem, because my WIRELESS Verizon cell phone has 1/10th the ping time. i have the ticket open with time warner and they are looking at it. i will let everyone know when they tell me something. Until then you can keep your self busy by trolling their Facebook page and giving out the contact info for the FCC complaints to people who post about the poor customer service. thats what i have been doing, and its somewhat satisfying.

Edited by SoggyGorilla, 29 December 2014 - 10:31 PM.

[Clit Beastwood]

Kin3ticX, on 29 December 2014 - 09:57 PM, said:

We should get together, research a good VPN, and wire around this crap. Looks like they are about $10 dollars a month on average.

Already tried the WTFast trial and it is not compatible with MWO.

Yeah I bought a month and spent some time with their support to no avail - pingzapper worked but the client isn't ver informational. The wtfast gui had some neat stats -maybe if everyone contacts wtfast support for mwo support to be added... I'll pop into TS at some point and see if you're on to talk VPN's - I've tested a bunch with mwo.

Edited by Fierostetz, 30 December 2014 - 09:58 AM.

[Kin3ticX]

SoggyGorilla, on 29 December 2014 - 10:31 PM, said:

Right now im getting 600+ms ping. and its every night between 10pm and 2am Central Time. I grab my cell phone and download an android app that lets me ping and its 84ms. so that tells me its a time warner problem, because my WIRELESS Verizon cell phone has 1/10th the ping time. i have the ticket open with time warner and they are looking at it. i will let everyone know when they tell me something. Until then you can keep your self busy by trolling their Facebook page and giving out the contact info for the FCC complaints to people who post about the poor customer service. thats what i have been doing, and its somewhat satisfying.

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.

Edited by Kin3ticX, 30 December 2014 - 10:18 AM.

[Kin3ticX]

LordSkippy, on 22 December 2014 - 05:50 PM, said:

TWC in Austin, TX here. Same symptoms as others, was getting 80ms pings a month or so ago, now getting 110+ms pings with spikes into the 400-600ms pings. When the 400-600ms ping spikes happen, they can last for over 20 minutes.

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:
 
  1	<1 ms	<1 ms	<1 ms  r2d2 [172.16.10.1]
  2	 8 ms	 5 ms	 9 ms  192.168.0.1
  3	28 ms	27 ms	22 ms  cpe-68-203-0-1.austin.res.rr.com [68.203.0.1]
  4	31 ms	29 ms	29 ms  cpe-68-203-0-1.austin.res.rr.com [68.203.0.1]
  5	38 ms	29 ms	19 ms  tge7-4.ausgtxlg02h.texas.rr.com [66.68.4.77]
  6	39 ms	43 ms	50 ms  tge0-11-0-24.ausxtxir02r.texas.rr.com [24.175.41.6]
  7	19 ms	33 ms	29 ms  be22.ausxtxir02r.texas.rr.com [24.175.43.215]
  8	28 ms	39 ms	40 ms  agg22.hstqtxl301r.texas.rr.com [24.175.41.48]
  9	27 ms	40 ms	39 ms  ae-2-0.cr0.hou30.tbone.rr.com [66.109.6.108]
10	38 ms	39 ms	39 ms  107.14.19.218
11	27 ms	39 ms	41 ms  ae0.pr1.dfw10.tbone.rr.com [107.14.17.232]
12	38 ms	36 ms	33 ms  dls-bb1-link.telia.net [213.248.93.189]
13	71 ms	87 ms	83 ms  nyk-bb2-link.telia.net [213.155.137.28]
14	73 ms	79 ms	89 ms  nyk-b2-link.telia.net [213.155.130.30]
15	 *		*		*	 Request timed out.
16	 *	  473 ms   489 ms  bhs-g1-6k.qc.ca [198.27.73.205]
17   138 ms   134 ms   135 ms  198.27.73.231
18   120 ms   123 ms   139 ms  mwomercs.com [192.99.109.192]
 
Trace complete.

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

Edited by Kin3ticX, 30 December 2014 - 06:47 PM.