141 replies to this topic

[Mechteric]

i have no doubt the patch did not do this, the only thing I'm trying to figure out now if its on their server's end, or if its somewhere on my end or my ISP's end. My only guess is that its not their server's end because I see other people getting the normal pings I usually get.

Edited by CapperDeluxe, 30 January 2013 - 06:40 PM.

[Akulakhan]

It wasn't the patch, guys, it's just a huge influx of data on one overtaxed router that cause this whole mess, that seemed to REALLY affect Verizon customers. This influx just happened to be occurring around abut the same time as the patch that introduced the Spider.

However, it seems that this issue is getting addressed tomorrow and there's not really anyone to blame, so sit tight.

[GalaxyBluestar]

aussie ping was 250-300 before patch and has remained so.

so i'm not in the op's boat here.

[Typatty]

Verizon customer on northeast of U.S. here, ping went from 50 to 200 recently. Glad to hear there's a fix in the works.

[BigJim]

My ping has gone from 120 to 180-190 with this patch, and I'm noticeably rubber-banding/warping whereas before my connection was rock solid.

[Mechteric]

I did a traceroute to mwomercs.com from my house last night and found at certain times (which is when I would see the higher pings) there was a significant jump in milliseconds response when going to some "pnap.net". So its going out of my house just fine to the first hop for roadrunner, but somewhere around Kansas is where it jumped up significantly (at least according to google maps the IP was in Wichita, Kansas). Apparently that IP is also owned by roadrunner, so something is definitely up with these ISPs.


I just tried this from work, which appears slightly different than from at home, but still shows that massive ping spike at pnap.net:
Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\>tracert www.mwomercs.com

Tracing route to www.mwomercs.com [70.42.29.74]
over a maximum of 30 hops:
...
8 165 ms 212 ms 207 ms border1.te7-1-bbnet1.tor001.pnap.net [70.42.24.132]
9 * * * Request timed out.


To see where it starts going bad for you, run 'tracert www.mwomercs.com' from your command line in windows.

Edited by CapperDeluxe, 31 January 2013 - 07:00 AM.

[Flapdrol]

Yesterday night my ingame ping was terrible. 120-200, always fluctuating. My ping to local sites was good (steady 22-24).

I played a game a few hours ago and it was a steady 113-115, just when it gets busy on the internet my latency to canada is all over the place. Maybe my provider cheaps out on their transatlantic contract, I dont know how those things go. I saw someone else from NL on yesterday night and he had a steady 95ms.

[ElmoWithAGun]

agentdavion, on 30 January 2013 - 02:23 PM, said:

recived a text from tech support that says the problem will be resolved on 1/31 by 5pm est...... i dont want to blowsmoke up my butt but YOUR WELCOME mwo land :-)

Bumping this to the top.

If what agentdavion says is true, would love to get some feedback from those that have been having this issue!

[Akulakhan]

Just logged in for a match after work from about 520-530 EST, still getting horribad pings in MWO and perfect pings everywhere else, unfortunately. So, same problem.

[DudeBroSki]

Yea verizon still didnt fix the problem.

[Akulakhan]

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\>tracert www.mwomercs.com

Tracing route to www.mwomercs.com [70.42.29.74]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dslrouter.westell.com [192.168.1.1]
2 41 ms 41 ms 45 ms 10.29.29.1
3 42 ms 42 ms 42 ms P15-1.SCTNPA-LCR-01.verizon-gni.net [130.81.197.
64]
4 46 ms 54 ms 47 ms so-5-0-2-0.NWRK-BB-RTR1.verizon-gni.net [130.81.
22.12]
5 55 ms 57 ms 56 ms xe-1-0-2-0.NY5030-BB-RTR1.verizon-gni.net [130.8
1.23.184]
6 59 ms 59 ms 59 ms 0.so-6-0-3.XT1.NYC4.ALTER.NET [152.63.17.85]
7 58 ms 58 ms 59 ms TenGigE0-5-0-0.GW8.NYC4.ALTER.NET [152.63.21.65]

8 155 ms 172 ms 158 ms tinet-gw.customer.alter.net [152.179.72.122]
9 176 ms 178 ms 178 ms xe-4-3-0.tor10.ip4.tinet.net [89.149.184.110]
10 172 ms 169 ms 169 ms internap-gw.ip4.tinet.net [77.67.70.94]
11 176 ms 175 ms 174 ms border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.1
96]

It's still that damn tinet-gw.customer.alter.net. I mean, just look at that jump from 7 to 8. I'm not sayin' Verizon isn't trying to fix it, but they sure haven't succeeded just yet.

Edited by Akulakhan, 31 January 2013 - 02:52 PM.

[ElmoWithAGun]

My trace route doesn't even complete...as soon as it hits border1.te9-1-bbnet2.tor001.pnap.net, all the hops after that just time out.

[Vedic]

I'm getting the same problem, and was hoping that Verizon fix would be in by now. No such luck:


1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 9 ms 6 ms L100.PHLAPA-VFTTP-99.verizon-gni.net [98.114.33.
1]
3 9 ms 7 ms 9 ms G0-6-3-4.PHLAPA-LCR-21.verizon-gni.net [130.81.140.90]
4 25 ms 117 ms 59 ms so-9-0-0-0.PHIL-BB-RTR1.verizon-gni.net [130.81.22.58]
5 11 ms 9 ms 9 ms xe-11-1-1-0.NY325-BB-RTR1.verizon-gni.net [130.81.23.54]
6 12 ms 9 ms 9 ms 0.so-0-0-0.XT1.NYC4.ALTER.NET [152.63.1.41]
7 18 ms 16 ms 11 ms TenGigE0-4-1-0.GW8.NYC4.ALTER.NET [152.63.21.69]
8 84 ms 82 ms 84 ms tinet-gw.customer.alter.net [152.179.72.122]
9 127 ms 130 ms 135 ms xe-4-3-0.tor10.ip4.tinet.net [89.149.184.110]
10 123 ms 122 ms 121 ms internap-gw.ip4.tinet.net [77.67.70.94]
11 138 ms 140 ms 144 ms border1.te7-1-bbnet1.tor001.pnap.net [70.42.24.132]

That's actually pretty good for this traceroute, but is pretty early versus when I usually play. Within an hour it's going to be in the 180s again.

I looked up xe-4-3-0.tor10.ip4.tinet.net, and it appears to be located in Germany. I can't imagine this is normal or correct - why are my packets moving from Philadelphia, over the Atlantic, and then back again?

[Akulakhan]

ElmoWithAGun, on 31 January 2013 - 02:56 PM, said:

My trace route doesn't even complete...as soon as it hits border1.te9-1-bbnet2.tor001.pnap.net, all the hops after that just time out.

Yeah, same.

@Vedic-When I originally sent in a ticket to MWO support, I actually said the ping "is like being from Europe," and that my ping seems to be worse during European peak play time (round about now) and after those across the pond go to bed (well, the ones that play into the wee hours, anyway) around 9 EST, my ping magically goes back to 70ms instead of the cringeworthy 180 I have during the day.

So if it is ACTUALLY going to Europe, then back, a lot of things make sense. But why would it do this?

Edited by Akulakhan, 31 January 2013 - 03:03 PM.

[Trev Firestorm]

Same issue, verizon fios...

[DrxAbstract]

This issue is not limited to Verizon FiOS. Obviously it's still unresolved, and i cant imagine it's possible to correct it while the hub is still active or that they would disable it for repairs during peak hours since it's still 'functional'... assuming they are aware of what the problem is yet. If Verizon is in fact responsible for and capable of fixing the error, add a minimum of 24 hours onto whatever timeline they give you, typically +2-3 days.

[ElmoWithAGun]

Damn Germans stealing our internets!

[Solaxxas]

ElmoWithAGun, on 31 January 2013 - 02:56 PM, said:

My trace route doesn't even complete...as soon as it hits border1.te9-1-bbnet2.tor001.pnap.net, all the hops after that just time out.

That's because the mwomercs servers don't accept ping requests, so it's normal.

[Flapdrol]

didn't have the problem today, yesterday was terrible though.

Edited by Flapdrol, 31 January 2013 - 03:38 PM.

[Vedic]

I have no clue why we were going through Germany, but all those tinet.net servers are German - that's 3-4 hops around the EU before crossing back to Atlanta, GA. Bizarre. It explains what's going on with the pings, but not why we're being routed like that.

Hopefully someone with more knowledge of networks like this can explain if this is Verizon or PGI's ISP's problem? It's not the router slowing us down per se, but the route we're taking to get to the server. All the nodes seem very reasonable in their ping times...for being 3000 miles away!