375 replies to this topic

[Santanico Pandamonium]

Marklee,

No, this hasn't been solved...

I'm a TWC customer in central Texas. My pings to Montreal via Ookla speedtest is 51ms. My ping to mwomercs.com (via cmd) is 96ms.

During prime time (around 2100 CST) my in game ping to mwomercs is between 300-400ms.

I'm going to try the Pingzapper thing. It's a shame cause before the "server move" my ping was a reliable 30-40ms.

[Zuri Prime]

I've used Pingzapper for a couple of days. I'm in Dallas.

It works, though my ping through New York is ~100ms-120ms. I still get connection throttling/degradation over a period of time, so I'll wind up at 400ms-500ms again, though the VPN takes longer for it to do so than normal. And I mean something like an hour or two instead or every 15 - 30 minutes. Pingzapper seems to be worth it for now, but TWC and Tella need to get their $#!% in gear.

[Kin3ticX]

Santanico Pandamonium, on 25 January 2015 - 06:59 AM, said:

Marklee,

No, this hasn't been solved...

I'm a TWC customer in central Texas. My pings to Montreal via Ookla speedtest is 51ms. My ping to mwomercs.com (via cmd) is 96ms.

During prime time (around 2100 CST) my in game ping to mwomercs is between 300-400ms.

I'm going to try the Pingzapper thing. It's a shame cause before the "server move" my ping was a reliable 30-40ms.

I thought the server move after IGP went under was alright until I saw the unexplainable high pings in the evenings. Thought it was a fluke for a long while until it just kept happening and happening.

[Cabbage Merchant]

Pretty sure I did something wrong with this trace.

Maybe wrong IP or something?

I've got TWC and I've been experiencing more rubberbanding than usual.



Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Sparticus>tracert 192.168.109.192

Tracing route to 192.168.109.192 over a maximum of 30 hops

1 <1 ms 1 ms 1 ms 192.168.0.2
2 * * * Request timed out.
3 33 ms 29 ms 30 ms 142.254.151.129
4 16 ms 13 ms 16 ms tge7-1.lynhohae01h.midwest.rr.com [24.164.108.15
3]
5 17 ms 14 ms 16 ms 24.33.101.80
6 17 ms 36 ms 18 ms be14.pltsohae01r.midwest.rr.com [65.29.1.87]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
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.

[Kin3ticX]

I called Time Warner and got in touch with a nice and helpful tech guy. Explained the issue, how it was affecting 2 of my friends in the area and people between here and Texas. He told me there was no record of this problem existing in his system(which surprised me).

I also explained that I had been in contact with the senior architecture lead for Mechwarrior Online and that the problem was hard to pinpoint but he believed it was Telia. There seems to be some confusion whether we are supposed to be peering through Telia in the first place(he briefly spoke with his senior network guy). He took a copy paste of my traceroute to mwomercs.com and is going to elevate it and call me back in a few days.

Edited by Kin3ticX, 27 January 2015 - 11:58 AM.

[Clit Beastwood]

Good luck! despite lots of data I've never successfully gotten a call back. They always wind up back at 1) they can't do anything outside their network, or 2) they offer to send someone to my house. Post back letting us know how it goes!

Edited by Fierostetz, 27 January 2015 - 12:00 PM.

[BellatorMonk]

Nothing will occur on either side of the fence until $$$ start to shrink.

[Dagorlad13]

BellatorMonk, on 27 January 2015 - 12:41 PM, said:

Nothing will occur on either side of the fence until $$$ start to shrink.

The problem is that TWC is the only high-speed internet option available in many areas, so they have no competition.

[Kin3ticX]

Fierostetz, on 27 January 2015 - 11:59 AM, said:

Good luck! despite lots of data I've never successfully gotten a call back. They always wind up back at 1) they can't do anything outside their network, or 2) they offer to send someone to my house. Post back letting us know how it goes!

The tech called me back just now and said they can't do anything about it unfortunately.

[Zuri Prime]

Kin3ticX, on 27 January 2015 - 01:21 PM, said:

The tech called me back just now and said they can't do anything about it unfortunately.

So we're screwed? This really sucks because even with a VPN I'm still getting crazy latency with a persisting connection.

[NocturnalBeast]

Airmanator, on 27 January 2015 - 02:24 PM, said:

So we're screwed? This really sucks because even with a VPN I'm still getting crazy latency with a persisting connection.

I have good luck with Pingzapper, but my ping is still about 20-30ms higher than it was before the server move and TWC's speed "increase".

Edited by Ed Steele, 27 January 2015 - 03:35 PM.

[Zuri Prime]

Ed Steele, on 27 January 2015 - 03:34 PM, said:

I have good luck with Pingzapper, but my ping is still about 20-30ms higher than it was before the server move and TWC's speed &quot;increase&quot;.

Interesting. What server do you use for Pingzapper?

[NocturnalBeast]

Airmanator, on 27 January 2015 - 05:13 PM, said:

Interesting. What server do you use for Pingzapper?

I usually get the best results with Chicago 1.

[Clit Beastwood]

Ed Steele, on 27 January 2015 - 05:46 PM, said:

I usually get the best results with Chicago 1.

Same here (re:chicago 1). Though, sometimes I get a 200-300ms ping even when using pingzapper thru Chicago. Also, some nights I get a lot of dc's from the Chicago1 or Chicago2 server, but it's infrequent. I still think its totally worth the money. I *do* wish that it had some better reporting like wtfast though - initially I wanted WTFast more because of its logging and graphs, but the fact that pingzapper "just worked" won me over.



I just opened a support ticket with pingzapper linking to this thread - I asked for some configuration advice or "best practices" that I can re-post here. If TWC won't put some pressure on telia to fix their poopy peering, maybe the pingzapper folks can at least ease the setup process.

[NocturnalBeast]

Fierostetz, on 28 January 2015 - 08:47 AM, said:

Same here (re:chicago 1). Though, sometimes I get a 200-300ms ping even when using pingzapper thru Chicago. Also, some nights I get a lot of dc's from the Chicago1 or Chicago2 server, but it's infrequent. I still think its totally worth the money. I *do* wish that it had some better reporting like wtfast though - initially I wanted WTFast more because of its logging and graphs, but the fact that pingzapper "just worked" won me over.



I just opened a support ticket with pingzapper linking to this thread - I asked for some configuration advice or "best practices" that I can re-post here. If TWC won't put some pressure on telia to fix their poopy peering, maybe the pingzapper folks can at least ease the setup process.

Please share the response from Pingzapper.

[Smoked]

Austin, TX. Exactly the same as others in my area. Was consistently 80 ms before the server move around October 20. Now hover between 107 to 125 often going to 350 to 750. I have time warner as well. Ping to Canada using that city closest to server was 67 ms. Not sure why mwo server switch adds extra latency.

[NocturnalBeast]

Smoked, on 28 January 2015 - 10:12 AM, said:

Austin, TX. Exactly the same as others in my area. Was consistently 80 ms before the server move around October 20. Now hover between 107 to 125 often going to 350 to 750. I have time warner as well. Ping to Canada using that city closest to server was 67 ms. Not sure why mwo server switch adds extra latency.

http://pingzapper.com/ my friend.

[Inathero]

I experienced no change with pingzapper trial whatsoever, was exactly the same.

Do I really have to purchase it in order to successfully test it out?

[LobsterPete]

I have the same problem. I'm in San Diego and without pingzapper I can't get in one game without my ping rocketing to 500ms. If I use Pingzapper (and route it through Chicago 1) I can maybe get one game in before it goes to hell. So frustrating I'm pretty much done with MWO during primetime.

[Santanico Pandamonium]

The trial (PingZappr) didn't work for me... I had to purchase a 30 day subscription and put it in UDP mode. And it wasn't a simple install and run either... had to finagle with some of the settings.

But I'm running through Chicago 1... Ping stays a constant 88~130, from the Austin area.

However, there has been one problem. About 2 hrs into playing CW, at the peak of primetime, I get disconnected from the servers mid game... Kicked back to mech lab, and unable to rejoin or launch a new game. I have to close client and relaunch to get back in.

Never happened before using the pingzapper.

So essentially, my choices are 1) stuck with 500ms in prime time, 2) Use PingZapper and expect a DC at the height primetime.