Would appear this issue has resurfaced recently or is still onging?
<br>
<br> 1 115.31.88.230 (115.31.88.230) 0.890 ms 0.960 ms 1.141 ms
<br> 2 10.1.1.1 (10.1.1.1) 0.846 ms 0.838 ms 0.829 ms
<br> 3 <a href="http://c-20784-2726-VAIES-303-464.pr2.melb.nxg.net.au">c-20784-2726-VAIES-303-464.pr2.melb.nxg.net.au</a> (203.176.97.53)
14.941 ms 15.438 ms 15.454 ms
<br> 4 <a href="http://s-pr2-melb-1.br1.melb.nxg.net.au">s-pr2-melb-1.br1.melb.nxg.net.au</a> (121.200.224.151) 14.932 ms
15.382 ms 21.397 ms
<br> 5 <a href="http://GigabitEthernet7-19.lon55.Melbourne.telstra.net">GigabitEthernet7-19.lon55.Melbourne.telstra.net</a> (165.228.205.81)
2.433 ms 2.432 ms 2.456 ms
<br> 6 <a href="http://TenGigabitEthernet0-12-0-2.exi-core1.Melbourne.telstra.net">TenGigabitEthernet0-12-0-2.exi-core1.Melbourne.telstra.net</a>
(203.50.80.1) 2.457 ms 4.003 ms 3.996 ms
<br> 7 <a href="http://Bundle-Pos3.chw-core2.Sydney.telstra.net">Bundle-Pos3.chw-core2.Sydney.telstra.net</a> (203.50.11.14) 19.134 ms
19.161 ms 18.209 ms
<br> 8 <a href="http://Bundle-ether1.pad-gw1.Sydney.telstra.net">Bundle-ether1.pad-gw1.Sydney.telstra.net</a> (203.50.6.25) 18.069 ms
18.067 ms 18.090 ms
<br> 9 <a href="http://i-0-0-0-peer.sydp-core01.pr.reach.com">i-0-0-0-peer.sydp-core01.pr.reach.com</a> (134.159.126.33) 171.731 ms
171.750 ms 172.672 ms
<br>10 <a href="http://i-0-1-1-0.sydp-core05.bi.reach.com">i-0-1-1-0.sydp-core05.bi.reach.com</a> (202.84.220.209) 173.265 ms
172.752 ms 172.743 ms
<br>11 <a href="http://i-0-0-1-0.sydo-core02.bi.reach.com">i-0-0-1-0.sydo-core02.bi.reach.com</a> (202.84.249.14) 172.457 ms
172.486 ms 172.487 ms
<br>12 <a href="http://i-7-1-1.hptw-core01.bx.reach.com">i-7-1-1.hptw-core01.bx.reach.com</a> (202.84.142.154) 171.819 ms
171.923 ms 171.947 ms
<br>13 203.167.233.14 (203.167.233.14) 171.992 ms 171.983 ms 171.969 ms^C<br><br><div class="gmail_quote">On Tue, May 3, 2011 at 10:53 AM, Kevin Karp <span dir="ltr"><<a href="mailto:ausnog@pps.com.au">ausnog@pps.com.au</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi Don<br>
<br>
We have had a ticket open with Pacnet since early March highlighting the<br>
problem at<br>
<br>
<a href="http://pacifi121.lnk.telstra.net" target="_blank">pacifi121.lnk.telstra.net</a><br>
<br>
I believe the ticket is still open. Pacnet have never acknowledged the problem.<br>
They have many times requested traces and we have responded an equal number of<br>
times with results such as the one you listed.<br>
<br>
Unfortunately, I have no idea what the cause or remedy may be.<br>
<br>
Regards<br>
<br>
KJK<br>
<br>
Kevin Karp<br>
PPS Internet<br>
<br>
[p] <a href="tel:%2B61%202%209281%203905" value="+61292813905">+61 2 9281 3905</a><br>
[e] <a href="mailto:kjk@pps.com.au">kjk@pps.com.au</a><br>
[w] <a href="http://pps.com.au" target="_blank">pps.com.au</a><br>
<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
<a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</blockquote></div><br>