Oceanic Server Connection Discussion
#121
Posted 17 September 2015 - 11:07 PM
#122
Posted 21 September 2015 - 05:27 AM
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.
Can't complain, I'd say I haven't had this kind of problem. Initially after Oceanic servers launch had problems disconnecting from the match to the mechlab screen and being unable to reconnect, but since that problem was fixed I haven't got a single disconnect in more than a month. And never got kicked back to the login screen.
#123
Posted 25 September 2015 - 06:48 AM
Edited by l33tworks, 25 September 2015 - 06:48 AM.
#124
Posted 28 September 2015 - 03:54 PM
#125
Posted 29 September 2015 - 08:20 PM
#126
Posted 30 September 2015 - 11:37 PM
I'm on Optus.
Melbourne.
#127
Posted 01 October 2015 - 05:06 PM
Such an epic fail.
#128
Posted 03 October 2015 - 11:10 PM
applor, on 01 October 2015 - 05:06 PM, said:
Fixed.
Because they're all starved of Mechwarrior, Living Legends was curbstomped in favor of this tripe, and assuming PGI is any more competent after the departure of IGP is wishful thinking.
Edited by RedThirteen, 03 October 2015 - 11:11 PM.
#130
Posted 07 October 2015 - 04:19 AM
Location: Cebu, Philippines
Was getting around 60-70+ ping initially then it jumped straight to 200+ in just a week
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| ******************* - 0 | 34 | 34 | 0 | 0 | 1 | 0 |
| ************************* - 0 | 34 | 34 | 29 | 38 | 168 | 29 |
| ************************* - 4 | 31 | 30 | 28 | 29 | 37 | 29 |
| 210.213.130.178.static.pldt.net - 0 | 34 | 34 | 41 | 48 | 173 | 41 |
| 122.2.175.50.static.pldt.net - 0 | 34 | 34 | 41 | 49 | 191 | 41 |
| 210.213.131.81.static.pldt.net - 7 | 30 | 28 | 252 | 257 | 338 | 252 |
| 210.14.2.190 - 88 | 8 | 1 | 0 | 296 | 296 | 296 |
| w118012045.w118012.starhub.net.sg - 8 | 27 | 25 | 255 | 259 | 266 | 255 |
| 203.118.2.29 - 8 | 28 | 26 | 255 | 260 | 340 | 256 |
| an-ats-int11.starhub.net.sg - 4 | 31 | 30 | 284 | 290 | 344 | 285 |
| sh2.nc1.sg.vodien.com - 4 | 31 | 30 | 252 | 258 | 275 | 254 |
| 86.201.100.101.in-addr.arpa - 8 | 27 | 25 | 252 | 259 | 341 | 254 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
#131
Posted 07 October 2015 - 05:00 AM
Was previously getting a ping of 126 before the cable cut issue, now getting the same as a NA server connection. Seems to be the Sydney - HK (?) hop....
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| ***************** - 0 | 61 | 61 | 0 | 0 | 7 | 0 |
| ***************** - 0 | 61 | 61 | 30 | 34 | 46 | 35 |
| ***************** - 0 | 61 | 61 | 30 | 37 | 52 | 41 |
|bundle-ether4.lon-edge901.melbourne.telstra.net - 0 | 61 | 61 | 30 | 39 | 54 | 31 |
|bundle-ether10.exi-core10.melbourne.telstra.net - 0 | 61 | 61 | 30 | 35 | 57 | 33 |
|bundle-ether5.way-core4.adelaide.telstra.net - 0 | 61 | 61 | 46 | 57 | 74 | 48 |
|bundle-ether5.pie-core1.perth.telstra.net - 0 | 61 | 61 | 75 | 82 | 103 | 79 |
|tengige0-8-0-5-1.wel-core3.perth.telstra.net - 0 | 61 | 61 | 79 | 91 | 123 | 96 |
|tengige0-7-0-0.pthw-core01.perth.net.reach.com - 0 | 61 | 61 | 76 | 87 | 101 | 92 |
|i-0-1-0-5.sydp-core03.bx.telstraglobal.net - 0 | 61 | 61 | 91 | 103 | 113 | 104 |
|i-0-1-0-0.hkhh-core02.bx.telstraglobal.net - 0 | 61 | 61 | 208 | 220 | 231 | 223 |
| i-0-4-0-18.hkhh11.bi.telstraglobal.net - 0 | 61 | 61 | 216 | 224 | 251 | 222 |
| ge9-9.br01.hkg05.pccwbtn.net - 0 | 61 | 61 | 204 | 222 | 356 | 220 |
| TenGigE0-5-0-1.cr04.hkg05.pccwbtn.net - 0 | 61 | 61 | 262 | 278 | 305 | 266 |
| TenGE0-4-0-2.cr03.sin02.pccwbtn.net - 0 | 61 | 61 | 286 | 296 | 310 | 287 |
| 73.168.22.103.in-addr.arpa - 0 | 61 | 61 | 285 | 298 | 319 | 291 |
| tl1.tl1.sg.vodien.com - 0 | 61 | 61 | 259 | 273 | 305 | 275 |
| No response from host - 100 | 12 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 12 | 0 | 0 | 0 | 0 | 0 |
| 86.201.100.101.in-addr.arpa - 0 | 61 | 61 | 241 | 248 | 272 | 251 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
#132
Posted 07 October 2015 - 03:18 PM
tried something different that seemed to work still checking it out but i added one of Star Hubs (Singapore ISP) DNS servers to my router and seems my ping went down again to the 70s
if you want to try them out i'll place it here
202.156.1.38
202.156.1.48
202.156.1.58
202.156.1.68
202.156.1.78
218.186.1.38
218.186.1.68
218.186.1.88
Edited by scp, 07 October 2015 - 03:19 PM.
#133
Posted 07 October 2015 - 04:31 PM
scp, on 07 October 2015 - 03:18 PM, said:
tried something different that seemed to work still checking it out but i added one of Star Hubs (Singapore ISP) DNS servers to my router and seems my ping went down again to the 70s
Fyi,
There are very few cases that changing dns would help ping and that involves CDNs.
MWO's game server IP should not be dynamic in nature and changing of DNS server, should not help.
Edited by ShinVector, 07 October 2015 - 05:37 PM.
#134
Posted 07 October 2015 - 06:48 PM
ShinVector, on 07 October 2015 - 04:31 PM, said:
Fyi,
There are very few cases that changing dns would help ping and that involves CDNs.
MWO's game server IP should not be dynamic in nature and changing of DNS server, should not help.
Yes i understand its not a 100% fix or it wouldnt fix anything at all but some might find it useful so i just placed it here
Edited by scp, 07 October 2015 - 06:48 PM.
#135
Posted 07 October 2015 - 07:20 PM
scp, on 07 October 2015 - 06:48 PM, said:
Yes i understand its not a 100% fix or it wouldnt fix anything at all but some might find it useful so i just placed it here
I just trying to understand the logic in the suggestion. LOL.
To me:
Either your ISP resolved your latency in the background as you were changing the DNS.
Or
You are not pinging the correct IP address for PGIs game server.
This can be verified by switching back to the 'old dns' and see whether latency problem comes back.
Am a network engineer myself.. So the suggestion was making go... Ehhhhh...
#136
Posted 08 October 2015 - 01:34 PM
It kind of defeats the whole purpose of having OC regional servers if their performance is worse than what they were to replace (NA server connections).
C:Users****>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 * * * Request timed out.
2 20 ms 34 ms 19 ms 218.101.61.29
3 20 ms 18 ms 21 ms ie2-g-0-0-0.telstraclear.net [203.98.50.2]
4 18 ms 18 ms 18 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251]
5 19 ms 21 ms 19 ms unknown.telstraglobal.net [134.159.174.41]
6 145 ms 143 ms 144 ms i-0-5-1-1.1wlt-core01.bx.telstraglobal.net [202.84.142.114]
7 144 ms 146 ms 146 ms i-0-4-0-4.1wlt-core01.bi.telstraglobal.net [202.40.149.221]
8 227 ms 231 ms 229 ms i-0-1-0-4.siko-core04.bx.telstraglobal.net [202.84.143.162]
9 227 ms 227 ms 227 ms i-0-0-0-7.siko11.bi.telstraglobal.net [202.84.148.234]
10 227 ms 224 ms 226 ms pccwg-peer.siko11.pr.telstraglobal.net [134.159.98.46]
11 248 ms 248 ms 247 ms TenGE8-5.br02.sin02.pccwbtn.net [63.218.228.154]
12 248 ms 248 ms 248 ms TenGE8-5.br02.sin02.pccwbtn.net [63.218.228.154]
13 248 ms 248 ms 247 ms 63-218-213-182.static.pccwglobal.net [63.218.213.182]
14 248 ms 248 ms 248 ms 73.168.22.103.in-addr.arpa [103.22.168.73]
15 256 ms 248 ms 248 ms tl1.tl1.sg.vodien.com [103.22.168.154]
16 249 ms 250 ms 250 ms r1.eqx1.sg.vodien.com [103.245.92.6]
17 248 ms 248 ms 249 ms r1.nc1.sg.vodien.com [103.245.92.18]
18 251 ms 248 ms 250 ms 86.201.100.101.in-addr.arpa [101.100.201.86]
Trace complete.
Hops 6 through 9 are all located in Hong Kong (Telstra Global Internet Services). The slow downs all seem to be when routing through Telstra's networks.
Edited by EasyPickings, 08 October 2015 - 01:43 PM.
#137
Posted 12 October 2015 - 02:55 PM
Usual ping to Oceanic 125 now 250ish
Usual ping to NA 260-270 now 350-450
This has been since the last patch.
I was having issues with my internet connection but after replacing the line filter that has cleared up and now I have this issue. I pinged a few other Montreal ISP's through speedtest.net and got good download speeds and my usual NA ping of around 270. Still not sure if it is my ISP or something to do with the MWO servers.
Location Adelaide: South Australia
Edited by slide, 12 October 2015 - 02:56 PM.
#138
Posted 12 October 2015 - 03:23 PM
slide, on 12 October 2015 - 02:55 PM, said:
I'm just seeing an increase in OC server pings. The NA servers have actually gone down slightly - used to be around 260 and are now around 230. Location: Wellington, NZ
Edited by EasyPickings, 12 October 2015 - 03:24 PM.
#139
Posted 12 October 2015 - 06:33 PM
the routes to the servers have been an issue for years for Australasian players ..... and by putting the server outside of our region, it remains hard to convince anyone to spend money on it ....
current route, from Queensland on Telstra, goes
Brisbane - Telstra
Sydney - Telstra
Melbourne - Telstra
Adelaide - Telstra
Perth - Telstra
Perth - Reach
Sydney - Telstra
Hong Kong - Telstra
with the last two being where most of the latency comes in .... they will ALWAYS do this stuff to save few cents, that's what Telstra is known for ..... I know someone probably gave assurances it would be great .... but, that person was selling you something .....
#140
Posted 13 October 2015 - 05:40 PM
RD BAIT UTi, on 12 October 2015 - 06:33 PM, said:
the routes to the servers have been an issue for years for Australasian players ..... and by putting the server outside of our region, it remains hard to convince anyone to spend money on it ....
current route, from Queensland on Telstra, goes
Brisbane - Telstra
Sydney - Telstra
Melbourne - Telstra
Adelaide - Telstra
Perth - Telstra
Perth - Reach
Sydney - Telstra
Hong Kong - Telstra
with the last two being where most of the latency comes in .... they will ALWAYS do this stuff to save few cents, that's what Telstra is known for ..... I know someone probably gave assurances it would be great .... but, that person was selling you something .....
5 user(s) are reading this topic
0 members, 5 guests, 0 anonymous users