Highlighted
Level 3: Gumshoe

High Latency/Bad Routing to Singapore (Again)

Hello everyone,

 

For a while now I've been playing a game that is based outside of Australia. Because of that, I use GPN/VPN/VPS's to route my data through singapore and to the game server, giving me better latency.
EDIT: I am from Perth
Recently, my latency to multiple different Singapore based servers/data centers would fluctuate randomly. It will be a low 50ms for a week or two, then up between 120-300 for a few days. The increase and decrease of my latency to multiple singapore servers would be random - some days I would have low ping to certain servers and high to the others, and some days I would have low ping to the servers I previously had high ping to, same applying to the servers I recently had low ping to. Some days, I will have extremely high latency to ALL Singapore servers. 

This becomes frustrating as the time I get to play these games is already very limited, and being unable or unwilling to play due to such high latency makes it much, much more aggravating. 

Would it be possible to fix my peering/routing/path to Singapore? At the moment I'm planning to buy a VPS and host an OpenVPN server on it for gaming. If possible, I'd like to have the best routing to the servers used by IndoVirtue.com. The IP address of their Singapore Server is: 116.251.223.250

Here's my traceroute at this current time: 

 

C:\Users\Ryan>tracert 116.251.223.250

Tracing route to singapore-lg.indovirtue.com [116.251.223.250]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms T-GATEWAY [10.0.0.138]
2 4 ms 4 ms 4 ms 172.18.216.100
3 4 ms 4 ms 5 ms 172.18.73.133
4 3 ms 4 ms 4 ms bundle-ether4.wel-edge901.perth.telstra.net [203
.50.112.50]
5 7 ms 7 ms 3 ms bundle-ether6.wel-core3.perth.telstra.net [203.5
0.6.214]
6 36 ms 39 ms 39 ms bundle-ether7.fli-core1.adelaide.telstra.net [20
3.50.11.18]
7 46 ms 46 ms 46 ms bundle-ether9.win-core10.melbourne.telstra.net [
203.50.11.91]
8 59 ms 59 ms 61 ms bundle-ether12.ken-core10.sydney.telstra.net [20
3.50.11.122]
9 60 ms 62 ms 60 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
10 60 ms 60 ms 61 ms bundle-ether1.sydp-core04.sydney.reach.com [203.50.13.90]
11 242 ms 243 ms 239 ms i-0-1-0-2.tlot-core01.bx.telstraglobal.net [202.84.140.50]
12 237 ms 238 ms 238 ms i-0-5-0-2.eqla01.bi.telstraglobal.net [202.84.253.10]
13 238 ms 237 ms 238 ms unknown.telstraglobal.net [134.159.63.171]
14 239 ms 238 ms 238 ms if-6-20.tcore2.LVW-Los-Angeles.as6453.net [64.86.252.65]
15 236 ms 235 ms 235 ms if-2-2.tcore1.LVW-Los-Angeles.as6453.net [66.110.59.1]
16 238 ms 238 ms 238 ms 63.243.197.2
17 255 ms 279 ms 249 ms core-1.v3.lax1.sg.gs [124.6.40.21]
18 305 ms 376 ms 296 ms core-1.v54.hk1.sg.gs [103.14.244.102]
19 305 ms 304 ms 319 ms core-1.v52.sg3.sg.gs [103.14.244.98]
20 307 ms 400 ms 369 ms core-1.v31.sg1.sg.gs [203.175.175.128]
21 298 ms 299 ms 307 ms core-2.v3.sg1.sg.gs [203.175.175.38]
22 294 ms 292 ms 292 ms 116.251.222.32
23 293 ms 292 ms 301 ms singapore-lg.indovirtue.com [116.251.223.250]

Trace complete.

 

Thanks, Ryan.

Was this helpful?

  • Yes it was, thank you
  • No, I still need help
9 REPLIES 9
Highlighted
Level 24: Supreme Being
Level 24: Supreme Being

Re: High Latency/Bad Routing to Singapore (Again)

There's issues with the undersea cables to singapore atm. Not sure on repair timeframe

I am Complex Customer Service Specialist, nominally working with most assurance products. However, I am not an official representative on CrowdSupport.

IT Helpdesk and Technicial Support by Telstra Platinum
Smart Home Automation & Monitoring from Telstra
Helping Australians Find the Things that Matter Most with Telstra Locator
Highlighted
Level 3: Gumshoe

Re: High Latency/Bad Routing to Singapore (Again)

Ah, I see I see. That makes sense. How come the "issues" with the undersea cables occur every couple of days? And last a couple of days? It seems to affect random cables, assuming each cable leads to an individual server in Singapore. Why aren't we able to use the same undersea cable as say, iiNet? All my mates on there have no issues ever with their connection to Singapore.
Highlighted
Level 24: Supreme Being
Level 24: Supreme Being

Re: High Latency/Bad Routing to Singapore (Again)

An actual cable repair can take several weeks and even months to fix. Any extra failures then cause a snowball effect and traffic then has to be routed around the problems. Telstra wholesale is essentially Telstra retails sole service provider
I am Complex Customer Service Specialist, nominally working with most assurance products. However, I am not an official representative on CrowdSupport.

IT Helpdesk and Technicial Support by Telstra Platinum
Smart Home Automation & Monitoring from Telstra
Helping Australians Find the Things that Matter Most with Telstra Locator
Highlighted
Level 3: Gumshoe

Re: High Latency/Bad Routing to Singapore (Again)

That still doesn't explain why it's so random. If it can take several weeks and months to fix, how come my originally low latency route is now back to low latency after 3 days? Once again I have lower latencies to certain SG servers and higher to others. It seems to change every 2-3 days. If the cable is undergoing repair and traffic has to be routed around the problems, how much only some routes get routed and it changes around every couple of days? This doesn't seem to make any sense :/
Highlighted
Level 3: Gumshoe

Re: High Latency/Bad Routing to Singapore (Again)

* BUMP * 

Would really like to see if Telstra could fix my peering/routing to this Singapore Server/Address : 116.251.223.250

It's hosted by IndoVirtue. All my other friends on iiNet have perfect 50ms latency to it. 

Please do try and get the route :c

Traceroute: 

C:\Users\Ryan>tracert 116.251.223.250

Tracing route to singapore-lg.indovirtue.com [116.251.223.250] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dsldevice.gateway [10.0.0.138]
2 18 ms 17 ms 14 ms 172.18.216.100
3 3 ms 4 ms 4 ms 172.18.73.133
4 4 ms 4 ms 5 ms bundle-ether4.wel-edge901.perth.telstra.net [203.50.112.50]
5 9 ms 7 ms 8 ms bundle-ether6.wel-core3.perth.telstra.net [203.50.6.214]
6 39 ms 40 ms 39 ms bundle-ether7.fli-core1.adelaide.telstra.net [203.50.11.18]
7 48 ms 48 ms 46 ms bundle-ether9.win-core10.melbourne.telstra.net [203.50.11.91]
8 60 ms 59 ms 59 ms bundle-ether12.ken-core10.sydney.telstra.net [203.50.11.122]
9 58 ms 60 ms 56 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
10 58 ms 60 ms 58 ms bundle-ether1.sydp-core04.sydney.reach.com [203.50.13.90]
11 213 ms 214 ms 208 ms i-0-1-0-1.tlot-core01.bx.telstraglobal.net [202.84.140.74]
12 208 ms 206 ms 207 ms i-0-5-0-0.eqla01.bi.telstraglobal.net [202.84.253.2]
13 206 ms 206 ms 213 ms unknown.telstraglobal.net [134.159.63.171]
14 206 ms 206 ms 206 ms if-6-20.tcore2.LVW-Los-Angeles.as6453.net [64.86.252.65]
15 208 ms 204 ms 206 ms if-2-2.tcore1.LVW-Los-Angeles.as6453.net [66.110.59.1]
16 201 ms 200 ms 201 ms 63.243.197.2
17 217 ms 331 ms 208 ms core-1.v3.lax1.sg.gs [124.6.40.21]
18 246 ms 322 ms 246 ms core-1.v54.hk1.sg.gs [103.14.244.102]
19 371 ms 231 ms 235 ms core-1.v52.sg3.sg.gs [103.14.244.98]
20 239 ms 435 ms 284 ms core-1.v31.sg1.sg.gs [203.175.175.128]
21 227 ms 218 ms 218 ms core-2.v3.sg1.sg.gs [203.175.175.38]
22 228 ms 218 ms 221 ms 116.251.222.32
23 216 ms 219 ms 218 ms singapore-lg.indovirtue.com [116.251.223.250]

Trace complete.

Highlighted
Telstra (Retired)
Telstra (Retired)

Re: High Latency/Bad Routing to Singapore (Again)

Hi, 

 

There are currently a number of submarine cables that have been damaged. Routing around these damaged cables are the likely cause of the higher than normal and fluctuating ping results that you are seeing.
 
Ben

Need help? Check out our Community Wiki or Support Portal || Looking for a new mobile? Order online today || Get help with any Tech at Home with Telstra Platinum || Don't forget to tag answers as Accepted Solutions and give a Like to the member(s) who helped you out.

All moderation actions are supported by the CrowdSupport Community Guidelines

Highlighted
Level 1: Cadet

Re: High Latency/Bad Routing to Singapore (Again)

 Hi,

 

Is this still the issue at this date?

I am getting some routing issues to singapore on the NBN. 

 

Thanks

Highlighted
Telstra (Retired)
Telstra (Retired)

Re: High Latency/Bad Routing to Singapore (Again)

Can you provide a traceroute and advise the state that you are connecting from?

 

- Shelly

Need help? Check out our Community Wiki or Support Portal || Looking for a new mobile? Order online today || Get help with any Tech at Home with Telstra Platinum || Don't forget to tag answers as Accepted Solutions and give a Like to the member(s) who helped you out.

All moderation actions are supported by the CrowdSupport Community Guidelines

Highlighted
Level 1: Cadet

Re: High Latency/Bad Routing to Singapore (Again)

 

I'm having the same problem after connecting to Telstra NBN from Sydney.

 

Before converting to the NBN, I was getting 100-150ms pings.  Now it is 250ms+

 

 

Tracing route to login.worldoftanks.asia [92.223.16.65]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.138
2 * * * Request timed out.
3 13 ms 9 ms 8 ms 144.130.208.210
4 9 ms 8 ms 9 ms bundle-ether2.chw-edge902.sydney.telstra.net [203.50.11.105]
5 10 ms 10 ms 10 ms bundle-ether14.chw-core10.sydney.telstra.net [203.50.11.100]
6 24 ms 24 ms 22 ms bundle-ether8.exi-core10.melbourne.telstra.net [203.50.11.125]
7 53 ms 49 ms 42 ms bundle-ether5.way-core4.adelaide.telstra.net [203.50.11.92]
8 64 ms 68 ms 64 ms bundle-ether5.pie-core1.perth.telstra.net [203.50.11.17]
9 64 ms 63 ms 93 ms tengige0-0-1-0.pthp-core01.perth.net.reach.com [203.50.13.250]
10 56 ms 55 ms 57 ms i-0-1-0-27.sydo-core03.bi.telstraglobal.net [202.84.143.45]
11 171 ms 170 ms 170 ms i-0-5-2-0.hkth-core01.bx.telstraglobal.net [202.84.143.22]
12 204 ms 207 ms 207 ms i-0-2-0-8.skdi-core01.bx.telstraglobal.net [202.84.137.34]
13 201 ms 205 ms 202 ms unknown.telstraglobal.net [202.84.224.194]
14 255 ms 258 ms 259 ms i-0-0-2-2.istt03.bi.telstraglobal.net [202.84.219.182]
15 232 ms 226 ms 230 ms unknown.telstraglobal.net [202.127.73.118]
16 257 ms 255 ms 255 ms sg2-n5596-fe-1-vl231.fe.core.pw [92.223.116.163]
17 265 ms 255 ms 255 ms sg2-sl-a65.fe.core.pw [92.223.16.65]

Trace complete.

 

 

On a friend's Optus connection to the same server, I'm getting 150ms ping.

 

Set it & forget it

With direct debit there’s no need to give paying your bill another thought.

Avoid queuing up and never worry about late fees again.

Setup direct debit