Highlighted
Level 2: Rookie

Problem with Perth to Singapore Routing

Hey guys,

 

I've noticed recently that the Perth to Singapore routing for telstra global seems to be quite bad, and giving on the order of 140 ping, rather than the 60 ping it used to give. Can anyone else from Perth confirm this?

 

It is really inconvenient, as a lot of games (overwatch, world of tanks, pubg, fortnite, CS:GO) have servers that service Perth from Singapore.

Was this helpful?

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

Re: Problem with Perth to Singapore Routing

Not seeing anything service impacting (nice change) along the smw3 cable

 

Can you post a traceroute?

I am a 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 2: Rookie

Re: Problem with Perth to Singapore Routing

I couldn't complete your request earlier because the cable got severed. Now the cable is back online the tracert is as below to the overwatch server in singapore from perth. There is definitely weirdness after it lands in singapore at level3-peer.istt04.pr.telstraglobal.net [202.126.129.65].

 

 

3 8 ms 8 ms 8 ms Bundle-Ether17.wel-edge901.perth.telstra.net [110.145.136.161]
4 8 ms 8 ms 8 ms bundle-ether2.pie-edge901.perth.telstra.net [203.50.6.185]
5 8 ms 11 ms 11 ms bundle-ether6.pie-core1.perth.telstra.net [203.50.6.212]
6 10 ms 9 ms 10 ms bundle-ether19.pie-core10.perth.telstra.net [203.50.11.236]
7 9 ms 11 ms 11 ms tengige0-5-1-0.pthp-core01.perth.net.reach.com [203.50.13.254]
8 56 ms 57 ms 57 ms 202.84.140.38
9 69 ms 56 ms 58 ms i-93.istt04.telstraglobal.net [202.84.224.190]
10 57 ms 57 ms 56 ms level3-peer.istt04.pr.telstraglobal.net [202.126.129.65]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 130 ms 130 ms 130 ms 203.83.223.31

 

 

Oddly the valve half life-2 server doesnt seem to have these weird arrangements with routing

 

  3    20 ms    19 ms    19 ms  Bundle-Ether17.wel-edge901.perth.telstra.net [110.145.136.161]
4 21 ms 19 ms 20 ms bundle-ether6.wel-core3.perth.telstra.net [203.50.6.214]
5 22 ms 18 ms 19 ms tengige0-6-0-0.pthw-core01.perth.net.reach.com [203.50.13.234]
6 69 ms 69 ms 67 ms 202.84.140.18
7 67 ms 68 ms 68 ms i-91.istt04.telstraglobal.net [202.84.224.197]
8 70 ms 67 ms 68 ms unknown.telstraglobal.net [210.176.138.193]
9 69 ms 67 ms 67 ms sgp-2.valve.net [103.10.124.1]

 

 

From contacting blizzard:

 


Greetings, ! Tech Specialist Warturtin here. Thanks for taking the time to follow up. I don't actually know of any reverse trace we can run from AWS. I did a bit of digging to see if I could figure this out, though. Best I can tell, the route between you and our AWS server location appears to be travelling up to Hong Kong before being routed back down to Singapore. Naming isn't always 100% accurate on these but this is what I'm looking at: | level3-peer.hkmi01.pr.telstraglobal.net - 0 | 644 | 644 | 55 | 56 | 69 | 56 | After that we sadly can't see anything, other than one of the final nodes showing an average of 132ms. I know one of the main cables between Perth and Singapore went down earlier in September (SMW3). It should have been fixed mid-late Sept, so I'm almost wondering if this is being routed around a problem that no longer exists. The route on your Vavle tracert does not go up to HK that I can tell. I'd expect a normal route to look like this one and go straight to Singapore. If you continue to see HK in tests run to our SGP IP, I'd definitely suspsect misrouting. Feel free to get any other tests sent over to us if you want to go over them with us. I'm hoping I was at least able to help a little but, but we'll always be here to help as much as we can.

 

 

Highlighted
Level 25: The Singularity
Level 25: The Singularity

Re: Problem with Perth to Singapore Routing

The truly odd thing is that you are getting a better response to valve, even though it is being routed through Singapore (202.84.224.197), then Hong Kong (210.176.138.193), then back to Singapore (103.10.124.1).

The Blizzard route (although can't tell what the steps 11-16 are) is Hong Kong (202.84.140.18) then Singapore for 9, 10 & 17. It's only showing a slower response at the final AWS node, so the problem could be at Amazon in Singapore.
Never be afraid to back yourself when trying new things, just always make sure you have 3 escape routes if things go wrong.
Highlighted
Level 2: Rookie

Re: Problem with Perth to Singapore Routing

The speculation at whirlpool is that it's the return path.

 

If I looking glass Perth to Hong Kong  and vice versa (POP to POP) it runs as expected linearly. However if I run from Hong Kong to my ip, rather than heading along the same path it heads via sydney melbourne adelaide and back to perth.

 

If the forward path is sneaking up to hong kong for some reason, then I wouldn't be surprised if it's using this return path back considering the latency.

Highlighted
Level 2: Rookie

Re: Problem with Perth to Singapore Routing

Anyone else in Perth have this issue?

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