56 replies to this topic

[Wski]

Telstra, they seemed to reset the servers today to no effect what so ever and it is only MWO that is effected, there are some great mechs coming out in the near future but the game is becoming unplayable at a decent lvl with these pings above 200, this should nopt be that hard.

Edited by Wski, 27 November 2016 - 08:43 PM.

[Jay Z]

Telstra, North Queensland.

[jjm1]

Telstra Perth.

Oceanic: 244 ms
NA : 273 ms

To get a visual on how fubar this is:
Distance to Singapore: 4000km
Distance to Toronto: 18400km

what annoys me the most is that the SEAMEWE-3 cable direct from Perth to Singapore is right there and the traffic should be flowing on that, instead Telstra and/or Singapore ISPs are either to dumb to route anything efficiently or are cheapskates and are forcing data along the cheapest crappiest route they can get away with. PGI should just get a server in Sydney already.

[Wski]

It is sad that nobody from MWO has commented or let us know they are looking into this issue, the Aussie community may only be small, but it will never increase with no service from the game provider. this is in direct contrast to when i by something at which point i get assistance straight away..........ummm they seem to be very money focused rather then having a more complete customer focus.

[General Solo]

I think it could be about peering issues between carriers

[Liveish]

Wski, on 28 November 2016 - 11:17 PM, said:

It is sad that nobody from MWO has commented or let us know they are looking into this issue, the Aussie community may only be small, but it will never increase with no service from the game provider. this is in direct contrast to when i by something at which point i get assistance straight away..........ummm they seem to be very money focused rather then having a more complete customer focus.

Its more the ISP you use and the location (cheap place) that PGI placed the server.

jjm1, on 28 November 2016 - 08:02 PM, said:

Telstra Perth.

Oceanic: 244 ms
NA : 273 ms

To get a visual on how fubar this is:
Distance to Singapore: 4000km
Distance to Toronto: 18400km

what annoys me the most is that the SEAMEWE-3 cable direct from Perth to Singapore is right there and the traffic should be flowing on that, instead Telstra and/or Singapore ISPs are either to dumb to route anything efficiently or are cheapskates and are forcing data along the cheapest crappiest route they can get away with. PGI should just get a server in Sydney already.

For the game point of view, both pings are playable, HSR is great.

Apart from Comp and maybe solo group the Asian server is a waste of time

[Wski]

True but most of the time as an Aussie in Aussie play time solo group is all i get, and i can tell you straight a ping of 100 make a big difference to play style and the things you can do, as opposed to a ping of 250+. the reason the complaints are happening now is that pre patch the pings were 120ish for me now that have more then doubled for no explained reason. you also need to have good look at most of the top tier players, they are not running 250+ ping. All of this aside it still doesn't excuse the poor communication we receive with issues like this, it is my favorite MMO, but it has the worst communication in regards to problems and issues of all of them, it is the Ostrich guide to solving problems with customers - Hide you face till they go away. then we all lose out because there are less of us supporting the game.

[Liveish]

Mate PGI can not help that telstra is no longer sending your traffic in a good way, the only people having problems are those on telstra and optus ( Optus has always been bad)

the ping is fine, most of us play on NA, AP and EU servers with pings up to 400 and still do everything we can if we had a ping under 100.

HSR is the best thing PGI has done.

There is bitching about PGI when they stuff up and blaming them for things that is not there fault. ( this time its the ISP fault)

When you logged a ticket what did they say ? What has changed in your traceroute ?
Have you asked your ISP what the high ping for ?

[Wski]

So you say it is not their fault...Do you work for them or are you a representative from them, and as such you are privy to the real information and reason as to why my ping changed after the patch was downloaded. and are using this forum to respond poorly......or are you a player trolling other players with your speculations that have little or no basis in fact other then you own opinion......i have ticketed this and received no response which is why I went to the forums to see if I was alone or there were others, and it seems a lot of us have the same issue that started at the same time from different ISPs.....wow that is a big coincidence. So maybe you do not have the answer and only half backed ideas, if you are not here to be helpful, just leave the post alone, and if you are an Australian player who did not receive a ping increase please let us know, if this does not concern you just stay away. PGI are big boys they can answer for themselves they don't need your help.

[Liveish]

So post your trace route then >? ( IF YOU ARE UNSURE HOW TO DO THIS ASK)

FYI - If you have not worked out the forums are not the place to get an answer by PGI, but the player base.

Apart from IBorg users the rest have been telstra and the traceroute show its a Telstra problem not PGI.

FYI out of the 10 people i play with from Aust, only the 2 people that use Telstra/Optus backbone has been affected.

Edited by live1991, 03 December 2016 - 12:13 AM.

[Daidachi]

Live ain't no shill, trust me - he'll call PGI out when he thinks they're being naff as much as anyone (just look at the stuff he posted during the tournament where he pointedly asked questions on why their servers were so unstable).

But he's right - if the problem is with your ISP, being as they're a totally separate company to them there ain't exactly much they can do to help.

If you're looking for help from the playerbase, post a traceroute, because that'll help identify where your traffic is being routed through, and how long it's taking to get to the server itself.

But if you're looking for someone from pgi to blame for this, you're barking up the wrong tree.

[cleghorn6]

Has anyone else on Telstra just lost their route to AP servers? I'm pinging over 300 at the moment, higher than US.

[jjm1]

cleghorn6, on 12 December 2016 - 06:02 AM, said:

Has anyone else on Telstra just lost their route to AP servers? I'm pinging over 300 at the moment, higher than US.

Turned off Oceanic weeks ago because of degrading ping. Getting 322 from Perth at the moment so yes, its even more munted than usual.

[General Solo]

I had similar problems a while back when I was with Telstra.

I recommend posting on Telstra's Crowd Support Website
Add the link to this page to said post

A little bad publicity goes a long way

There are the links I used to get things fixxed to give you an idea

http://mwomercs.com/...ts-need-advice/

https://crowdsupport...-p/380209#M3356

[jjm1]

OZHomerOZ, on 12 December 2016 - 05:25 PM, said:

I had similar problems a while back when I was with Telstra.

I recommend posting on Telstra's Crowd Support Website
Add the link to this page to said post

A little bad publicity goes a long way

There are the links I used to get things fixxed to give you an idea

http://mwomercs.com/...ts-need-advice/

https://crowdsupport...-p/380209#M3356

If bad publicity worked on Telstra it would had shriveled up like a **** under the spotlight decades ago.

[cleghorn6]

Just for reference, the SMW3 cable repair was completed yesterday, so PER/SNG traffic is no longer being routed through HK.

For me on Telstra cable, my ping is now lower to OC servers than NA for the first time in months. Hopefully when Telstra gets their act together it will drop down again to something reasonable.

[justcallme A S H]

Mine is still going via HK for Telstra


7 23 ms 23 ms 25 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
8 27 ms 25 ms 25 ms bundle-ether1.sydp-core04.sydney.reach.com [203.50.13.90]
9 202 ms 202 ms 201 ms i-52.tlot-core02.bx.telstraglobal.net [202.84.137.101]
10 164 ms 166 ms 167 ms i-0-0-0-7.eqla01.bi.telstraglobal.net [202.40.149.230]
11 180 ms 177 ms 181 ms tisparkle-peer.eqla01.pr.telstraglobal.net [134.159.61.26]
12 244 ms 245 ms 244 ms te0-1-0-0.hongkong1.hok.seabone.net [195.22.206.165]
13 242 ms 240 ms 239 ms starhub.hongkong1.hok.seabone.net [195.22.223.145]
14 241 ms 243 ms 242 ms 203.118.15.181
15 246 ms 239 ms 242 ms 203.118.2.30
16 241 ms 242 ms 242 ms an-atl-int11.starhub.net.sg [203.118.15.86]
17 240 ms 242 ms 242 ms 203.116.7.78
18 * * * Request timed out.
19 242 ms 242 ms 242 ms 86.201.100.101.in-addr.arpa [101.100.201.86]

Trace complete.

My ping is actually better to the US ATM

[cleghorn6]

That's interesting, I hadn't run a trace, I just assumed that because I'd dropped about 60ms from my ping time that the routing had been fixed. Possibly the ping has dropped because of reduced load on the HK link as all the other ISPs who actually give a **** about their customers switch back over.

I've been pinging 260-270 to US pretty solid. I had been 120 or so to OC until December, then it shot up to just over 300. Currently sitting at about 240 or so. From Perth.

Will do some science tonight.

[justcallme A S H]

Yeah Telstra probably just haven't moved it back yet perhaps?

I don't know enough about that side of the IT works. That said to the Core01 vs Core02 (from my post the other page) there is a 100ms jump there alone.

Perhaps still issues internally to Telstra.

[cleghorn6]

Wow. This was so ... I had to run it 3 times.

5 17 ms 19 ms 17 ms bundle-ether6.wel-core3.perth.telstra.net [203.50.6.214]
6 45 ms 41 ms 44 ms bundle-ether7.fli-core1.adelaide.telstra.net [203.50.11.18]
7 50 ms 50 ms 55 ms bundle-ether9.win-core10.melbourne.telstra.net [203.50.11.91]
8 65 ms 95 ms 99 ms bundle-ether12.ken-core10.sydney.telstra.net [203.50.11.122]
9 102 ms 100 ms 102 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
10 111 ms 100 ms 63 ms bundle-ether1.sydp-core04.sydney.reach.com [203.50.13.90]
11 313 ms 303 ms 303 ms i-52.tlot-core02.bx.telstraglobal.net [202.84.137.101]
12 216 ms 305 ms 298 ms i-0-5-0-1.eqla01.bi.telstraglobal.net [202.84.253.6]
13 318 ms 220 ms 285 ms tisparkle-peer.eqla01.pr.telstraglobal.net [134.159.61.26]
14 320 ms 378 ms 407 ms te0-0-2-0.hongkong1.hok.seabone.net [195.22.223.164]
15 309 ms 303 ms 261 ms starhub.hongkong1.hok.seabone.net [195.22.223.145]
16 320 ms 304 ms 303 ms 203.118.15.186
17 311 ms 305 ms 304 ms 203.118.2.26
18 306 ms 304 ms 304 ms an-atl-int11.starhub.net.sg [203.118.15.82]
19 312 ms 251 ms 256 ms 203.116.7.78
20 * * * Request timed out.
21 244 ms 242 ms 294 ms 86.201.100.101.in-addr.arpa [101.100.201.86]


So no. Telstra haven't fixed their routing.