5 replies to this topic

[Splatshot]

Anyone else use AT&T U-verse, and had their ping increase lately?

Basically I get 134 to the NA server and 132 to the Euro server.

I live in Kansas.

Edited by Splatshot, 21 September 2016 - 07:29 PM.

[Deathlike]

Tell AT&T to upgrade their tincans?

The best solution I would suggest is file a support request through DSLReports in the appropriate forum for them to look into it.

Sometimes it's congestion, but sometimes you can be connected in an overloaded stack.

Although my quick search/look into the thing suggests that section is on hiatus for whatever reason.

[dervishx5]

[Splatshot]

On AT&T's forums I found other MWO users in Texas complaining about it, has something to do with routing to OHV server clusters.

Edited by Splatshot, 21 September 2016 - 09:27 PM.

[CheeseThief]

Routing antics are things than happen, so send PGI a support ticket about it so they can get someone on AT&T's case about it.


When PGI changed data center a while ago Telstra Australia had the best route. Instead of going from Sydney to Hawaii to mainland USA then too the data center, Telstra instead thought it more efficient to route from Sydney through Indonesia, to China, to somewhere in the middle east, to North Africa, to mainland Europe, to London, to Canada, and then to the USA data center for an increase of 300~ ping. Chances are good that AT&T have done something similar.

[Splatshot]

The AT&T had a MWO Player that already did that provingit was AT&T.

AT&T is fighting with OHV about whose issue it really is...basically there are three unknown hits in the trace route that time out and the our traffic gets sent to OHV in europe who then route it correctly back to the NA after about 4 bounces.
[color=#333333]
C:\Users\notme>tracert mwomercs.com[/color]
[color=#333333]
Tracing route to mwomercs.com [192.99.109.143]
over a maximum of 30 hops:[/color]
[color=#333333]
1 <1 ms <1 ms <1 ms 192.168.1.254
2 21 ms 21 ms 21 ms 99-7-64-3.lightspeed.rcsntx.sbcglobal.net [99.7.64.3]
3 * * * Request timed out.
4 25 ms 26 ms 26 ms 12.83.80.225
5 24 ms 27 ms 27 ms gar27.dlstx.ip.att.net [12.123.16.77]
6 24 ms 26 ms 27 ms 192.205.36.94
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 160 ms 192 ms 199 ms be100-110.fra-1-a9.de.eu [37.187.232.46]
11 208 ms 210 ms 206 ms be1-1170.sbg-g1-a9.fr.eu [37.187.232.86]
12 206 ms 211 ms 205 ms vl21.sbg-g1-a75.fr.eu [213.186.32.251]
13 209 ms 204 ms 208 ms sbg-g5-a9.fr.eu [37.187.36.186]
14 215 ms 217 ms 222 ms mad-3-4m.es.eu [91.121.215.215]
15 167 ms 200 ms 204 ms 192.99.109.143[/color]
[color=#333333]
Trace complete.[/color]
[color=#333333]
[/color]
[color=#333333]
[/color]
[color=#333333]
"I've received a response from the company (PGI) that owns the server in question, they ran a reverse tracert from their server to my IP, and they didn't get routed to the EU. I've asked for them to forward me the tracert results so that we'll have that information available, however, again, traffic from the Canadian OVH hosting facility is making it out just fine."[/color]

Edited by Splatshot, 21 September 2016 - 09:45 PM.