356 replies to this topic

[Luca M Pryde]

EasyPickings, on 24 February 2016 - 03:45 PM, said:

These numbers can be misleading. The response at each hop is sent back to you on a lower priority basis than the actual traffic. In other words, when you're sending regular traffic (MWO connects) to the OC server it is done at regular priority. Most routers set their priorities to pass traffic first and foremost, but assign lower priorities to "service" requests like ping and traceroute. If you look at the overall ping time it reflects the whole route, but you'll occasionally see individual nodes send their response much later than the round trip takes.

In your case, you've got 3 responses for the entire route timed at 341 ms 345 ms 333 ms respectively, but node number 14 (and others) takes longer to respond to your request than the entire route: 348 ms 409 ms 346 ms.

Each node is giving its response time to your request, but isn't necessarily assigning the same priority to it as regular traffic.

Keep this in mind when trying to discover where the bottleneck lies.

MWO also reports the same bad ping. I just used tracert to see if there was some weird path issues and I discovered that there are more IP addressed being hit in Singapore than what there used to be.

i.e the problem is in Singapore, not the route taken this time. Or I could be wrong.

[Fannyflasher]

Hiya,

Come back to MWO after a fairly long hiatus, been playing on Oceanic with a ping of 40ms constantly. (Connected from Hong Kong).

Today ping is 500+, cannot find a discernible reason why. Have copypasted the tracert here.
It does look like there is a huge delay between me and my local exchange, but the delay to Sing is abnormally high too. Is this a problem on my end or the SG servers?

Ping for US/Europe remains the same. This must be an issue from SG?
1 <1 ms <1 ms <1 ms
2 1 ms 1 ms 2 ms
3 2 ms 1 ms 1 ms
4 10 ms 11 ms 10 ms 014199255029.ctinets.com [14.199.255.29]
5 164 ms 8 ms 6 ms 014136129014.ctinets.com [14.136.129.14]
6 284 ms 285 ms 283 ms 4657.hkg.equinix.com [119.27.63.54]
7 282 ms 283 ms 291 ms 203.118.15.233
8 318 ms 326 ms 322 ms an-ats-int11.starhub.net.sg [203.118.15.114]
9 310 ms 311 ms 321 ms sh2.nc1.sg.vodien.com [203.116.246.34]
10 515 ms 503 ms 501 ms 85.201.100.101.in-addr.arpa [101.100.201.85]

Edit: Ran multiple tests to several oceanic servers on different games. This is the only one giving me 500ms +. After much testing, involving different ISP providers in HK, and using different SG servers, such as the DotA servers, it seems the problem lies with the HK-SG connection. Specifically in my case, the jumps always occur when hitting an equinix data centre. On different providers it seems to be when it hits the starhub data centre. Any clarification if there is any fix that I can perform on my side, will this be a PGI issue? Or am I stuck waiting for the data centres to fix their issues?

Edit2: So there's two issues here, one is the Hong Kong datacentre as seen in the 6th hop. The second is PGI's Singapore servers; hop 10. 200ms to connect from the Singapore datacentre to the game server is utterly ridiculous...

Edit3: New traceroute, server issues on my side have been fixed:
1 <1 ms <1 ms <1 ms
2 2 ms 1 ms 2 ms
3 2 ms 2 ms 7 ms
4 10 ms 10 ms 11 ms 014199255029.ctinets.com [14.199.255.29]
5 2 ms 1 ms 2 ms 014136129158.ctinets.com [14.136.129.158]
6 3 ms 3 ms 3 ms ix-5-2-5-567.thar1.HK2-Hong-Kong.as6453.net [116.0.67.165]
7 38 ms 38 ms 42 ms if-3-2.tcore2.SVW-Singapore.as6453.net [180.87.163.26]
8 35 ms 35 ms 36 ms if-20-2.tcore1.SVQ-Singapore.as6453.net [180.87.96.21]
9 213 ms 216 ms 217 ms 180.87.96.2
10 185 ms 185 ms 191 ms 73.168.22.103.in-addr.arpa [103.22.168.73]
11 184 ms 184 ms 189 ms tl1.tl1.sg.vodien.com [103.22.168.154]
12 230 ms 220 ms 220 ms r1.eqx1.sg.vodien.com [103.245.92.6]
13 216 ms 217 ms 212 ms r1.nc1.sg.vodien.com [103.245.92.18]
14 222 ms 216 ms 218 ms 85.201.100.101.in-addr.arpa [101.100.201.85]

Still insane packet loss at Singapore server.

Edit 4: Day 3 of ridiculous ping and I've found the issue, please clarify if this is a PGI issue or SG routing issue:

180.87.96.2 - This server is in India... So I'm getting sent to Sing, rerouted out to India, the routed back to Sing before I connect to the game server... Why???
Edit 5: Routing is worse than I thought, the server 103.22.168.73 is in Indonesia, so my route looks like this:

HK (6 nodes) --> SG (2 nodes) --> India --> Indonesia --> SG (3 nodes) --> MWO server (101.100.201.85)

If I can get clarification, I can take steps to rectify the issue if the problem is my ISP, if not it would be nice to know if it's PGI's issue so I can find a work around such as a tunneling program.

Edited by sfurui, 01 March 2016 - 10:41 PM.

[MechWarrior4023212]

I find it completely crap that ping from Brisbane to Oceania server is about the same as to EU and US...clearly this needs to be fixed

[jjm1]

I hope someone at PGI is looking at these.

packet loss on final hop (tons of rubber banding in game). STILL not routing efficiently.

|------------------------------------------------------------------------------------------|
|									  WinMTR statistics								   |
|					   Host			  -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|					   dsldevice.gateway -    0 |  100 |  100 |    0 |    0 |    1 |    0 |
|				   No response from host -  100 |   20 |    0 |    0 |    0 |    0 |    0 |
|						 xxx -    0 |  100 |  100 |   18 |   20 |   26 |   18 |
|bundle-ether7.wel-core3.perth.telstra.net -    0 |  100 |  100 |   18 |   21 |   28 |   21 |
|tengige0-8-0-5-1.pie-core1.perth.telstra.net -    0 |  100 |  100 |   17 |   21 |   27 |   22 |
|tengige0-5-1-0.pthp-core01.perth.net.reach.com -    0 |  100 |  100 |   18 |   22 |   27 |   20 |
|i-0-5-4-0.skdi-core01.bx.telstraglobal.net -    0 |  100 |  100 |   66 |   70 |   78 |   71 |
|   i-0-3-0-0.6ntp02.bi.telstraglobal.net -    0 |  100 |  100 |   68 |   73 |  105 |   79 |
|						   203.116.5.157 -    0 |  100 |  100 |   68 |   71 |  101 |   69 |
|						  203.118.15.186 -    0 |  100 |  100 |   68 |   71 |   77 |   69 |
|			 an-ats-int11.starhub.net.sg -    0 |  100 |  100 |   67 |   68 |   78 |   69 |
|				   sh2.nc1.sg.vodien.com -    0 |  100 |  100 |   67 |   70 |   81 |   67 |
|			 86.201.100.101.in-addr.arpa -   10 |   72 |   65 |  165 |  173 |  187 |  167 |
|________________________________________________|______|______|______|______|______|______|

[Appogee]

I've had three days of 92 ping to Oceanic. A moment ago it went back to 234.

Can anyone tell me the IP address of the Oceanic server? I want to talk to my ISP about whatever it is they are doing with their routing.

[SQW]

Oceanic is still f*cked. Been weeks since I was forced to play only NA server.

Right now Oceanic is as bad as EU for Australia (at 350+ pin). Was 200 before this 'issue'.

[jjm1]

<div>I have done some experiments, considering the failing playability status of the game for us in Australia. Some people might be interested.</div>
<div> </div>
<div>These are with Tel$tra out of Perth using PIA VPN to try and get alternate routes.</div>
<div> </div>
<div>Without VPN: </div>
<div> </div>
<div>same as usual. Playable, but far from where it should be at.</div>
<div> </div>
<div>

<br />
|------------------------------------------------------------------------------------------|<br />
|                                      WinMTR statistics                                   |<br />
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |<br />
|------------------------------------------------|------|------|------|------|------|------|<br />
|                       dsldevice.gateway -    0 |   67 |   67 |    0 |    0 |    1 |    0 |<br />
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |<br />
|                         xxx    -    0 |   67 |   67 |   18 |   20 |   30 |   20 |<br />
|bundle-ether7.wel-core3.perth.telstra.net -    0 |   67 |   67 |   20 |   24 |   31 |   22 |<br />
|tengige0-8-0-5-1.pie-core1.perth.telstra.net -    0 |   67 |   67 |   18 |   22 |   31 |   22 |<br />
|                              203.50.9.2 -    0 |   67 |   67 |   17 |   20 |   25 |   20 |<br />
|i-0-5-4-0.skdi-core01.bx.telstraglobal.net -    8 |   52 |   48 |   69 |   71 |   82 |   69 |<br />
|   i-0-3-0-0.6ntp02.bi.telstraglobal.net -    4 |   60 |   58 |   69 |   72 |   87 |   71 |<br />
|                           203.116.5.157 -    2 |   64 |   63 |   67 |   70 |   80 |   69 |<br />
|                          203.118.15.186 -    0 |   67 |   67 |   68 |   70 |   86 |   68 |<br />
|             an-ats-int11.starhub.net.sg -    2 |   64 |   63 |   66 |   69 |   80 |   69 |<br />
|                   sh2.nc1.sg.vodien.com -    0 |   67 |   67 |   68 |   70 |   79 |   71 |<br />
|             86.201.100.101.in-addr.arpa -    0 |   67 |   67 |  143 |  152 |  164 |  151 |<br />
|________________________________________________|______|______|______|______|______|______|<br />

</div>
<div> </div>
<div> </div>
<div>With VPN connected to Singapore</div>
<div> </div>
<div>way better, but real word results are different.</div>
<div> </div>
<div>

<br />
|------------------------------------------------------------------------------------------|<br />
|                                      WinMTR statistics                                   |<br />
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |<br />
|------------------------------------------------|------|------|------|------|------|------|<br />
|                              10.109.1.1 -    0 |   66 |   66 |   69 |   71 |   79 |   72 |<br />
|    42.7c.5177.ip4.static.sl-reverse.com -    0 |   66 |   66 |   70 |   76 |   85 |   74 |<br />
|    96.76.85ae.ip4.static.sl-reverse.com -    0 |   66 |   66 |   69 |   77 |   92 |   74 |<br />
|   ae9.bbr01.eq01.sng02.networklayer.com -    2 |   63 |   62 |   68 |   74 |   88 |   70 |<br />
|            1g.eq01.sng02.starhub.com.sg -    4 |   59 |   57 |   70 |   81 |  161 |   72 |<br />
|             an-uts-int13.starhub.net.sg -    0 |   66 |   66 |   73 |   78 |   90 |   74 |<br />
|                          203.118.15.229 -    6 |   55 |   52 |   72 |   75 |   87 |   74 |<br />
|             an-ats-int11.starhub.net.sg -    6 |   56 |   53 |   73 |   79 |   92 |   76 |<br />
|                   sh2.nc1.sg.vodien.com -    2 |   63 |   62 |   73 |   78 |   91 |   73 |<br />
|             86.201.100.101.in-addr.arpa -    4 |   59 |   57 |   71 |   77 |   91 |   73 |<br />
|________________________________________________|______|______|______|______|______|______|<br />

</div>
<div> </div>
<div> </div>
<div>In-game pings with VPN connected to Singapore. Two Oceanic matches played back to back. One was awesome, one was horrible. So yet another dice roll as to whether you can enjoy a match or not.</div>
<div> </div>
<div><img alt="" src="http://s9.postimg.org/tjlo60nz3/image.jpg" /></div>
<div> </div>
<div> </div>
<div><img alt="" src="http://s14.postimg.org/ljh5r5ovl/image.jpg" /></div>
<div> </div>
<div>Anyone have any idea as to how the ping can be so inconsistent to the same server, it must be circling the globe twice. And I don't think its anything my end or what I can do to fix it.</div>
<div> </div>
<div>---</div>
<div> </div>
<div>Also some North America tests. because I noticed it has an unplayable ping now as well. Routing to Miami? really.</div>
<div> </div>
<div>without VPN:</div>
<div> </div>
<div>

<br />
|------------------------------------------------------------------------------------------|<br />
|                                      WinMTR statistics                                   |<br />
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |<br />
|------------------------------------------------|------|------|------|------|------|------|<br />
|                       dsldevice.gateway -    0 |   66 |   66 |    0 |    0 |    1 |    0 |<br />
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |<br />
|                         xxx -    0 |   66 |   66 |   17 |   20 |   40 |   20 |<br />
|bundle-ether7.wel-core3.perth.telstra.net -    0 |   66 |   66 |   18 |   21 |   28 |   22 |<br />
|bundle-ether7.fli-core1.adelaide.telstra.net -    0 |   66 |   66 |   48 |   57 |   63 |   57 |<br />
|bundle-ether9.win-core10.melbourne.telstra.net -    0 |   66 |   66 |   58 |   64 |   72 |   61 |<br />
|bundle-ether12.ken-core10.sydney.telstra.net -    0 |   66 |   66 |   68 |   77 |   92 |   69 |<br />
|bundle-ether1.pad-gw11.sydney.telstra.net -    0 |   66 |   66 |   69 |   73 |   80 |   77 |<br />
|bundle-ether1.sydp-core04.sydney.reach.com -    0 |   66 |   66 |   67 |   74 |   85 |   67 |<br />
|i-0-3-0-5.paix-core01.bx.telstraglobal.net -    0 |   66 |   66 |  205 |  210 |  223 |  211 |<br />
|   i-0-5-0-1.paix02.bi.telstraglobal.net -    0 |   66 |   66 |  204 |  211 |  233 |  211 |<br />
|      xe-5-3-0.paloalto2.pao.seabone.net -    0 |   66 |   66 |  205 |  213 |  261 |  209 |<br />
|        et-4-3-0.miami15.mia.seabone.net -    0 |   66 |   66 |  293 |  301 |  326 |  294 |<br />
|        et-4-3-0.miami15.mia.seabone.net -    0 |   66 |   66 |  293 |  301 |  317 |  302 |<br />
|                 po99-155.mia-5-6k.fl.us -   77 |   17 |    4 |  489 |  494 |  504 |  490 |<br />
|               be100-1036.nwk-1-a9.nj.us -    0 |   66 |   66 |  470 |  474 |  496 |  475 |<br />
|               be10-1037.bhs-g1-a9.qc.ca -    2 |   63 |   62 |  468 |  472 |  490 |  469 |<br />
|                         bhs-g5-a9.qc.ca -    2 |   63 |   62 |  473 |  479 |  505 |  474 |<br />
|                          192.99.109.129 -    0 |   66 |   66 |  474 |  478 |  496 |  476 |<br />
|________________________________________________|______|______|______|______|______|______|<br />

</div>
<div> </div>
<div>with VPN connected to Toronto:</div>
<div> </div>
<div>This one at least seems the most stable of the lot so far and its probably at the furthest point on the globe from me. Irony noted.</div>
<div> </div>
<div>

<br />
|------------------------------------------------------------------------------------------|<br />
|                                      WinMTR statistics                                   |<br />
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |<br />
|------------------------------------------------|------|------|------|------|------|------|<br />
|                              10.183.1.1 -    0 |   68 |   68 |  276 |  279 |  290 |  280 |<br />
|                             172.98.67.1 -    0 |   68 |   68 |  277 |  282 |  291 |  279 |<br />
|      ovh.ip4.torontointernetxchange.net -    0 |   68 |   68 |  277 |  309 |  480 |  280 |<br />
|               be10-1214.bhs-g1-a9.qc.ca -    0 |   68 |   68 |  284 |  288 |  297 |  285 |<br />
|                         bhs-g5-a9.qc.ca -    0 |   68 |   68 |  285 |  288 |  298 |  287 |<br />
|                          192.99.109.129 -    0 |   68 |   68 |  284 |  287 |  296 |  288 |<br />
|________________________________________________|______|______|______|______|______|______|<br />

</div>


...and the forum code broke.

not fixing. totally over it.

[IronMate]

Hi there
This is compare of Telstra and Optus rauting passes from Melbourne to oceanic server in Singapore.
Trecing taken from same place and computer in Melbourne.


Tracing route to 86.201.100.101.in-addr.arpa [101.100.201.86]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 75 ms 30 ms 29 ms Bundle-Ether12.lon-edge901.melbourne.telstra.net [XX.XX.XX.XX]
6 65 ms 35 ms 31 ms bundle-ether10.exi-core10.melbourne.telstra.net [XX.XX.XX.XX]
7 76 ms 49 ms 38 ms bundle-ether5.way-core4.adelaide.telstra.net [203.50.11.92]
8 108 ms 75 ms 76 ms bundle-ether5.pie-core1.perth.telstra.net [203.50.11.17]
9 81 ms 68 ms 70 ms gigabitethernet0-7-0-0.pthp-core01.perth.net.reach.com [203.50.13.246]
10 157 ms 111 ms 119 ms i-0-0-1-0.skdi-core01.bx.telstraglobal.net [202.84.143.2]
11 156 ms 127 ms 119 ms i-0-3-0-0.6ntp02.bi.telstraglobal.net [202.84.243.82]
12 127 ms 125 ms 111 ms 203.116.5.157
13 148 ms 119 ms 127 ms 203.118.15.181
14 128 ms 128 ms 109 ms an-ats-int11.starhub.net.sg [203.118.15.114]
15 145 ms 130 ms 110 ms sh2.nc1.sg.vodien.com [203.116.246.34]
16 123 ms 117 ms 111 ms 86.201.100.101.in-addr.arpa [101.100.201.86]

Trace complete.

C:\Users\Jacek>tracert 101.100.201.86

Tracing route to 86.201.100.101.in-addr.arpa [101.100.201.86]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 23 ms 22 ms 22 ms meb2.bng.optusnet.com.au [xx.xx.xx.xx]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 35 ms 34 ms 34 ms 198.142.250.205
7 36 ms 35 ms 36 ms 198.142.139.114
8 36 ms 35 ms 36 ms 198.142.139.130
9 191 ms 189 ms 190 ms 203.208.190.193
10 381 ms 380 ms 380 ms 203.208.183.45
11 386 ms 385 ms 364 ms 203.208.166.58
12 370 ms 370 ms 370 ms 203.208.152.2
13 361 ms 362 ms 364 ms 203.208.190.38
14 363 ms 364 ms 364 ms 203.208.152.2
15 372 ms 372 ms 372 ms 203.208.190.38
16 365 ms 364 ms 365 ms 29.168.22.103.in-addr.arpa [103.22.168.29]
17 369 ms 369 ms 368 ms tl1.tl1.sg.vodien.com [103.22.168.154]
18 * * * Request timed out.
19 381 ms 382 ms 381 ms r1.nc1.sg.vodien.com [103.245.92.18]
20 366 ms 383 ms 369 ms 86.201.100.101.in-addr.arpa [101.100.201.86]

Trace complete.

[IronMate]

So, Optus routing STINKS. I can notice difference in performance between connections. With Optus high pings my aim is sluggish and some of the kills are assign to other players. With Telstra performer is sharper and game bit more enjoable.

[SlothfulArchangel]

So because i'm with Optus, I'm forced to play on NA servers. How is it possible connecting all the way to Canada is faster then connecting to Singapore by 100ms

[SQW]

Cthulhu mk, on 09 March 2016 - 09:12 PM, said:

So because i'm with Optus, I'm forced to play on NA servers. How is it possible connecting all the way to Canada is faster then connecting to Singapore by 100ms

SG was good at 150pin when I started MWO last dec. It's just been the last months or so that even EU is beating my Oceanic server by 20pins. Good thing NA has enough population to ensure a quick game all the time.

I wonder what changed in the past 30-40 days.

[A Corpse]

Last night for the first time I saw 150 ping to Oceanic. Still 250-280 to EU and NA. Something has improved somewhere.

That's on fibre in NZ.

[Oderint dum Metuant]

A Corpse, on 10 March 2016 - 04:21 PM, said:

Last night for the first time I saw 150 ping to Oceanic. Still 250-280 to EU and NA. Something has improved somewhere.

That's on fibre in NZ.

Wasn't the severed underwater cable due to be fixed around now?

[Blerome Jake]

Greetings MechWarriors,

We are aware of the Oceanic server issues. Please bear with us while we investigate. While we investigate the issue Oceanic Servers will be offline.

Thank you for your patience and understanding.

I wasn't aware of a server issue (other than great ping then **** ping again (or as a beta tester i can affirm normal server behaviour)), and this post does not acknowledge any "issue" so it would help me "Bear with you" if you gave a little more info than "LOL Oceania is down, Deal with it".

I'm sure they know what is going on and have a reason to ruin a saturday night during an event, But at the same time this lack of information on the issue/reason is annoying as all hell.

[A Corpse]

Whatever the current issue is, it's causing it to route MUCH BETTER than what the previous status was. Can we keep it like this? It's cut 100ms off my ping to Oceanic.

[A Corpse]

Welp, one evening of decent ping but it's back to ~280. :/

[Alardus]

I've lost connection to the entire service. I've gotten into lobbies at the vote screen only to see "lobby has been destroyed" after being returned to mechlab, and I don't think its based on Oceanic having issues. There seems to be a more severe game-wide issue.

its happening slightly less today, but the last 4 days have been chronic disconnects before match, or midmatch, etc.

[SQW]

Alardus, on 13 March 2016 - 09:11 PM, said:

I've lost connection to the entire service. I've gotten into lobbies at the vote screen only to see "lobby has been destroyed" after being returned to mechlab, and I don't think its based on Oceanic having issues. There seems to be a more severe game-wide issue.

its happening slightly less today, but the last 4 days have been chronic disconnects before match, or midmatch, etc.

On the homepage, PGI has been warning people for the last several days they are looking into the Oceanic server and maintenance will interfere with connection. Just use the other servers for now and hop back in after PGI give the all-clear for Oceanic.

Edited by SQW, 14 March 2016 - 07:32 PM.

[Jungle Rhino]

Right - so the Oeanic server just took a massive poop and as far as I can tell my whole match got canned - couldn't rejoin at all - even better - I then got flagged with a TK 5s penalty for an 'early disconnect' - lol awesome!

[Shwinboy]

4 games in a row tonight on oceanic the game has disconnected, I've been killed before i can rejoin and get hit with a TK penalty. I'll start with a 196 ping then as soon as an enemy mech appears the game lag chokes. It's pretty crap and unplayable at the moment. Just played on the NA server and the same disconnect mid game. Seriously what has happened that the game is so unstable now?

Edited by Shwinboy, 18 March 2016 - 01:10 AM.