Higher Ping Times After Patch?
#101
Posted 04 February 2013 - 04:42 PM
#102
Posted 04 February 2013 - 05:29 PM
ElmoWithAGun, on 04 February 2013 - 04:42 PM, said:
It began for me just prior to 2 patches ago... so the issue doesnt coincide with any MWO patch as far as i know. I've logged on at 6am EST and had my normal 50-60ms ping and i've watched it slowly, 3-5ms every game or two, climb from 50ms up to 120ms from 6am to 8am and 120 to 250ms from 8am to 10am. At that point it literally bounces between 170-250ms from 10am straight on to 12 midnight in-game then starts decreasing slowly down to 50ms again after that, like clockwork. It seems the best times to get your 'normal' ping while playing MWO, consistently, is from 1am to 6am EST.
Whose fault it is, is unclear to me. The issue, however, does not coincide with an MWO patch, as much as people like to claim it does.
#103
Posted 04 February 2013 - 06:12 PM
DrxAbstract, on 04 February 2013 - 05:29 PM, said:
Whose fault it is, is unclear to me. The issue, however, does not coincide with an MWO patch, as much as people like to claim it does.
mine started well over a month ago
the simple fact remains that if u live on the east coast u should not see hirer then about 70 ping at most depending on ur bandwitdh
#104
Posted 04 February 2013 - 06:17 PM
I check both ips and they are the same
C:\Users\Jason>tracert 70.42.29.75
Tracing route to 70.42.29.75 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.254
2 7 ms 6 ms 6 ms 10.145.xxx.x
3 49 ms 49 ms 49 ms toroonxndr02.bb.telus.com [154.11.6.19]
4 49 ms 50 ms 49 ms 209.29.76.50
5 50 ms 49 ms 49 ms border1.te7-1-bbnet1.tor001.pnap.net [70.42.24.1
32]
6 * 52 ms * 70.42.29.65
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.
#105
Posted 04 February 2013 - 08:06 PM
@WhistlR: The ping problems we're talking about are more specifically affecting East Coast US players, narrowed down to the tinet-gw.customer.alter.net router and the nodes that come after it. Looking at your traceroute, you're only a few hops from the PGI server - are you sure the lag is ping-related? You'd need to be able to re-create that ping with a traceroute to know where it's coming from. It might just be a local hardware problem that seems like lag, and that's preferable because you can fix it instead of waiting on Verizon's lazy butts...
#106
Posted 05 February 2013 - 02:43 PM
#107
Posted 05 February 2013 - 02:54 PM
Blargh, I should just switch ISPs, shouldn't I?
#108
Posted 05 February 2013 - 04:33 PM
#109
Posted 06 February 2013 - 01:40 PM
I'm so sick of that mech, but trying to line up shots with this kind of ping is horrendous.
#110
Posted 06 February 2013 - 02:03 PM
#111
Posted 06 February 2013 - 02:12 PM
Icebound, on 06 February 2013 - 01:40 PM, said:
I'm so sick of that mech, but trying to line up shots with this kind of ping is horrendous.
Think about how I feel with with my dual AC/20 cat. I literally have to predict where my target is going to be.
#112
Posted 08 February 2013 - 04:08 PM
#113
Posted 08 February 2013 - 04:20 PM
I haven't noticed any actual lag in game though, haven't had to lead at all.
Interesting indeed.
#114
Posted 08 February 2013 - 04:40 PM
Which is why I switched ISPs, my ping times have only gotten worse.
#115
Posted 08 February 2013 - 06:40 PM
#116
Posted 10 February 2013 - 05:38 AM
I have finally decided to throw the towel in and shelve MWO for the time being. The combination of this and lack of a future this game has going for it isn't enough to keep supporting it (in my opinion).
#117
Posted 10 February 2013 - 06:20 AM
ElmoWithAGun, on 10 February 2013 - 05:38 AM, said:
I have finally decided to throw the towel in and shelve MWO for the time being. The combination of this and lack of a future this game has going for it isn't enough to keep supporting it (in my opinion).
This is not an issue PGI has any jurisdiction over. It's a gateway hub on the Verizon network grid that the East Coast is routed through to reach the MWO server, and until Verizon decides to fix it so we're not all be routed to Germany and back again or PGI changes their server hosting location/carrier, it is going to remain an issue... While Verizon is technically at fault, dont hold your breath on 'any time soon'.
#118
Posted 10 February 2013 - 11:41 AM
DrxAbstract, on 10 February 2013 - 06:20 AM, said:
No where in my post did I claim that PGI is responsible.
#119
Posted 10 February 2013 - 12:38 PM
I traced the route from where I am, and the highest ping was in Toronto, at 94ms. That does not account for the (literally) >9000ms pings I've been getting in a match.
Edit: I'm in California, San Jose.
Edited by Guy Grand, 10 February 2013 - 12:53 PM.
#120
Posted 10 February 2013 - 01:14 PM
Guy Grand, on 10 February 2013 - 12:38 PM, said:
I traced the route from where I am, and the highest ping was in Toronto, at 94ms. That does not account for the (literally) >9000ms pings I've been getting in a match.
Edit: I'm in California, San Jose.
Well East Coast Verizon definately does have an issue, my game go to where I had to lead frigging capapults.
Lo and behold check my 60/30Mb connection, I'm getting 6Mb at best with a couple local servers, under 3Mb to the Toronto area.
FiOS need to fix their ****.
16 user(s) are reading this topic
0 members, 16 guests, 0 anonymous users