184 replies to this topic

[Kh0rn]

So the question is why is this only affecting certain people. As you said Vertical all other use of the internet is fine but as soon as you try too play MWO the ping just go's haywire but as I am seeing now this is a more wide spread problem then I knew. All we can do is hope and pray for the next patch too resolve this problem.

[ice trey]

I'm currently in Japan, but I haven't been having this problem.

Currently sits between 180 and 200 ping.

[Caswallon]

Been having a similar thing to the OP though not quite as bad.
Pre patch usual ping 130 - 140 ish
Post Patch Ping 117 - 350+ with it changing every second or so. Occasional spikes to 2000+

Got the routine down by now so checked all the usual suspects my end. Get a B+ from Pingtest on my connection to Canada so doubt its that. Made no changes here to the hardware either.

Also the dump out of game incidence is up even though my voice com line remains active and open so I know its an MWO thing not an overall connectivity issue.

I wonder if they ran an optimising pass on certain localities but not others. Please to hear that folks Like Ice trey above have less or no issues, but there are too many saying the same sort of thing on these forums for it to have been a co incidence. Something got borked for EU and some other areas last patch I am sure.

[Kh0rn]

I have heard this from many people that this is a large problem and it happened directly after the patch. I ran checks with my line time and time again all other functions and even games have no problem like on MWLL 245 ping so I guess some where in MWO something went wrong during the patch for some people.

[Appogee]

My ping went from a consistent 220 to consistent 300 after the Dec 17 patch.

[John E]

my ping still ranges from 500 - 1200ms, before the patch it would sit at 230ms

below is my pingtest to sudbury

Edited by John E, 23 December 2013 - 01:00 PM.

[FrozenAzer]

Just to put my oar in. I've had the exact same same problem. Prior to the patch my ping was unstable but usually hung around 270 to 300. Now it sits anywhere between 1500 to 2500. PingPlotter gives a ping to mwomercs.com of 300. Oddly enough my ping comes down to the mid to high hundreds at the end of each match. Hope there is some solution to this.

[WVAnonymous]

OK, I won't complain. I started reading this because my ping increased 50%, but it was from 80 to 120.

If all you guys are playing with ping over 200, I guess I'll be fine.


Edit:

For those of you running ping tests, how do you determine what the IP address is of the MWO server?

Edited by WVAnonymous, 23 December 2013 - 03:19 PM.

[John E]

Currently I am using VPN (https://www.privateinternetaccess.com) and setting it to torronto and now the ping is at 300-400ms..

[John E]

found a different Toronto server to connect to using vpn and now my ping is back to 250ms, but i hope you guys fix the issue since i doubt most people would be willing to leverage vpn to play mwo

[MarauderBronze]

The IP of the MWO servers is usually provided by PGI support when you submit a trouble ticket. For reference, it is 70.42.29.65. I only post it here because I've previously seen it on multiple threads and reddit.

[PenitentTangent]

I'm glad to know I'm not the only person who's repairing their roof from the latest ping spike.

[Kh0rn]

I'm willing too try anything right now VPN included so I can play again. Its just so bad its not worth playing I really hope very very soon a fix will solve this problem. It seems too be on the increase.

[FrozenAzer]

I gave using a vpn a try and my ping stabilized at 300. Not really a solution though as JohnE says.

[John E]

try using cyber ghost 5 its a free vpn if you dont want to spend money. and look for the LA/washington connection and it should give you a ping of 260-280ms. its better than playing with 2k ping

Edited by John E, 26 December 2013 - 06:58 AM.

[Caswallon]

Over here in the UK has gone up since last patch (usual story Ping up: fps down :same as EVERY SINGLE PATCH EVER bar one...!) But more importantly this patch, the jitter is massivly increased. SO hello rubber band city!

Pre patch Ping had crept up from the 75 when I started playing a year ago to about 135. Post patch we get (the wife and I both play on the same line - this is not the royal "we" here sorry for any confusion) 120 - 350+ ping with it jittering (changing) every second or so. I tried a free vpn and it did give a stable ping of about 230- 250 which is sorta an improvement but not much. It was interesting that the vpn stabilised stuff so much something is whacky between here and Canada on the open routes thats for sure..

[Gambit001]

I've been experiencing bad ping since Wed or Thu last week.
I'm based in the Philippines and my normal ping in-game is somewhere between 240-260ms.
Today, I got a ping of 1.6k.

Ping and tracert to 70.42.29.65 yielded higher than normal ping.
Here are the results:

Ping Test

Spoiler

C:\>ping -t 70.42.29.65

Pinging 70.42.29.65 with 32 bytes of data:
Reply from 70.42.29.65: bytes=32 time=257ms TTL=49
Reply from 70.42.29.65: bytes=32 time=274ms TTL=49
Reply from 70.42.29.65: bytes=32 time=259ms TTL=49
Reply from 70.42.29.65: bytes=32 time=276ms TTL=49
Reply from 70.42.29.65: bytes=32 time=264ms TTL=49
Reply from 70.42.29.65: bytes=32 time=276ms TTL=49
Reply from 70.42.29.65: bytes=32 time=255ms TTL=49
Reply from 70.42.29.65: bytes=32 time=276ms TTL=49
Reply from 70.42.29.65: bytes=32 time=264ms TTL=49
Reply from 70.42.29.65: bytes=32 time=276ms TTL=49
Reply from 70.42.29.65: bytes=32 time=265ms TTL=49
Reply from 70.42.29.65: bytes=32 time=274ms TTL=49
Reply from 70.42.29.65: bytes=32 time=270ms TTL=49
Reply from 70.42.29.65: bytes=32 time=270ms TTL=49
Reply from 70.42.29.65: bytes=32 time=283ms TTL=49
Reply from 70.42.29.65: bytes=32 time=263ms TTL=49
Reply from 70.42.29.65: bytes=32 time=268ms TTL=49
Reply from 70.42.29.65: bytes=32 time=270ms TTL=49
Reply from 70.42.29.65: bytes=32 time=305ms TTL=49
Reply from 70.42.29.65: bytes=32 time=267ms TTL=49
Reply from 70.42.29.65: bytes=32 time=275ms TTL=49
Reply from 70.42.29.65: bytes=32 time=264ms TTL=49
Reply from 70.42.29.65: bytes=32 time=274ms TTL=49
Reply from 70.42.29.65: bytes=32 time=274ms TTL=49
Reply from 70.42.29.65: bytes=32 time=276ms TTL=49
Reply from 70.42.29.65: bytes=32 time=276ms TTL=49
Reply from 70.42.29.65: bytes=32 time=260ms TTL=49
Reply from 70.42.29.65: bytes=32 time=270ms TTL=49
Reply from 70.42.29.65: bytes=32 time=264ms TTL=49
Reply from 70.42.29.65: bytes=32 time=270ms TTL=49
Reply from 70.42.29.65: bytes=32 time=270ms TTL=49
Reply from 70.42.29.65: bytes=32 time=266ms TTL=49
Reply from 70.42.29.65: bytes=32 time=298ms TTL=49
Reply from 70.42.29.65: bytes=32 time=273ms TTL=49
Reply from 70.42.29.65: bytes=32 time=281ms TTL=49
Reply from 70.42.29.65: bytes=32 time=319ms TTL=49
Reply from 70.42.29.65: bytes=32 time=335ms TTL=49
Reply from 70.42.29.65: bytes=32 time=260ms TTL=49
Reply from 70.42.29.65: bytes=32 time=276ms TTL=49
Reply from 70.42.29.65: bytes=32 time=340ms TTL=49
Reply from 70.42.29.65: bytes=32 time=335ms TTL=49
Reply from 70.42.29.65: bytes=32 time=281ms TTL=49
Reply from 70.42.29.65: bytes=32 time=268ms TTL=49
Reply from 70.42.29.65: bytes=32 time=280ms TTL=49
Reply from 70.42.29.65: bytes=32 time=290ms TTL=49
Reply from 70.42.29.65: bytes=32 time=311ms TTL=49
Reply from 70.42.29.65: bytes=32 time=260ms TTL=49
Reply from 70.42.29.65: bytes=32 time=275ms TTL=49
Reply from 70.42.29.65: bytes=32 time=260ms TTL=49
Reply from 70.42.29.65: bytes=32 time=274ms TTL=49
Reply from 70.42.29.65: bytes=32 time=259ms TTL=49
Reply from 70.42.29.65: bytes=32 time=268ms TTL=49
Reply from 70.42.29.65: bytes=32 time=271ms TTL=49
Reply from 70.42.29.65: bytes=32 time=274ms TTL=49
Reply from 70.42.29.65: bytes=32 time=272ms TTL=49
Reply from 70.42.29.65: bytes=32 time=267ms TTL=49
Reply from 70.42.29.65: bytes=32 time=273ms TTL=49
Reply from 70.42.29.65: bytes=32 time=262ms TTL=49
Reply from 70.42.29.65: bytes=32 time=274ms TTL=49
Reply from 70.42.29.65: bytes=32 time=259ms TTL=49
Reply from 70.42.29.65: bytes=32 time=275ms TTL=49
Reply from 70.42.29.65: bytes=32 time=256ms TTL=49
Reply from 70.42.29.65: bytes=32 time=273ms TTL=49
Reply from 70.42.29.65: bytes=32 time=265ms TTL=49
Reply from 70.42.29.65: bytes=32 time=277ms TTL=49
Reply from 70.42.29.65: bytes=32 time=269ms TTL=49
Reply from 70.42.29.65: bytes=32 time=273ms TTL=49
Reply from 70.42.29.65: bytes=32 time=265ms TTL=49
Reply from 70.42.29.65: bytes=32 time=274ms TTL=49
Reply from 70.42.29.65: bytes=32 time=266ms TTL=49
Reply from 70.42.29.65: bytes=32 time=273ms TTL=49
Reply from 70.42.29.65: bytes=32 time=271ms TTL=49
Reply from 70.42.29.65: bytes=32 time=263ms TTL=49
Reply from 70.42.29.65: bytes=32 time=266ms TTL=49
Reply from 70.42.29.65: bytes=32 time=272ms TTL=49
Reply from 70.42.29.65: bytes=32 time=260ms TTL=49
Reply from 70.42.29.65: bytes=32 time=275ms TTL=49
Reply from 70.42.29.65: bytes=32 time=253ms TTL=49
Reply from 70.42.29.65: bytes=32 time=275ms TTL=49
Reply from 70.42.29.65: bytes=32 time=261ms TTL=49
Reply from 70.42.29.65: bytes=32 time=275ms TTL=49
Reply from 70.42.29.65: bytes=32 time=261ms TTL=49
Reply from 70.42.29.65: bytes=32 time=275ms TTL=49
Reply from 70.42.29.65: bytes=32 time=272ms TTL=49
Reply from 70.42.29.65: bytes=32 time=275ms TTL=49
Reply from 70.42.29.65: bytes=32 time=267ms TTL=49
Reply from 70.42.29.65: bytes=32 time=275ms TTL=49
Reply from 70.42.29.65: bytes=32 time=256ms TTL=49
Reply from 70.42.29.65: bytes=32 time=274ms TTL=49
Reply from 70.42.29.65: bytes=32 time=262ms TTL=49
Reply from 70.42.29.65: bytes=32 time=269ms TTL=49
Reply from 70.42.29.65: bytes=32 time=275ms TTL=49
Reply from 70.42.29.65: bytes=32 time=271ms TTL=49
Reply from 70.42.29.65: bytes=32 time=270ms TTL=49
Reply from 70.42.29.65: bytes=32 time=272ms TTL=49
Reply from 70.42.29.65: bytes=32 time=275ms TTL=49
Reply from 70.42.29.65: bytes=32 time=265ms TTL=49
Reply from 70.42.29.65: bytes=32 time=274ms TTL=49
Reply from 70.42.29.65: bytes=32 time=250ms TTL=49
Reply from 70.42.29.65: bytes=32 time=271ms TTL=49
Reply from 70.42.29.65: bytes=32 time=268ms TTL=49
Reply from 70.42.29.65: bytes=32 time=272ms TTL=49
Reply from 70.42.29.65: bytes=32 time=266ms TTL=49
Reply from 70.42.29.65: bytes=32 time=271ms TTL=49
Reply from 70.42.29.65: bytes=32 time=271ms TTL=49
Reply from 70.42.29.65: bytes=32 time=270ms TTL=49
Reply from 70.42.29.65: bytes=32 time=262ms TTL=49
Reply from 70.42.29.65: bytes=32 time=276ms TTL=49
Reply from 70.42.29.65: bytes=32 time=258ms TTL=49
Reply from 70.42.29.65: bytes=32 time=276ms TTL=49
Reply from 70.42.29.65: bytes=32 time=259ms TTL=49
Reply from 70.42.29.65: bytes=32 time=265ms TTL=49
Reply from 70.42.29.65: bytes=32 time=275ms TTL=49
Reply from 70.42.29.65: bytes=32 time=268ms TTL=49
Reply from 70.42.29.65: bytes=32 time=271ms TTL=49
Reply from 70.42.29.65: bytes=32 time=269ms TTL=49
Reply from 70.42.29.65: bytes=32 time=267ms TTL=49
Reply from 70.42.29.65: bytes=32 time=274ms TTL=49
Reply from 70.42.29.65: bytes=32 time=261ms TTL=49
Reply from 70.42.29.65: bytes=32 time=274ms TTL=49
Reply from 70.42.29.65: bytes=32 time=263ms TTL=49
Reply from 70.42.29.65: bytes=32 time=275ms TTL=49
Reply from 70.42.29.65: bytes=32 time=257ms TTL=49
Reply from 70.42.29.65: bytes=32 time=276ms TTL=49
Reply from 70.42.29.65: bytes=32 time=280ms TTL=49
Reply from 70.42.29.65: bytes=32 time=320ms TTL=49
Reply from 70.42.29.65: bytes=32 time=325ms TTL=49
Reply from 70.42.29.65: bytes=32 time=279ms TTL=49
Reply from 70.42.29.65: bytes=32 time=340ms TTL=49
Reply from 70.42.29.65: bytes=32 time=306ms TTL=49
Reply from 70.42.29.65: bytes=32 time=271ms TTL=49
Reply from 70.42.29.65: bytes=32 time=322ms TTL=49
Reply from 70.42.29.65: bytes=32 time=319ms TTL=49
Reply from 70.42.29.65: bytes=32 time=347ms TTL=49
Reply from 70.42.29.65: bytes=32 time=293ms TTL=49
Reply from 70.42.29.65: bytes=32 time=321ms TTL=49
Reply from 70.42.29.65: bytes=32 time=278ms TTL=49
Reply from 70.42.29.65: bytes=32 time=308ms TTL=49
Reply from 70.42.29.65: bytes=32 time=267ms TTL=49
Reply from 70.42.29.65: bytes=32 time=275ms TTL=49
Reply from 70.42.29.65: bytes=32 time=471ms TTL=49
Reply from 70.42.29.65: bytes=32 time=262ms TTL=49
Reply from 70.42.29.65: bytes=32 time=275ms TTL=49
Reply from 70.42.29.65: bytes=32 time=268ms TTL=49
Reply from 70.42.29.65: bytes=32 time=275ms TTL=49
Reply from 70.42.29.65: bytes=32 time=265ms TTL=49
Reply from 70.42.29.65: bytes=32 time=277ms TTL=49
Reply from 70.42.29.65: bytes=32 time=264ms TTL=49
Reply from 70.42.29.65: bytes=32 time=276ms TTL=49
Reply from 70.42.29.65: bytes=32 time=267ms TTL=49
Reply from 70.42.29.65: bytes=32 time=268ms TTL=49
Reply from 70.42.29.65: bytes=32 time=268ms TTL=49
Reply from 70.42.29.65: bytes=32 time=272ms TTL=49
Reply from 70.42.29.65: bytes=32 time=263ms TTL=49
Reply from 70.42.29.65: bytes=32 time=275ms TTL=49
Reply from 70.42.29.65: bytes=32 time=258ms TTL=49
Reply from 70.42.29.65: bytes=32 time=269ms TTL=49
Reply from 70.42.29.65: bytes=32 time=263ms TTL=49
Reply from 70.42.29.65: bytes=32 time=259ms TTL=49
Reply from 70.42.29.65: bytes=32 time=276ms TTL=49
Reply from 70.42.29.65: bytes=32 time=264ms TTL=49
Reply from 70.42.29.65: bytes=32 time=274ms TTL=49
Reply from 70.42.29.65: bytes=32 time=262ms TTL=49
Reply from 70.42.29.65: bytes=32 time=269ms TTL=49
Reply from 70.42.29.65: bytes=32 time=274ms TTL=49
Reply from 70.42.29.65: bytes=32 time=266ms TTL=49
Reply from 70.42.29.65: bytes=32 time=276ms TTL=49
Reply from 70.42.29.65: bytes=32 time=261ms TTL=49
Reply from 70.42.29.65: bytes=32 time=274ms TTL=49
Reply from 70.42.29.65: bytes=32 time=256ms TTL=49
Reply from 70.42.29.65: bytes=32 time=260ms TTL=49
Reply from 70.42.29.65: bytes=32 time=275ms TTL=49
Reply from 70.42.29.65: bytes=32 time=266ms TTL=49
Reply from 70.42.29.65: bytes=32 time=277ms TTL=49
Reply from 70.42.29.65: bytes=32 time=258ms TTL=49
Reply from 70.42.29.65: bytes=32 time=273ms TTL=49
Reply from 70.42.29.65: bytes=32 time=271ms TTL=49
Reply from 70.42.29.65: bytes=32 time=262ms TTL=49
Reply from 70.42.29.65: bytes=32 time=276ms TTL=49
Reply from 70.42.29.65: bytes=32 time=259ms TTL=49
Reply from 70.42.29.65: bytes=32 time=268ms TTL=49
Reply from 70.42.29.65: bytes=32 time=274ms TTL=49
Request timed out.
Reply from 70.42.29.65: bytes=32 time=270ms TTL=49
Reply from 70.42.29.65: bytes=32 time=275ms TTL=49
Reply from 70.42.29.65: bytes=32 time=272ms TTL=49
Reply from 70.42.29.65: bytes=32 time=268ms TTL=49
Reply from 70.42.29.65: bytes=32 time=268ms TTL=49

Ping statistics for 70.42.29.65:
Packets: Sent = 188, Received = 187, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 250ms, Maximum = 471ms, Average = 274ms
Control-C
^C
C:\>

Tracert

Spoiler

C:\>tracert -d 70.42.29.65

Tracing route to 70.42.29.65 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 19 ms 17 ms 16 ms 112.210.128.1
3 16 ms 16 ms 16 ms 119.93.255.233
4 19 ms 20 ms 19 ms 210.213.131.58
5 16 ms 16 ms 16 ms 210.213.131.89
6 255 ms 256 ms 255 ms 209.58.33.57
7 323 ms 324 ms 323 ms 64.86.252.45
8 314 ms 310 ms 312 ms 66.198.144.73
9 312 ms 312 ms 312 ms 66.198.144.58
10 303 ms 317 ms 299 ms 64.86.79.2
11 310 ms 310 ms 307 ms 63.243.172.41
12 262 ms 265 ms 273 ms 216.6.49.2
13 272 ms 275 ms 275 ms 70.42.24.132
14 277 ms 276 ms 274 ms 70.42.29.65

Trace complete.

C:\>

As you can see, the tests return normal to slightly higher than average results, but in-game, the minimum ping I could get was 400ms.
Most of the time it is somewhere around 600ms.
Hitting 1.6k after logging-in today is a new high. It also makes the game unplayable for me.
If I had premium time running, I would certainly and definitely complain.

If latency is not the issue, what could it be, and how could it be resolved?

[DrxAbstract]

I've noticed a massive (Relative) increase in my ping since Wednesday 12/25. Going from 50-70 to 130-160. After running a trace and using an IP database i've discovered my signal is being routed in this manner:

New York(Source)
Kansas (1=130.81.198.202 || 2=130.81.162.20 || 3=130.81.162.20 || 4=152.63.3.46)
New York (5=152.63.21.129)
Ireland(6=141.136.107.94 || 7=77.67.70.94)
Georgia U.S. (8=70.42.24.132 || 9=70.42.29.65)

All i can say is wtf Ireland? This reminds me of the time a few months ago when a faulty service node activated and sent half the Eastern Seaboard of the U.S. through Europe and back when accessing the MWO servers. So it may be a similar situation again, or my signal is getting hijacked by a service in Ireland for the sake of billing my ISP for the traffic... /paranoid

Either way, it's not a stable 140 ping as I experience the effects of a 500+ ping latency repeatedly throughout my matches.

Edited by DrxAbstract, 27 December 2013 - 01:26 AM.

[ShadowDarter]

ping stable at 220, No issues from Sydney Australia.

[A Mach Twelve Jellyfish]

Alright, I've got premium time running so this is getting really annoying for me. When I first started I purchased the Phoenix. I enjoyed an easily playable 175-250 ping. A month into the premium time (Most recent patch) the ping went to hell. I've gotten a minimum of 350 since patch and an average of 440-600. I cant play the game anymore. This. Should. Not. Be. Happening. I've tried every fix I could think of. I'm playing from South Korea on a 100mbps connection and on average most North American servers give me an average of 150 ping. If this isnt fixed soon count me out for future PGI endeavors. I was so looking forward to the Clan Invasion but, after this, forget it.