95 replies to this topic

[Bobby Jubraj]

Hey everyone,

It looks like the issues were being caused by a lack of direct routes between AT&T and OVH's servers, leading to the large spike in reported pings. This was specifically affecting routes from or coming through the Midwest. We've received confirmation from OVH today that these issues should be resolved and we're told that AT&T has established more direct routes for the affected areas.

If you're still encountering connection issues please let us know, we'll continue to look into it. It seems like there are still some folks seeing pings in the 80-90ms region, and while this is an improvement over the previous 120-150ms, those numbers are still a bit higher than we'd expect. For anyone seeing ping in the 80-90ms region or above, please contact AT&T directly to report it, as the issue will most likely reside within their network.

Thanks

[Grrzoot]

wow i hope this works, my steady 59 ping was averaging 120-250 randomly for the last couple weeks, (midwest)

[Wing 0]

Bobby Jubraj, on 04 October 2016 - 03:18 PM, said:

Hey everyone,

It looks like the issues were being caused by a lack of direct routes between AT&T and OVH's servers, leading to the large spike in reported pings. This was specifically affecting routes from or coming through the Midwest. We've received confirmation from OVH today that these issues should be resolved and we're told that AT&T has established more direct routes for the affected areas.

If you're still encountering connection issues please let us know, we'll continue to look into it. It seems like there are still some folks seeing pings in the 80-90ms region, and while this is an improvement over the previous 120-150ms, those numbers are still a bit higher than we'd expect. For anyone seeing ping in the 80-90ms region or above, please contact AT&T directly to report it, as the issue will most likely reside within their network.

Thanks

I was wondering if something was going on with routes and nodes and your post confirmed it 100% for me. Thanks giving letting us know Bobby. There were times where I wouldn't be able to connect to not only the site but also the game's server as well. sometimes I couldn't connect at all period. I will send a report on this issue to AT&T personally. I had this problem with them on this matter before and its clear that this symptom has returned.

Edited by Wing 0, 07 October 2016 - 07:33 PM.

[Davegt27]

whish there was a way to tell before you drop ping and or loss that way
low rates don't effect other players

[ChillAAA]

Not sure if issues are still being reported post early October inside the US but I'm seeing 100% packet loss about 2/3 in to my route from Sydney, Australia to mwomercs.com every single day (I'm with Optus). At this stage the best information I've got from work are the linked pictures of my pingplotter sessions. http://i.imgur.com/uDbs515.png and http://i.imgur.com/pCcwJu7.png

[WANTED]

I saw another post on this issue and was directed here. I have same problem from Ft Worth that definitely is same issue with AT&T when running tracert( routes to europe for no reason when N American MWO server is only set). Went from 60ms to constant 130-140. Chat online was a waste of time. Not sure how to get them to look into this. On phone but will post tracert later from PC.

Edited by WANTED, 04 December 2016 - 07:28 AM.

[ChairBorneRanger]

I started the other thread that WANTED is referencing, here's a link:

https://mwomercs.com...through-europe/

The trace route is in the other thread but it seems to jump the pond at some point for no reason.

*UPDATE *
Ran a trace route this morning with the following results:

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

1 <1 ms <1 ms <1 ms (Home Router)
2 1 ms <1 ms <1 ms (Home Gateway)
3 6 ms 11 ms 9 ms (Local residential head end) [104.189.72.1]
4 3 ms 2 ms 2 ms 99.71.0.174
5 * * * Request timed out.
6 4 ms 3 ms 3 ms 12.83.39.65
7 14 ms 11 ms 11 ms gar26.dlstx.ip.att.net [12.123.16.109]
8 * 1791 ms * 4.68.62.229
9 * * * Request timed out.
10 49 ms 49 ms 49 ms be100-155.nwk-5-a9.nj.us [198.27.73.29]
11 51 ms 50 ms 50 ms be100-2.nwk-1-a9.nj.us [178.32.135.218]
12 65 ms 55 ms 55 ms be10-1037.bhs-g1-a9.qc.ca [192.99.146.99]
13 57 ms 57 ms 56 ms vl21.bhs-g1-a75.qc.ca [198.27.73.63]
14 57 ms 57 ms 56 ms bhs-g5-a9.qc.ca [178.32.135.194]
15 57 ms 57 ms 57 ms 192.99.109.143

Guess someone figured it out ISP side. I'll update again if it does it in the future.

[Dimento Graven]

As of this morning it appears to have been fixed.

I contacted the ATT rep that helped last time and they still had the contact info of whomever it was that was malf'd and apparently got it corrected.

[WANTED]

Yes fixed thanks!

[Ragnahawk]

You deserve a like good sir!

[Burning2nd]

I had a problem earlier this year where my ping was a good 100ms more then normal..

From 30-50 up to 120-150ms I know to some of you that's nothing.. but that's a world of difference..

So it went on for about 5 months... I started to get mad, did some tests, confirmed it wasn't on my end.. and the problem was only to PGI's servers... So i did some investigating and when i had proof to actually approach support with i swear to god.. as soon as i sent the email to them.. It sorted it self out.. like literally... They respond quickly.. and i had to be like... oh sorry nothing wrong.. fixed it self...

weird right?

[OverHeater30]

I to have lately been getting kicked from games and in the Mech lab screens randomly. Both on the North American Servers and European Servers. My ping sits at about 27 here in North America and about 118 on the European servers. This has only recently begun within the last 2 weeks. Before that I had absolutely no problems.

[Splatshot]

Bad routing is happening again from AT&T



Before it went to the West coast and then Europe, now it seems to go to Miami, and then gets stuck for a bit.



tracert www.mwomercs.com

Tracing route to www.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 171 ms 3 ms 9 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 7 ms 3 ms 3 ms 71.150.18.27
5 4 ms 6 ms 3 ms 71.150.32.186
6 4 ms 3 ms 3 ms 12.83.42.153
7 16 ms 15 ms 15 ms gar27.dlstx.ip.att.net [12.123.16.77]
8 13 ms 12 ms 12 ms 192.205.36.42
9 53 ms 55 ms 53 ms et4-3-0.miami15.mia.seabone.net [195.22.199.177]

10 * * * Request timed out.
11 91 ms 90 ms 91 ms be100-1263.chi-1-a9.il.us [178.32.135.5]
12 107 ms 107 ms 107 ms be10-1312.bhs-g1-a9.qc.ca [198.27.73.196]
13 107 ms 106 ms 106 ms vl21.bhs-g1-a75.qc.ca [198.27.73.63]
14 107 ms 107 ms 107 ms bhs-g5-a9.qc.ca [178.32.135.194]
15 107 ms 106 ms 106 ms 192.99.109.143

Trace complete.



105 NA

133 EU

[Ronusan]

Same here. I'm in DFW area of Texas on AT&T and just got fiber 100mbs. Logged in to MWO and pings are still 100-120ms even though I'm getting under 10ms to just about everywhere else. Tracert shows I'm getting bounced from Texas to Italy and France and then finally on to Quebec and MWO.

I really hope this isn't permanent since the main reason I upgraded my internet (and upped my bill) was to finally get low latency for MWO!

The problematic IP addresses I'm seeing in the tracert over and over:
89.221.41.177 (Italy)
178.32.135.5 (France)
178.32.135.194 (France)
195.22.199.179 (Italy)
198.27.73.196 (Quebec, Canada)
198.27.73.63 (Quebec, Canada)

[Grey Ghost]

I pretty much have the same issue as the guy above me. Why AT&T is routing us through Italy I've not a clue.

[Ronusan]

Issue is still ongoing. At about 11pm my ping was hovering around 70ms even though I'm on ATT&T fiber lines now. Then in game lag spiked with mechs freezing in place and then warping, though in game chat was unaffected. The game then kicked me to login screen saying "server connection lost" though I could still hear the chat running from other players in the match! I closed program and found that the webpage was not loading either, though other websites loaded fine. I did an ipconfig dnsflush and the website came back and I was able to get into game again but my ping had then gone back up to 130ms. Tracert shows half of the hops with pings of 130 to 135 and half with pings of single digits. After a few minutes in game it went back down to 70 and THEN it lost server connection again and will not let me back in now!