95 replies to this topic

[Hotthedd]

My ISP is AT&T as well.

Since the beginning of September my ping to the Montreal server has spiked up up from an average of <70 to around 150-160.

Trace route confirms that after bouncing all over the USA, I am always routed to Europe, whether it is Germany, France, or Spain (Or even all 3 on occasion)

[Dimento Graven]

Hotthedd, on 21 September 2016 - 08:57 AM, said:

My ISP is AT&amp;T as well.

Since the beginning of September my ping to the Montreal server has spiked up up from an average of &lt;70 to around 150-160.

Trace route confirms that after bouncing all over the USA, I am always routed to Europe, whether it is Germany, France, or Spain (Or even all 3 on occasion)

Could you post a tracert here?

I have various people from AT&T referencing this thread.

[Hotthedd]

Latest tracert:

192.168.1.254 (home)
184.46.139.1 (Baton Rouge, LA)
72.157.32.31 (Atlanta, GA)
12.122.162.221 (either NJ or Los Angeles)
12.122.162.226 " " " " "
" " " " " timed out
12.123.16.77 (Dallas, TX)
192.205.36.94 (either Indianapolis or San Francisco)
" " " " " timed out
" " " " " timed out
" " " " " timed out
37.187.232.46 (Roubaix, France)
37.187.232.86 (Strausbourg, France)
213.186.32.251 (Paris, France)
37.187.36.186 (Paris, France)
91.121.215.215 (Roubaix, France)
192.99.109.192 (MWO - Montreal)

[Dimento Graven]

FYI: Got proof positive (not just anecdotal evidence) that the issue is not specific to MWO.

Went to the bhs.proof.ovh.net, site and ran their test utility, specifying a Canadian test server, got similar results:



So if anyone else is attempting to work this issue with AT&T support, don't let 'em distract the conversation by trying to blame the mwomercs.com server.

Edited by Dimento Graven, 22 September 2016 - 06:33 AM.

[Ithilid]

I've gone to an old school hack / trick / workaround. I started playing in a windowed mode. I doesn't changed my ping but the jitters and lags have stopped it seems.

I'm happy to be back playing again

[Splatshot]

In KC

Have AT&T u-verse

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

C:\Users\xxxx>tracert mwomercs.com

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

1 <1 ms <1 ms <1 ms dsldevice.attlocal.net [192.168.1.254]
2 4 ms 2 ms 24 ms 172-13-0-1.lightspeed.mssnks.sbcglobal.net [172.
13.0.1]
3 4 ms 3 ms 3 ms 71.150.19.34
4 4 ms 3 ms 3 ms 71.150.32.188
5 7 ms 3 ms 3 ms 12.83.42.157
6 17 ms 15 ms 15 ms gar25.dlstx.ip.att.net [12.122.85.233]
7 17 ms 15 ms 15 ms 192.205.36.94
8 * * * Request timed out.
9 * * * Request timed out.
10 129 ms 127 ms 127 ms hundredgige0-14-0-0.ffttr5.Frankfurt.opentransit
.net [193.251.128.12]
11 125 ms 126 ms 125 ms be100-110.fra-1-a9.de.eu [37.187.232.46]
12 129 ms 128 ms 128 ms be1-1170.sbg-g1-a9.fr.eu [37.187.232.86]
13 126 ms 126 ms 126 ms vl21.sbg-g1-a75.fr.eu [213.186.32.251]
14 129 ms 129 ms 129 ms sbg-g5-a9.fr.eu [37.187.36.186]
15 134 ms 133 ms 133 ms mad-3-4m.es.eu [91.121.215.215]
16 133 ms 132 ms 132 ms 192.99.109.143

Trace complete.

C:\Users\xxxx>

Edited by Splatshot, 22 September 2016 - 09:19 PM.

[Dimento Graven]

Yeah, I'm fairly certain this is an AT&T router that's causing the problem. The interesting thing is, I've found that OVH has a peering point in DFW area, so it's apparent that AT&T's network is not optimized if they're not utilizing this 'local' peering point to get those of us in the SW onto the NA OVH network.

Given that those of us have a problem all have a route that takes us through the router 192.150.36.94, and things go teats up from that point (some of you even have one less 'unknown' hop than I do), I'm just going to assume that it's the router at 192.150.36.94, that's the cause of our problems (until AT&T gets off their *** proves otherwise), that's the last 'decent' hop before the fit hits the shan.

Update: Subsequent investigations show that AT&T is not peer at any exchange point OVH has been peered...

Edited by Dimento Graven, 22 September 2016 - 01:36 PM.

[Splatshot]

Mine gets to ATT SF - 192.205.36.94 and goes to unknown crap then...

[Davegt27]

what is the purpose of running a trace route? (and how do you do it?)

one things for sure in my case---I cant play the game until i get better internet

it is interesting seeing what does and does not work in game

for example my KDK SB blew up because I could turn MASC on but not off

Dakka does not work well
all Mechs run in place except me when I shoot it does no damage but they can shoot me and do damage

cant get a lock-on so I cant fire my streaks

I can play 1 to 3 matches in the early AM
I cant really tell if things will work right until I am in game which hurt the other players on my team
so I cut back to one attempt per day

edit:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Users\davepc7>tracert mwomercs.com
Tracing route to mwomercs.com [192.99.109.143]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.42.129
2 1789 ms 557 ms 517 ms 10.167.243.113
3 452 ms 797 ms 547 ms 10.166.27.5
4 484 ms 1717 ms 537 ms 10.166.27.11
5 509 ms 557 ms 1617 ms 10.164.72.4
6 400 ms 487 ms 797 ms 10.164.165.19
7 402 ms 456 ms 457 ms lag-198.ear2.LosAngeles1.Level3.net [4.71.136.21]
8 * * * Request timed out.
9 877 ms 517 ms 537 ms be100-155.nwk-5-a9.nj.us [198.27.73.29]
10 763 ms 537 ms 557 ms be10-1018.bhs-g2-a9.qc.ca [192.99.146.101]
11 467 ms 1597 ms 537 ms vl21.bhs-g2-a75.qc.ca [198.27.73.91]
12 508 ms 527 ms 517 ms bhs-g5-a9.qc.ca [178.32.135.196]
13 458 ms 547 ms 547 ms 192.99.109.143
Trace complete.

Edited by Davegt27, 24 September 2016 - 04:09 AM.

[Splatshot]

command line

type tracert mwomercs.com

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

C:\Users\youruser>tracert mwomercs.com

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

1 <1 ms 1 ms <1 ms dsldevice.attlocal.net [192.168.1.254]
2 6 ms 3 ms 2 ms 172-13-0-1.lightspeed.mssnks.sbcglobal.net [172.
13.0.1]
3 4 ms 3 ms 3 ms 71.150.19.34
4 5 ms 3 ms 8 ms 71.150.32.188
5 6 ms 7 ms 6 ms 12.83.42.157
6 13 ms 15 ms 15 ms gar25.dlstx.ip.att.net [12.122.85.233]
7 16 ms 15 ms 15 ms 192.205.36.94
8 * * * Request timed out.
9 * * * Request timed out.
10 124 ms 128 ms 126 ms hundredgige0-14-0-0.ffttr5.Frankfurt.opentransit
.net [193.251.128.12]
11 144 ms 145 ms 145 ms be100-110.fra-1-a9.de.eu [37.187.232.46]
12 131 ms 130 ms 130 ms be1-1170.sbg-g1-a9.fr.eu [37.187.232.86]
13 127 ms 127 ms 129 ms vl21.sbg-g1-a75.fr.eu [213.186.32.251]
14 128 ms 130 ms 128 ms sbg-g5-a9.fr.eu [37.187.36.186]
15 133 ms 136 ms 136 ms mad-3-4m.es.eu [91.121.215.215]
16 136 ms 134 ms 133 ms 192.99.109.143

Trace complete.

Still the same...

[MadCatMk11]

Having the same issue. Seems as if i'm being routed through the European server when requesting the American one.

[Splatshot]

got this from AT&T today.



Sep 27, 2016 2:42:16 PM


We dont really have much control of how other networks route your traffic. After it leaves our network then its out of our hands. Your complaint is most likely with RIPE networks on the other side of the pond.[/color]


But I did the trace route and it after it hit over there it stayed over there with horrendous ping times. I would suspect that those 3 routers that timed out might have something to do with it. They could have an error that is causing latency, OR it just doesnt respond to pings.


Community Support

Edited by Splatshot, 27 September 2016 - 01:57 PM.

[Dimento Graven]

Splatshot, on 27 September 2016 - 01:56 PM, said:

got this from AT&amp;T today.



Sep 27, 2016 2:42:16 PM


We dont really have much control of how other networks route your traffic. After it leaves our network then its out of our hands. Your complaint is most likely with RIPE networks on the other side of the pond.[/color]


But I did the trace route and it after it hit over there it stayed over there with horrendous ping times. I would suspect that those 3 routers that timed out might have something to do with it. They could have an error that is causing latency, OR it just doesnt respond to pings.


Community Support

Update- The service guy reread the post after the next outburst and now understands the issue.

It's going on for more investigation.

Edited by Dimento Graven, 27 September 2016 - 02:30 PM.

[Splatshot]

Yep, seems we may finally be getting some where.

[Dimento Graven]

@PGI - In the AT&T forum thread (https://forums.att.c.../4935227#M20570), we have an AT&T employee asking for a contact at OVH they can discuss this issue with.

Could someone from PGI go to that forum and PM them the information, OR, you could PM me, and I'll forward it to the AT&T rep?

Either way, OVH doesn't seem to be responsive (currently) on their generic support email addresses.

[Bobby Jubraj]

Hey everyone,

Just wanted to let you all know what was happening with this. We're in contact with OVH while they try to pursue a resolution with AT&T. While there isn't anything we can do directly to speed this along, we'll try to keep everyone posted with any updates we receive regarding any changes to these routing issues.

[Dimento Graven]

Update from AT&T:

Quote

I have received email from OVH and I have replied with the information we show. So now we wait.

As was stated... and now we wait...

[Splatshot]

Its fixed for me, ping back to 40ish.

[Hotthedd]

Was something corrected? My ping has returned to normal.

[Dimento Graven]

Hotthedd, on 29 September 2016 - 02:36 PM, said:

Was something corrected? My ping has returned to normal.

It's getting there.

I'm now back to the pre-fubarage of 80 ping.

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

1 <1 ms <1 ms <1 ms dsldevice.attlocal.net [192.168.1.254]
2 23 ms 23 ms 21 ms 99-7-64-3.lightspeed.rcsntx.sbcglobal.net [99.7.64.3]
3 * * * Request timed out.
4 25 ms 22 ms 23 ms 12.83.80.225
5 25 ms 26 ms 27 ms gar26.dlstx.ip.att.net [12.123.16.109]
6 * * * Request timed out.
7 * * * Request timed out.
8 77 ms 74 ms 72 ms be100-104.nwk-1-a9.nj.us [192.99.146.253]
9 162 ms 166 ms 165 ms be10-1037.bhs-g1-a9.qc.ca [192.99.146.99]
10 86 ms 88 ms 90 ms vl21.bhs-g1-a75.qc.ca [198.27.73.63]
11 82 ms 90 ms 84 ms bhs-g5-a9.qc.ca [178.32.135.194]
12 83 ms 81 ms 77 ms 192.99.109.143

Trace complete.

Still have one slow router on BHS's side, but it is a definitive improvement.

BUT IT COULD BE BETTER!

I want a 40 ping!