332 replies to this topic

[Naduk]

Alymbic, on 10 September 2014 - 12:17 AM, said:

Question on that point Russ. There are those of us in Australia who are currently finding the game more or less unplayable since you moved the game servers which left our ISP routing to rediciously high pings. Can we expect a return of the premium time we currently have ticking seeing as this current issue is far from being in the players control?

its not a fault of PGI , while it would be nice of them to return lost premium or what have you they are under zero obligation to do so, the fact they are putting pressure on giants like Telstra for us is more than anyone should ask of them

call your provider and let them know of the issue, send tracert logs as proof
in most cases it has been auto-resolving but thats clearly a luck of the draw approach

[Alymbic]

Naduk, on 10 September 2014 - 12:48 AM, said:

its not a fault of PGI , while it would be nice of them to return lost premium or what have you they are under zero obligation to do so, the fact they are putting pressure on giants like Telstra for us is more than anyone should ask of them

call your provider and let them know of the issue, send tracert logs as proof
in most cases it has been auto-resolving but thats clearly a luck of the draw approach

The attempt has already been made, but telstra support has been less than helpful for me. Has anyone successfully called Telstra and gotten them to do anything?

[Primetimex]

GREAT WORK PGI, ping went from 271ms before patch 3 weeks ago and whatever you did in that time screwed it up to 380+ms:

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

C:\Users\primetime>tracert www.mwomercs.com

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

1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 14 ms 13 ms 13 ms Lo0.amnet.l1-45sgt-se800-01.wa.amnet.net.au [203
.161.65.253]
3 14 ms 13 ms 13 ms vl70.ten7-3.cr01.wa.amnet.net.au [203.161.65.41]

4 14 ms 13 ms 13 ms te3-2.br02.wa.amcom.net.au [203.161.65.65]
5 98 ms 96 ms 94 ms mail-o.mcms.com.au [61.88.8.41]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 148 ms 153 ms 152 ms 59.154.142.236
10 296 ms 307 ms 302 ms 203.208.190.17
11 302 ms 304 ms 304 ms 203.208.172.238
12 * * * Request timed out.
13 302 ms 296 ms * snj-2-6k.ca.us [178.32.135.168]
14 312 ms * * lax-1-6k.ca.us [178.32.135.161]
15 * * * Request timed out.
16 916 ms 930 ms 934 ms bhs-g2-6k.qc.ca [198.27.73.207]
17 368 ms 377 ms 380 ms 198.27.73.233
18 388 ms 378 ms 380 ms mwomercs.com [192.99.109.192]

Trace complete.

C:\Users\primetime>tracert www.mwomercs.com>results.txt

Just for giggles I tried firing up another game MMO: 199ms - 203ms ping!

Edited by GetterRobo, 10 September 2014 - 03:52 AM.

[FatYak]

Russ, the desync issue and rubber banding is absolutely out of control mat the moment. of 8 matches tonight, 4 of them i was killed in because of desync and the other all had heavy rubber banding and terrible hit registration, its not worth playing

the game feels like its dying

[IraqiWalker]

GetterRobo, on 10 September 2014 - 03:48 AM, said:

GREAT WORK PGI, ping went from 271ms before patch 3 weeks ago and whatever you did in that time screwed it up to 380+ms:

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

C:\Users\primetime>tracert www.mwomercs.com

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

1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 14 ms 13 ms 13 ms Lo0.amnet.l1-45sgt-se800-01.wa.amnet.net.au [203
.161.65.253]
3 14 ms 13 ms 13 ms vl70.ten7-3.cr01.wa.amnet.net.au [203.161.65.41]

4 14 ms 13 ms 13 ms te3-2.br02.wa.amcom.net.au [203.161.65.65]
5 98 ms 96 ms 94 ms mail-o.mcms.com.au [61.88.8.41]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 148 ms 153 ms 152 ms 59.154.142.236
10 296 ms 307 ms 302 ms 203.208.190.17
11 302 ms 304 ms 304 ms 203.208.172.238
12 * * * Request timed out.
13 302 ms 296 ms * snj-2-6k.ca.us [178.32.135.168]
14 312 ms * * lax-1-6k.ca.us [178.32.135.161]
15 * * * Request timed out.
16 916 ms 930 ms 934 ms bhs-g2-6k.qc.ca [198.27.73.207]
17 368 ms 377 ms 380 ms 198.27.73.233
18 388 ms 378 ms 380 ms mwomercs.com [192.99.109.192]

Trace complete.

C:\Users\primetime>tracert www.mwomercs.com>results.txt

Just for giggles I tried firing up another game MMO: 199ms - 203ms ping!

You know this should be sent to support, and not posted on the forums, right? This absolutely does nothing. Send it to support@mwomercs.com

[Primetimex]

IraqiWalker I have sent it to Support but since Support is Niko, him and himself I don't hold out much hope.

I posted it here since others have done so too earlier.

[IraqiWalker]

Well, good luck getting it fixed. I understand how much it sucks when your ping jumps to such an extent, that the game becomes unplayable.

[Gryphorim]

Adding my name to the headcount. Still stuck on 370ms ping.

[Clit Beastwood]

GetterRobo, on 10 September 2014 - 05:20 AM, said:

IraqiWalker I have sent it to Support but since Support is Niko, him and himself I don't hold out much hope.

I posted it here since others have done so too earlier.

Shoot, I'm an IT guy anyways and worked support for several companies... I wouldn't mind doing after-hours (after my work hours) support a few days a week. I try to help people out in the support forum here, but I generally don't have access to what I need to help them.

[boboking]

YAY! I am happy to report changing my DNS did not work, and neither whatever PGI did on their end. Ping is still coming back at 400ms. Telstra in VIC.

[Primetimex]

My ISP helped me by doing something at the exchange (interleaving?) this reduced the MW:0 ping from 381ms to 331ms but still unplayable.

In my other MMO game though it has reduced ping down to 199ms from around 230-240ms.

PGI, get a proper datacenter so we can get on with playing and why do you keep insisting it's ISP routing when it's clearly your rubbish datacenter??!!

Edited by GetterRobo, 11 September 2014 - 12:49 AM.

[N0MAD]

Alymbic, on 10 September 2014 - 02:33 AM, said:

The attempt has already been made, but telstra support has been less than helpful for me. Has anyone successfully called Telstra and gotten them to do anything?

Ya i called Telstra, altho i wasnt been routed thru EU, they assure me Telstra does not route thru Europe to go to North America.
You only get routed thru EU if the site is being broadcast thru EU (their explanation).
As i couldnt send them Traces because i wasnt been Routed thru EU they couldnt give me any further info.
If you are a Telstra customer and are being routed thru Europe, they suggest you contact them and have traceroutes ready to send. They will trace for you and tell you why its happening, i found them helpful.

[POWR]

Ping from denmark is also improved to closer to 100 than 150.

[N0MAD]

POWR, on 11 September 2014 - 04:35 AM, said:

Ping from denmark is also improved to closer to 100 than 150.

Would love to see a trace from EU players..

[boboking]

An interesting surprise today when I ran tracert!

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

1 <1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 19 ms 21 ms 19 ms 172.18.211.15
3 19 ms 21 ms 19 ms 172.18.67.141
4 19 ms 19 ms 19 ms bundle-ether4.win-edge902.melbourne.telstra.net
[203.50.76.8]
5 22 ms 20 ms 20 ms bundle-ether12.win-core10.melbourne.telstra.net
[203.50.11.111]
6 35 ms 34 ms 34 ms bundle-ether12.ken-core10.sydney.telstra.net [20
3.50.11.122]
7 52 ms 34 ms 35 ms Bundle-ether18.pad-gw2.sydney.telstra.net [203.5
0.13.82]
8 38 ms 36 ms 36 ms bundle-ether1.sydp-core01.sydney.reach.com [203.
50.13.46]
9 173 ms 171 ms 171 ms i-0-3-0-3.paix-core01.bx.telstraglobal.net [202.
84.140.37]
10 170 ms 201 ms 171 ms i-0-4-0-6.paix02.bi.telstraglobal.net [202.40.14
9.58]
11 169 ms 169 ms 169 ms xe-5-3-0.paloalto2.pao.seabone.net [195.22.206.1
29]
12 236 ms 236 ms 236 ms pal-5-6k.ca.us [178.32.135.206]
13 * * * Request timed out.
14 300 ms * 302 ms 198.27.73.175
15 303 ms 302 ms 303 ms bhs-g2-6k.qc.ca [198.27.73.3]
16 303 ms 303 ms 303 ms 198.27.73.233
17 302 ms 301 ms 301 ms mwomercs.com [192.99.109.192][/color]


Trace complete.
Looks like its fixed>?!?!

On Telstra/VIC

Edited by boboking, 11 September 2014 - 10:16 PM.

[Oderint dum Metuant]

N0MAD, on 11 September 2014 - 04:47 AM, said:

Would love to see a trace from EU players..

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

1 <1 ms <1 ms <1 ms SkyRouter.Home [192.168.0.1]
2 * * * Request timed out.
3 10 ms 13 ms 14 ms 02780954.bb.sky.com [2.120.9.84]
4 * * * Request timed out.
5 14 ms 14 ms 14 ms rbx-g1-a9.fr.eu [91.121.215.141]
6 15 ms 14 ms 14 ms 37.187.36.131
7 * * * Request timed out.
8 95 ms 95 ms 94 ms mwomercs.com [192.99.109.192]

Trace complete.

boboking, on 11 September 2014 - 10:15 PM, said:

An interesting surprise today when I ran tracert!

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

1 <1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 19 ms 21 ms 19 ms 172.18.211.15
3 19 ms 21 ms 19 ms 172.18.67.141
4 19 ms 19 ms 19 ms bundle-ether4.win-edge902.melbourne.telstra.net
[203.50.76.8]
5 22 ms 20 ms 20 ms bundle-ether12.win-core10.melbourne.telstra.net
[203.50.11.111]
6 35 ms 34 ms 34 ms bundle-ether12.ken-core10.sydney.telstra.net [20
3.50.11.122]
7 52 ms 34 ms 35 ms Bundle-ether18.pad-gw2.sydney.telstra.net [203.5
0.13.82]
8 38 ms 36 ms 36 ms bundle-ether1.sydp-core01.sydney.reach.com [203.
50.13.46]
9 173 ms 171 ms 171 ms i-0-3-0-3.paix-core01.bx.telstraglobal.net [202.
84.140.37]
10 170 ms 201 ms 171 ms i-0-4-0-6.paix02.bi.telstraglobal.net [202.40.14
9.58]
11 169 ms 169 ms 169 ms xe-5-3-0.paloalto2.pao.seabone.net [195.22.206.1
29]
12 236 ms 236 ms 236 ms pal-5-6k.ca.us [178.32.135.206]
13 * * * Request timed out.
14 300 ms * 302 ms 198.27.73.175
15 303 ms 302 ms 303 ms bhs-g2-6k.qc.ca [198.27.73.3]
16 303 ms 303 ms 303 ms 198.27.73.233
17 302 ms 301 ms 301 ms mwomercs.com [192.99.109.192][/color]


Trace complete.
Looks like its fixed>?!?!

On Telstra/VIC

Think someone else had it fixed for a day or two then it diverted back so keep an eye on it.

[N0MAD]

DV McKenna, on 11 September 2014 - 11:41 PM, said:

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

1 <1 ms <1 ms <1 ms SkyRouter.Home [192.168.0.1]
2 * * * Request timed out.
3 10 ms 13 ms 14 ms 02780954.bb.sky.com [2.120.9.84]
4 * * * Request timed out.
5 14 ms 14 ms 14 ms rbx-g1-a9.fr.eu [91.121.215.141]
6 15 ms 14 ms 14 ms 37.187.36.131
7 * * * Request timed out.
8 95 ms 95 ms 94 ms mwomercs.com [192.99.109.192]

Trace complete.

Thanks, Jump 7 is a mystery (well not really).
5 &6 are some what unusual also, 6 is an OVH ip 37..... but supposedly in Montreal but as they are cloud servers who knows, 1ms from France to Montreal? nice then an 80ms jump in ping for last hop that should be the service(server) that MWO is using.
http://myip.ms/view/...0_37.187.36.255 (looked up info of that 37.187.36 ... on youre trace.
A couple of other EU traces would be interesting.
Very helpful, im pretty sure i got an idea of the situation now.
Interesting to hear that PGI also has the ability to route the game.

[ShinVector]

N0MAD, on 12 September 2014 - 12:51 AM, said:

Thanks, Jump 7 is a mystery (well not really).
5 &6 are some what unusual also, 6 is an OVH ip 37..... but supposedly in Montreal but as they are cloud servers who knows, 1ms from France to Montreal? nice then an 80ms jump in ping for last hop that should be the service(server) that MWO is using.

A small lesson on how the internet works.
How does a web trace program know which country a router/hop is in ?

It doesn't nor the router that in the hop. There is no automatic GPS working here at all.
They are just basing on the IP Whois database that every IP owner is expected to maintain with their respective IR all over the world. Human managed database are often inaccurate.
http://tools.whois.n...p/37.187.36.131

*On another note... That domain name (eg. rbx-g1-a9.fr.eu [91.121.215.141] ) that is you often see resolved on the hops of a simple traceroute on your PC ?
That is using a different mechanism and it is not related to IP whois database.
That is using DNS PTR (pointer record) that allows an IP owner to resolve an IP address to a domain name using DNS. It is convenient and simple way to verify IP address owner ship and provide information regarding an IP address.
Also human managed and can be completely inaccurate.

Edited by ShinVector, 12 September 2014 - 10:06 PM.

[N0MAD]

Thanks for the info, i know a litle about the internet, did several Microsoft certs including Networking, just for personal knowledge nothing pro. Ive owned my own domain for close on 20 years, Run my own server here running an Sql database, i like to dable in web design, just a hobby, but i take to much credit, two of my best friends are long term Nerds, they have worked in IT for 25 years, they do most of the backend stuff and keep my systems up to spec.

[Clobba]

well I am still 380 without the VPN connected and back to only slightly higher than old ping at 250ish with it connected to LA