Hi Everyone,
I have contacted telstra support regarding the international routing to Singapore going via sydney->honk kong as apposed to sydney->perth link which is causing higher latency to singapore services, though they dont know who to pass the request onto. They suggested that I post on the forums to see if I would get a better response here.
The international cable from perth to singapore has been down for a few months, though has now been repaired
http://status.vocus.com.au/view-incident.aspx?IncidentID=217
When will the better route(improved latency) be restored, or who would I contact?
Here is a trace route to a service that I use in singapore:
1 <1 ms <1 ms <1 ms hidden
2 5 ms 4 ms 5 ms hidden
3 6 ms 5 ms 5 ms hidden
4 7 ms 5 ms 5 ms bundle-ether4.cha-edge902.brisbane.telstra.net [203.50.44.38]
5 4 ms 7 ms 3 ms bundle-ether7.cha-core4.brisbane.telstra.net [203.50.11.142]
6 19 ms 23 ms 20 ms bundle-ether11.ken-core10.sydney.telstra.net [203.50.11.72]
7 19 ms 22 ms 22 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
8 20 ms 22 ms 22 ms bundle-ether1.sydp-core04.sydney.reach.com [203.50.13.90]
9 198 ms 202 ms 202 ms i-52.tlot-core02.bx.telstraglobal.net [202.84.137.101]
10 166 ms 163 ms 166 ms i-0-5-0-1.eqla01.bi.telstraglobal.net [202.84.253.6]
11 172 ms 173 ms 173 ms tisparkle-peer.eqla01.pr.telstraglobal.net [134.159.61.26]
12 253 ms 250 ms 255 ms te0-1-0-0.hongkong1.hok.seabone.net [195.22.206.165]
13 250 ms 249 ms 249 ms starhub.hongkong1.hok.seabone.net [195.22.223.145]
14 247 ms 249 ms 249 ms 203.118.15.181
15 249 ms 249 ms 249 ms 203.118.2.30
16 249 ms 249 ms 249 ms an-atl-int11.starhub.net.sg [203.118.15.86]
17 250 ms 249 ms 258 ms 203.116.7.78
18 * * * Request timed out.
19 251 ms 248 ms 249 ms 86.201.100.101.in-addr.arpa [101.100.201.86]
Solved! Go to Solution.
Yes I can, yay! no more hong kong, hello perth..
1 <1 ms <1 ms <1 ms hidden
2 3 ms 4 ms 4 ms hidden
3 6 ms 4 ms 5 ms hidden
4 7 ms 4 ms 4 ms bundle-ether4.woo-edge901.brisbane.telstra.net [203.50.44.36]
5 7 ms 2 ms 7 ms bundle-ether5.woo-core1.brisbane.telstra.net [203.50.11.136]
6 18 ms 15 ms 18 ms bundle-ether11.chw-core10.sydney.telstra.net [203.50.11.70]
7 29 ms 28 ms 29 ms bundle-ether8.exi-core10.melbourne.telstra.net [203.50.11.125]
8 44 ms 39 ms 43 ms bundle-ether5.way-core4.adelaide.telstra.net [203.50.11.92]
9 69 ms 66 ms 70 ms bundle-ether5.pie-core1.perth.telstra.net [203.50.11.17]
10 69 ms 68 ms 68 ms gigabitethernet0-7-0-0.pthp-core01.perth.net.reach.com [203.50.13.246]
11 121 ms 120 ms 117 ms i-0-1-3-0.sgpl-core01.bx.telstraglobal.net [202.84.143.181]
12 117 ms 114 ms 115 ms unknown.telstraglobal.net [202.84.224.186]
13 * * * Request timed out.
14 195 ms 190 ms 191 ms 29.168.22.103.in-addr.arpa [103.22.168.29]
15 193 ms 197 ms 198 ms tl1.tl1.sg.vodien.com [103.22.168.154]
16 * * * Request timed out.
17 117 ms 121 ms 120 ms 86.201.100.101.in-addr.arpa [101.100.201.86]
Reply from 101.100.201.86: bytes=32 time=120ms TTL=109
Reply from 101.100.201.86: bytes=32 time=115ms TTL=109
Reply from 101.100.201.86: bytes=32 time=117ms TTL=109
Reply from 101.100.201.86: bytes=32 time=115ms TTL=109
Was this helpful?
Thank you for your feedback
Thank you for your feedback
It will take some time to test and restore the routing tables...
yeah fair enough, though some isp's have moved over already, i know im keen
Yes, AARNET is switched on, getting average response time 165ms
cmon telstra
things are worse:
1 <1 ms <1 ms <1 ms hidden
2 3 ms 5 ms 5 ms hidden
3 2 ms 5 ms 5 ms hidden
4 2 ms 5 ms 5 ms bundle-ether4.cha-edge902.brisbane.telstra.net [203.50.44.38]
5 5 ms 3 ms 7 ms bundle-ether7.cha-core4.brisbane.telstra.net [203.50.11.142]
6 23 ms 22 ms 23 ms bundle-ether11.ken-core10.sydney.telstra.net [203.50.11.72]
7 21 ms 22 ms 21 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
8 19 ms 22 ms 22 ms bundle-ether1.sydp-core04.sydney.reach.com [203.50.13.90]
9 202 ms 202 ms 198 ms i-52.tlot-core02.bx.telstraglobal.net [202.84.137.101]
10 165 ms 167 ms 168 ms i-0-5-0-0.eqla01.bi.telstraglobal.net [202.84.253.2]
11 168 ms 168 ms 171 ms tisparkle-peer.eqla01.pr.telstraglobal.net [134.159.61.26]
12 304 ms 299 ms 302 ms te0-2-4-0.hongkong1.hok.seabone.net [195.22.206.185]
13 299 ms 301 ms 301 ms starhub.hongkong1.hok.seabone.net [195.22.223.145]
14 330 ms 330 ms 330 ms 203.118.15.186
15 299 ms 301 ms 302 ms 203.118.2.26
16 301 ms 301 ms 302 ms an-atl-int11.starhub.net.sg [203.118.15.82]
17 332 ms 330 ms 331 ms 203.116.7.78
18 * * * Request timed out.
19 304 ms 301 ms 301 ms 86.201.100.101.in-addr.arpa [101.100.201.86]
Hey KnoZiggeh,
I have received an update that you should now notice some improvement for this issue. Can you confirm this?
- 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
Yes I can, yay! no more hong kong, hello perth..
1 <1 ms <1 ms <1 ms hidden
2 3 ms 4 ms 4 ms hidden
3 6 ms 4 ms 5 ms hidden
4 7 ms 4 ms 4 ms bundle-ether4.woo-edge901.brisbane.telstra.net [203.50.44.36]
5 7 ms 2 ms 7 ms bundle-ether5.woo-core1.brisbane.telstra.net [203.50.11.136]
6 18 ms 15 ms 18 ms bundle-ether11.chw-core10.sydney.telstra.net [203.50.11.70]
7 29 ms 28 ms 29 ms bundle-ether8.exi-core10.melbourne.telstra.net [203.50.11.125]
8 44 ms 39 ms 43 ms bundle-ether5.way-core4.adelaide.telstra.net [203.50.11.92]
9 69 ms 66 ms 70 ms bundle-ether5.pie-core1.perth.telstra.net [203.50.11.17]
10 69 ms 68 ms 68 ms gigabitethernet0-7-0-0.pthp-core01.perth.net.reach.com [203.50.13.246]
11 121 ms 120 ms 117 ms i-0-1-3-0.sgpl-core01.bx.telstraglobal.net [202.84.143.181]
12 117 ms 114 ms 115 ms unknown.telstraglobal.net [202.84.224.186]
13 * * * Request timed out.
14 195 ms 190 ms 191 ms 29.168.22.103.in-addr.arpa [103.22.168.29]
15 193 ms 197 ms 198 ms tl1.tl1.sg.vodien.com [103.22.168.154]
16 * * * Request timed out.
17 117 ms 121 ms 120 ms 86.201.100.101.in-addr.arpa [101.100.201.86]
Reply from 101.100.201.86: bytes=32 time=120ms TTL=109
Reply from 101.100.201.86: bytes=32 time=115ms TTL=109
Reply from 101.100.201.86: bytes=32 time=117ms TTL=109
Reply from 101.100.201.86: bytes=32 time=115ms TTL=109
Hi People
This might be fixed but Telstra have not done anything about it see post
Other carriers seem to be utilising direct links but Telstra seems to be going around in circles in their exchanges
With direct debit there’s no need to give paying your bill another thought.
Avoid queuing up and never worry about late fees again.
Need a hand or want to share your expertise?
Register for CrowdSupport and get involved