Guys, would you be able to help or maybe Telstraclear is reading this and could help me.

Im working from home and our central office is based in SYD. I have no problems with latency before with AU sites but for some reason I am getting high latency now..

here's sample trace result from home to pipenetworks (our AU ISP)

I am suprised below with line 7 (checked the IP lookup and it resolves to verizon) which is not i am getting before..


Tracing route to pipenetworks.com [203.161.158.4]

over a maximum of 30 hops:

 

  1     1 ms     1 ms     1 ms  192.168.1.1

  2    15 ms    35 ms     8 ms  10.33.32.1

  3    10 ms     8 ms     9 ms  lo0.internet.ivpn.pe25.telstraclear.net [218.101.61.124]

  4     *        *        *     Request timed out.

  5    18 ms    19 ms    21 ms  ie1-g-0-0-0.telstraclear.net [203.98.50.1]

  6    97 ms    19 ms    19 ms  ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251]

  7    20 ms    20 ms    20 ms  210.80.27.5

  8    19 ms    22 ms    19 ms  0.xo-1-0-0.xt4.akl1.alter.net [210.80.35.17]

  9   147 ms   148 ms   149 ms  0.so-5-1-0.ir2.sac2.alter.net [210.80.51.197]

 10   149 ms   148 ms   148 ms  0.so-2-0-0.il2.sac1.alter.net [152.63.48.41]

 11   151 ms   153 ms   152 ms  0.so-5-1-0.xl4.sjc7.alter.net [152.63.0.146]

 12   160 ms   154 ms   151 ms  0.ae4.br1.sjc7.alter.net [152.63.51.42]

 

now I tried tracing another site telstra.com.au

if you check line 7 again.. it is different from my first trace... the line 7 resolves to telstraclear IP which is actually good as it routes to reach.com (SYD).

Tracing route to telstra.com.au [144.140.108.25] over a maximum of 30 hops:

 

  1     1 ms     1 ms     1 ms  192.168.1.1

  2    11 ms    13 ms    11 ms  10.33.32.1

  3    10 ms    22 ms    34 ms  lo0.internet.ivpn.pe25.telstraclear.net [218.101.61.124]

  4     *        *        *     Request timed out.

  5    20 ms    20 ms    21 ms  ie1-g-0-0-0.telstraclear.net [203.98.50.1]

  6    24 ms    20 ms    22 ms  ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251]

  7    21 ms    18 ms    19 ms  203.167.233.10

  8    47 ms    52 ms    46 ms  i-3-1-0.syd-core03.bx.reach.com [202.84.142.153]

  9    45 ms    45 ms    46 ms  i-14-1-0.sydp-core01.bi.reach.com [202.84.249.13]

 10    51 ms    44 ms    46 ms  TenGigE0-3-0-7.pad-gw1.Sydney.telstra.net [203.50.13.89]

 11    46 ms    47 ms    50 ms  Bundle-Ether3.chw-core2.Sydney.telstra.net [203.50.6.26]

 12    59 ms    64 ms    59 ms  Bundle-Pos3.exi-core1.Melbourne.telstra.net [203.50.11.15]

 13    61 ms    59 ms    69 ms  TenGigabitEthernet8-1.exi1.Melbourne.telstra.net [203.50.80.11]

 14    61 ms    63 ms    64 ms  telstr310.lnk.telstra.net [139.130.36.186]

 15    70 ms    60 ms    59 ms  144.140.109.252
 

 13   152 ms   151 ms   151 ms  xe-9-2-0.edge1.sanjose3.level3.net [4.68.62.109]

 14   154 ms   155 ms   155 ms  ae-14-69.car4.sanjose1.level3.net [4.68.18.6]

 15   202 ms   202 ms   200 ms  certigo-inc.car4.sanjose1.level3.net [4.71.114.114]

 16   219 ms   222 ms   223 ms  gig2-2.rq-148brunswick-core-02.pipenetworks.com[203.161.129.254]

 17   223 ms   218 ms   218 ms  fast0.rq-127creek-1800-01.pipenetworks.com [203.161.129.58]

 18   220 ms   223 ms   221 ms  www.pipenetworks.com [203.161.158.4]

 

can anyone give some feedback or maybe try to do the same trace on pipenetworks.com and maybe you could get better latency?