Oceanic Server Connection Discussion
#101
Posted 24 August 2015 - 04:41 PM
Could we get a confirmation?
#103
Posted 24 August 2015 - 07:01 PM
Xoco, on 22 August 2015 - 03:59 AM, said:
The game often starts with the mech cockpit graphics unloaded, and that will show up a bit later.
Does not sound like a network issue..
#104
Posted 24 August 2015 - 08:43 PM
TPG is not going to do anything about the packets going to Singapore via japan.
Here is the reply i got back from TPG -
"Hi Jon,
I've been advised that the path that the packets take to the destination is normal as that is how our network is configured.
Kind regards,"
#105
Posted 25 August 2015 - 07:26 AM
#106
Posted 26 August 2015 - 11:25 AM
#107
Posted 31 August 2015 - 02:54 AM
ShinVector, on 24 August 2015 - 07:01 PM, said:
Does not sound like a network issue..
I thought so initially--but it does not happen when I join EU or NA server, therefore it is not client side. I'm not even sure why Mech cockpit would even be handled remotely, but I don't know how else to explain it.
#108
Posted 01 September 2015 - 12:23 AM
Thinking Dodo- but they use both optus and telstra networks...sooo Has anyone in Australia on a telstra exchange and Dodo ISP done a trace rout?
Any other suggestions for a good ISP??? Official response from PGI?
Any help appreciated. Cheers- Wibble
PS. Can this thread be cleaned up? (ie remove the DC posts and disgruntled flames so we can more easily browse and compare)
#109
Posted 01 September 2015 - 01:42 AM
I am in Brisbane and have a Telstra land line so I am now routed over the Telstra path to Oceanic.
I don't have the tracert on hand but basically I now go Brissy to Sydney to Melbourne to Adelaide to Perth to Singapore and about 140ms. Used to be 300ish.
Also, latency to NA has gone from 315 to about 260 so its better too.
Good luck
#110
Posted 01 September 2015 - 02:27 AM
I use telstra always have, never ever had a problem, i negotiated what i wanted in Connection ( they do do that), sure i pay close to $80 a month but i get great connects to everywhere (cept MWO i average 300+ to NA, not played other servers) WT i average 220, WoWs unbelievable 130-150 to US servers, My sons get 220ish to NA LOL servers same to GW, Star trek etc.
Now Consider we are a very connected family here, 2 late teen sons, myself and wife (not so much wife, normal non gamer user),there are always 2 or 3 of us connected.
So when deciding on a provider if you use the interwebs for recreation dont stinge out over a few $ a month.
FYI, not saying go Telstra here, altho they serve my purpose well, they may not suit you, but check around.
#111
Posted 02 September 2015 - 04:10 AM
#112
Posted 11 September 2015 - 05:27 PM
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms *Blanked*
2 9 ms 11 ms 10 ms *Blanked*
36.1]
3 6 ms 7 ms 6 ms 103.241.59.197
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 33 ms 31 ms 36 ms ae-3.a04.sydnau03.au.ra.gin.ntt.net [103.13.80.1
25]
10 158 ms 156 ms 155 ms ae-3.r05.sydnau01.au.bb.gin.ntt.net [202.68.64.1
24]
11 202 ms 230 ms 203 ms ae-8.r20.tokyjp05.jp.bb.gin.ntt.net [129.250.3.7
6]
12 194 ms 193 ms 194 ms ae-15.r01.tokyjp01.jp.bb.gin.ntt.net [129.250.4.
91]
13 171 ms 171 ms 171 ms 61.213.145.202
14 171 ms 172 ms 172 ms 203.118.15.186
15 170 ms 171 ms 171 ms an-ats-int11.starhub.net.sg [203.118.15.110]
16 172 ms 171 ms 170 ms sh2.nc1.sg.vodien.com [203.116.246.34]
17 171 ms 171 ms 171 ms 86.201.100.101.in-addr.arpa [101.100.201.86]
Trace complete.
Whakatane, New Zealand. ISP: Trustpower.
Could all those Timeout responses be whats causing my game to randomly kick me back to Login every three or so matches?
#113
Posted 13 September 2015 - 01:56 PM
Thunder Child, on 11 September 2015 - 05:27 PM, said:
No, they're just routers that are either configured to not return pings, or they were too busy dealing with through traffic. If you get a return from further along, the router that didn't reply is sending your data along.
11 202 ms 230 ms 203 ms ae-8.r20.tokyjp05.jp.bb.gin.ntt.net [129.250.3.7
6]
12 194 ms 193 ms 194 ms ae-15.r01.tokyjp01.jp.bb.gin.ntt.net [129.250.4.
91]
The high ping is because your data is being sent to Tokyo before Singapore, which makes it almost twice as far.
#114
Posted 14 September 2015 - 11:49 AM
#115
Posted 15 September 2015 - 02:05 AM
Selbatrim, on 01 September 2015 - 01:42 AM, said:
I am in Brisbane and have a Telstra land line so I am now routed over the Telstra path to Oceanic.
I don't have the tracert on hand but basically I now go Brissy to Sydney to Melbourne to Adelaide to Perth to Singapore and about 140ms. Used to be 300ish.
Also, latency to NA has gone from 315 to about 260 so its better too.
Good luck
Thank you Selbatrim for the feedback! Having seen your success I also churned from TPG to DODO. I am located in Chiltern VIC on a Telstra exchange. My Ping to the oceanic server is less than half what it used to be (now I am getting 120 as opposed to 350ish) and US has gone from 315 to 260 as well. I am now a much happier Mechduck
#116
Posted 15 September 2015 - 03:45 AM
2 3 ms 9 ms 5 ms *hidden*
3 5 ms 5 ms 4 ms *hidden*
4 5 ms 4 ms 5 ms 33.27.69.111.static.snap.net.nz [111.69.27.33]
5 5 ms 4 ms 4 ms ae5-2.akbr7.global-gateway.net.nz [210.55.202.213]
6 28 ms 31 ms 27 ms xe0-0-1.sgbr3.global-gateway.net.nz [202.50.232.110]
7 28 ms 27 ms 28 ms ae2-10.sgbr4.global-gateway.net.nz [202.50.232.246]
8 27 ms 28 ms 27 ms ae-3.a04.sydnau03.au.ra.gin.ntt.net [103.13.80.125]
9 28 ms 28 ms 29 ms ae-3.r05.sydnau01.au.bb.gin.ntt.net [202.68.64.124]
10 142 ms 141 ms 142 ms ae-8.r20.tokyjp05.jp.bb.gin.ntt.net [129.250.3.76]
11 142 ms 141 ms 141 ms ae-15.r01.tokyjp01.jp.bb.gin.ntt.net [129.250.4.91]
12 207 ms 233 ms 206 ms 61.213.145.202
13 208 ms 207 ms 207 ms 203.118.15.181
14 208 ms 207 ms 208 ms an-ats-int11.starhub.net.sg [203.118.15.114]
15 206 ms 206 ms 206 ms sh2.nc1.sg.vodien.com [203.116.246.34]
16 206 ms 206 ms 206 ms 86.201.100.101.in-addr.arpa [101.100.201.86]
New Zealand, Auckland, ISP Snap!
Does not look good to me.
My current connectivity to MWO servers:
NA 386ms
EU 406ms
OC 206ms
In last couple of weeks ping to NA increased from just under 200ms to ~400ms. NA servers connection was the best around 180ms but now it is pretty much unplayable...
Has anyone noticed any changes recently?
#117
Posted 17 September 2015 - 06:06 PM
I want to see if it's a New Zealand thing, my connection, or my computer. I'll be installing MWO on my work computer in the weekend, and testing it on the company line on Monday, so hopefully that might eliminate two possibilities.
Edited by Thunder Child, 17 September 2015 - 06:08 PM.
#118
Posted 17 September 2015 - 06:22 PM
Thunder Child, on 17 September 2015 - 06:06 PM, said:
I want to see if it's a New Zealand thing, my connection, or my computer. I'll be installing MWO on my work computer in the weekend, and testing it on the company line on Monday, so hopefully that might eliminate two possibilities.
Uuuhhh... You realise that you do not actually need to install MWO right ?
Ping and traceroute (or winMTR) is pretty sufficient for troubleshooting routing problems.
#119
Posted 17 September 2015 - 07:37 PM
I've done the Traceroute and Ping, and sent the results to PGI Tech Support. What I am attempting to do now is isolate IF my computer or network are somehow at fault. Easiest way to do that, is to try MWO on my work computer on the home network. If it still DCs, then I can try it on the Work network. If it still DCs, it's a problem between here and there. If it doesn't, then maybe upgrading to 100/50 MBPS Fibre wasn't worth it after all.
#120
Posted 17 September 2015 - 07:46 PM
Thunder Child, on 17 September 2015 - 07:37 PM, said:
I've done the Traceroute and Ping, and sent the results to PGI Tech Support. What I am attempting to do now is isolate IF my computer or network are somehow at fault. Easiest way to do that, is to try MWO on my work computer on the home network. If it still DCs, then I can try it on the Work network. If it still DCs, it's a problem between here and there. If it doesn't, then maybe upgrading to 100/50 MBPS Fibre wasn't worth it after all.
Hmmmm... I would suggest running winMTR in the background to monitor the trends.
Take first screenshot for the base line... (Sometimes you might start to see loss already if there is issue.)
Play the game.... wait for a DC..
And immediately check winMTR... Should show sudden increase in packet loss or high latency if it was network issue.
Should also give you a good idea where the problem is.
Edited by ShinVector, 18 September 2015 - 12:33 AM.
15 user(s) are reading this topic
0 members, 15 guests, 0 anonymous users