[AusNOG] Telstra --> Pacific hand over problem? RESOLVED (again)
Don Gould
don at bowenvale.co.nz
Sat May 28 12:56:49 EST 2011
On 28/05/2011 2:41 p.m., Brett wrote:
> Don,
>
> Sorry Don i should been clearer in my first email, problem is to
> Telstra Clear not Pacific.
Sorry Brett, I didn't read your message clearly. I ran a quick test and
noted that the links were bent.
The link from this end looks ok now though...
1.
router
0.0% 15 0.2 0.2 0.2 0.4 0.0
2. ???
3.
lo0.internet.ivpn.pe22.telstraclear.net
0.0% 14 14.3 16.4 9.3 55.3 11.7
4. ???
5.
ie1-g-0-0-0.telstraclear.net
0.0% 14 22.6 24.1 22.4 27.1 1.5
6.
ge-0-2-0-1.xcore1.acld.telstraclear.net
0.0% 14 24.4 24.3 22.5 28.3 1.6
7.
210.80.27.5
0.0% 14 23.0 25.7 22.5 31.8 3.1
8.
0.xo-1-0-0.xt3.akl1.alter.net
0.0% 14 23.9 27.0 23.2 37.8 4.6
9.
0.ge-7-1-0.xt3.syd4.alter.net
0.0% 14 54.1 54.4 46.1 129.3 21.7
10.
so-6-0-0.gw4.syd4.alter.net
0.0% 14 46.1 53.3 46.0 113.5 17.6
11.
nextgen-syd4-gw.customer.alter.net
0.0% 14 50.2 50.1 48.2 54.5 1.6
12.
s-br1-sydn-1.pr2.melb.nxg.net.au
0.0% 14 63.2 66.2 61.0 80.8 6.2
13.
c-20784-2726-vaies-303-464.cust.nxg.net.au
0.0% 14 63.5 65.1 62.0 72.6 3.6
14.
115.31.88.230
0.0% 14 62.4 64.0 61.4 67.4 1.9
.... though there are some bends in there as well...
1.
router
0.0% 134 0.2 0.2 0.2 0.4 0.0
2. ???
3.
lo0.internet.ivpn.pe22.telstraclear.net
0.0% 134 14.3 13.2 8.4 55.3 6.0
4. ???
5.
ie1-g-0-0-0.telstraclear.net
0.0% 134 21.3 25.1 21.3 58.6 5.3
6.
ge-0-2-0-1.xcore1.acld.telstraclear.net
0.0% 134 23.2 25.2 21.8 53.8 5.2
7.
210.80.27.5
0.0% 133 26.4 25.0 22.0 41.5 2.8
8.
0.xo-1-0-0.xt3.akl1.alter.net
0.0% 133 29.4 26.1 22.1 49.2 4.5
9.
0.ge-7-1-0.xt3.syd4.alter.net
0.0% 133 51.5 51.1 45.3 129.3 12.3
10.
so-6-0-0.gw4.syd4.alter.net
0.0% 133 53.3 51.7 46.0 122.6 11.4
11.
nextgen-syd4-gw.customer.alter.net
0.0% 133 50.3 51.0 47.7 74.2 3.8
12.
s-br1-sydn-1.pr2.melb.nxg.net.au
0.0% 133 66.9 64.5 60.5 84.8 4.3
13.
c-20784-2726-vaies-303-464.cust.nxg.net.au
0.0% 133 62.4 65.8 59.9 *197.4* 15.7
14.
115.31.88.230
0.0% 133 73.4 63.8 60.5 79.8 2.9
A lot less bent out of my wellington location...
Host Loss% Snt Last Avg Best Wrst StDev
1.
202.68.81.105
0.0% 14 0.2 0.2 0.2 0.4 0.1
2.
ge0-3.cr2.wlg.dts.net.nz
0.0% 14 4.8 4.7 4.2 5.3 0.3
3.
124.157.96.194
0.0% 14 31.4 18.2 14.6 31.4 5.4
4.
vocus1.ape.net.nz
0.0% 13 15.8 16.1 15.8 17.0 0.3
5.
ten-0-2-0-400.bdr01.akl01.akl.VOCUS.net.au
0.0% 13 52.7 52.8 52.1 54.4 0.5
6.
ip-128.192.31.114.VOCUS.net.au
0.0% 13 53.3 53.0 52.5 53.5 0.3
7.
ge-0-0-0.bdr01.mel04.vic.VOCUS.net.au
0.0% 13 53.3 54.0 53.0 60.5 2.0
8.
ge-0-0-0.bdr02.mel04.vic.VOCUS.net.au
0.0% 13 54.8 53.3 52.7 54.8 0.7
9.
ge-0-0-2.bdr01.mel01.vic.VOCUS.net.au
0.0% 13 52.5 52.7 52.2 53.2 0.3
10. ???
11.
115.31.88.230
0.0% 13 53.2 53.6 51.9 56.1 1.2
Hope this info helps you to get a resolution :)
D
>
> 1 115.31.88.230 (115.31.88.230) 0.866 ms 0.998 ms 1.140 ms
> 2 10.1.1.1 (10.1.1.1) 0.812 ms 0.804 ms 0.793 ms
> 3 c-20784-2726-VAIES-303-464.pr2.melb.nxg.net.au
> <http://c-20784-2726-VAIES-303-464.pr2.melb.nxg.net.au>
> (203.176.97.53) 16.258 ms 17.217 ms 17.213 ms
> 4 s-pr2-melb-1.br1.melb.nxg.net.au
> <http://s-pr2-melb-1.br1.melb.nxg.net.au> (121.200.224.151) 16.223 ms
> 17.062 ms 17.102 ms
> 5 GigabitEthernet7-19.lon55.Melbourne.telstra.net
> <http://GigabitEthernet7-19.lon55.Melbourne.telstra.net>
> (165.228.205.81) 3.307 ms 3.338 ms 3.363 ms
> 6 TenGigabitEthernet0-12-0-2.exi-core1.Melbourne.telstra.net
> <http://TenGigabitEthernet0-12-0-2.exi-core1.Melbourne.telstra.net>
> (203.50.80.1) 3.305 ms 3.573 ms 3.552 ms
> 7 Bundle-Pos3.chw-core2.Sydney.telstra.net
> <http://Bundle-Pos3.chw-core2.Sydney.telstra.net> (203.50.11.14)
> 22.170 ms 22.171 ms 19.729 ms
> 8 Bundle-ether1.pad-gw1.Sydney.telstra.net
> <http://Bundle-ether1.pad-gw1.Sydney.telstra.net> (203.50.6.25)
> 19.645 ms 19.642 ms 19.669 ms
> 9 i-0-0-0-peer.sydp-core01.pr.reach.com
> <http://i-0-0-0-peer.sydp-core01.pr.reach.com> (134.159.126.33)
> 173.099 ms 173.103 ms 173.108 ms
> 10 i-0-1-1-0.sydp-core05.bi.reach.com
> <http://i-0-1-1-0.sydp-core05.bi.reach.com> (202.84.220.209) 173.665
> ms 173.702 ms 173.698 ms
> 11 i-0-0-1-0.sydo-core02.bi.reach.com
> <http://i-0-0-1-0.sydo-core02.bi.reach.com> (202.84.249.14) 174.293
> ms 174.319 ms 174.319 ms
> 12 i-7-1-1.hptw-core01.bx.reach.com
> <http://i-7-1-1.hptw-core01.bx.reach.com> (202.84.142.154) 173.560 ms
> 171.763 ms 171.757 ms
> 13 203.167.233.14 (203.167.233.14) 172.483 ms 172.524 ms 171.950 ms
> 14 ie1-g-0-0-0.telstraclear.net <http://ie1-g-0-0-0.telstraclear.net>
> (203.98.50.1) 172.741 ms 173.478 ms 173.475 ms
> 15 121-74-224-1.telstraclear.net
> <http://121-74-224-1.telstraclear.net> (121.74.224.1) 189.188 ms
> 189.221 ms 189.303 ms^C
>
>
> On Sat, May 28, 2011 at 12:06 PM, Don Gould <don at bowenvale.co.nz
> <mailto:don at bowenvale.co.nz>> wrote:
>
> Brett,
>
> Ok, seems to be bent back into shape again. :)
>
> Is it looking better for you as well now?
>
> D
>
> 1.
> router
> 0.0% 6 0.2 0.2 0.2 0.2 0.0
> <tel:0.2%C2%A0%C2%A0%200.2%C2%A0%C2%A0%200.2%C2%A0%C2%A0%200.2%C2%A0%C2%A0%200.0>
> 2. ???
> 3. lo0.internet.ivpn.pe22.telstraclear.net
> <http://lo0.internet.ivpn.pe22.telstraclear.net>
> 0.0% 6 13.2 14.9 9.2 21.3 4.9
> 4. ???
> 5. ie1-g-0-0-0.telstraclear.net
> <http://ie1-g-0-0-0.telstraclear.net>
> 0.0% 6 24.8 24.5 23.5 25.5 0.8
> 6. ge-0-2-0-1.xcore1.acld.telstraclear.net
> <http://ge-0-2-0-1.xcore1.acld.telstraclear.net>
> 0.0% 6 22.0 28.6 22.0 50.0 11.0
> 7.
> 203.167.233.10
> 0.0% 6 24.5 24.6 22.3 25.6 1.3
> 8. i-3-1-0.syd-core03.bx.reach.com
> <http://i-3-1-0.syd-core03.bx.reach.com>
> 0.0% 6 50.4 48.9 46.5 50.8 2.0
> 9. i-0-5-4-0.sydp-core05.bx.reach.com
> <http://i-0-5-4-0.sydp-core05.bx.reach.com>
> 0.0% 6 50.6 48.9 48.0 50.6 1.0
> 10. i-11-0-0.sydp-core01.bi.reach.com
> <http://i-11-0-0.sydp-core01.bi.reach.com>
> 0.0% 6 48.6 48.5 47.5 49.2 0.7
> 11. telstra_domestic_peer-peer.sydp-core01.pr.reach.com
> <http://telstra_domestic_peer-peer.sydp-core01.pr.reach.com>
> 0.0% 6 64.2 54.7 51.6 64.2 4.7
> 12. bundle-ether3.chw-core2.sydney.telstra.net
> <http://bundle-ether3.chw-core2.sydney.telstra.net>
> 0.0% 6 51.4 50.9 48.2 52.6 1.7
> 13. tengigabitethernet7-1.ult1.sydney.telstra.net
> <http://tengigabitethernet7-1.ult1.sydney.telstra.net>
> 0.0% 5 49.2 50.3 49.2 51.2 0.8
> 14. pacifi121.lnk.telstra.net
> <http://pacifi121.lnk.telstra.net>
> 0.0% 5 51.2 50.4 48.5 53.4 2.0
> 15. vl63.switch1.syd.pacific.net.au
> <http://vl63.switch1.syd.pacific.net.au>
> 0.0% 5 200.1 154.2 51.3 235.0 76.2
> 16. bvi11-0.cr-rtr01.ult.bulletproof.net
> <http://bvi11-0.cr-rtr01.ult.bulletproof.net>
> 0.0% 5 50.4 53.0 50.4 55.9 2.5
> 17. 171-171-53-117.rev.bulletproof.net
> <http://171-171-53-117.rev.bulletproof.net>
> 0.0% 5 48.7 50.0 48.7 52.2 1.4
>
>
> --> 15. vl63.switch1.syd.pacific.net.au
> <http://vl63.switch1.syd.pacific.net.au>
> 0.0% 5 200.1 154.2 51.3 235.0 76.2
> That hop is often a bit bent out of shape. I have commented to
> Telstra about it, but got no comment back.
>
> Tracing the route to121-73-114-1.cable.telstraclear.net <http://121-73-114-1.cable.telstraclear.net> (121.73.114.1)
>
> 1vl96.switch2.syd.pacific.net.au <http://vl96.switch2.syd.pacific.net.au> (61.8.2.1) 0 msec
> vl98.switch1.syd.pacific.net.au <http://vl98.switch1.syd.pacific.net.au> (210.23.140.1 <tel:%28210.23.140.1>) 0 msec
> vl96.switch2.syd.pacific.net.au <http://vl96.switch2.syd.pacific.net.au> (61.8.2.1) 0 msec
> 2vl63.switch2.syd.pacific.net.au <http://vl63.switch2.syd.pacific.net.au> (125.255.94.122) 4 msec
> GigabitEthernet3-1.ult1.Sydney.telstra.net <http://GigabitEthernet3-1.ult1.Sydney.telstra.net> (139.130.248.85) 0 msec
> vl63.switch2.syd.pacific.net.au <http://vl63.switch2.syd.pacific.net.au> (125.255.94.122) 0 msec
> 3TenGigE0-1-0-0.chw-core2.Sydney.telstra.net <http://TenGigE0-1-0-0.chw-core2.Sydney.telstra.net> (203.50.20.129) 4 msec
> GigabitEthernet3-1.ult1.Sydney.telstra.net <http://GigabitEthernet3-1.ult1.Sydney.telstra.net> (139.130.248.85) 0 msec
> TenGigE0-1-0-0.chw-core2.Sydney.telstra.net <http://TenGigE0-1-0-0.chw-core2.Sydney.telstra.net> (203.50.20.129) 0 msec
> 4TenGigE0-1-0-0.chw-core2.Sydney.telstra.net <http://TenGigE0-1-0-0.chw-core2.Sydney.telstra.net> (203.50.20.129) 0 msec
> Bundle-ether1.pad-gw1.Sydney.telstra.net <http://Bundle-ether1.pad-gw1.Sydney.telstra.net> (203.50.6.25) 4 <tel:%28203.50.6.25%29%204> msec
> TenGigE0-1-0-0.chw-core2.Sydney.telstra.net <http://TenGigE0-1-0-0.chw-core2.Sydney.telstra.net> (203.50.20.129) 0 msec
> 5i-0-0-0-peer.sydp-core01.pr.reach.com <http://i-0-0-0-peer.sydp-core01.pr.reach.com> (134.159.126.33) 0 msec
> Bundle-ether1.pad-gw1.Sydney.telstra.net <http://Bundle-ether1.pad-gw1.Sydney.telstra.net> (203.50.6.25) 8 <tel:%28203.50.6.25%29%208> msec
> i-0-0-0-peer.sydp-core01.pr.reach.com <http://i-0-0-0-peer.sydp-core01.pr.reach.com> (134.159.126.33) 0 msec
> 6i-0-0-0-peer.sydp-core01.pr.reach.com <http://i-0-0-0-peer.sydp-core01.pr.reach.com> (134.159.126.33) 0 msec
> i-0-1-1-0.sydp-core05.bi.reach.com <http://i-0-1-1-0.sydp-core05.bi.reach.com> (202.84.220.209) 0 msec
> i-0-0-0-peer.sydp-core01.pr.reach.com <http://i-0-0-0-peer.sydp-core01.pr.reach.com> (134.159.126.33) 4 msec
> 7i-0-0-1-0.sydo-core02.bi.reach.com <http://i-0-0-1-0.sydo-core02.bi.reach.com> (202.84.249.14) 4 msec
> i-0-1-1-0.sydp-core05.bi.reach.com <http://i-0-1-1-0.sydp-core05.bi.reach.com> (202.84.220.209) 0 msec
> i-0-0-1-0.sydo-core02.bi.reach.com <http://i-0-0-1-0.sydo-core02.bi.reach.com> (202.84.249.14) 0 msec
> 8i-0-0-1-0.sydo-core02.bi.reach.com <http://i-0-0-1-0.sydo-core02.bi.reach.com> (202.84.249.14) 4 msec
> i-7-1-1.hptw-core01.bx.reach.com <http://i-7-1-1.hptw-core01.bx.reach.com> (202.84.142.154) 24 msec
> i-0-0-1-0.sydo-core02.bi.reach.com <http://i-0-0-1-0.sydo-core02.bi.reach.com> (202.84.249.14) 4 msec
> 9 203.167.233.14 [AS 4768] 24 msec
> i-7-1-1.hptw-core01.bx.reach.com <http://i-7-1-1.hptw-core01.bx.reach.com> (202.84.142.154) 24 msec
> 203.167.233.14 [AS 4768] 28 msec
> 10 203.167.233.14 [AS 4768] 24 msec
> ie1-g-0-0-0.telstraclear.net <http://ie1-g-0-0-0.telstraclear.net> (203.98.50.1) [AS 4768] 24 msec
> 203.167.233.14 [AS 4768] 28 msec
> 11 *
> ie1-g-0-0-0.telstraclear.net <http://ie1-g-0-0-0.telstraclear.net> (203.98.50.1) [AS 4768] 60 msec *
> 12 *
>
>
> 121-73-114-1.cable.telstraclear.net <http://121-73-114-1.cable.telstraclear.net> (121.73.114.1) 40 msec *
>
>
>
> On 28/05/2011 11:05 a.m., Don Gould wrote:
>> Use http://mrtg.pacific.net.au/zip-lg.html to trace to my gw -
>> 121.73.114.1
>>
>> I could be wrong, but I think this time it is a fault in Telstra
>> Australia. The trace looks different from the last one I had.
>>
>> I'll throw this at t.au off list as well, though I'm sure they've
>> seen it.
>>
>> D
>>
>>
>> Type escape sequence to abort.
>> Tracing the route to121-73-114-1.cable.telstraclear.net <http://121-73-114-1.cable.telstraclear.net> (121.73.114.1)
>>
>> 1vl96.switch2.syd.pacific.net.au <http://vl96.switch2.syd.pacific.net.au> (61.8.2.1) 0 msec
>> vl98.switch1.syd.pacific.net.au <http://vl98.switch1.syd.pacific.net.au> (210.23.140.1 <tel:%28210.23.140.1>) 4 msec
>> vl96.switch2.syd.pacific.net.au <http://vl96.switch2.syd.pacific.net.au> (61.8.2.1) 0 msec
>> 2vl63.switch2.syd.pacific.net.au <http://vl63.switch2.syd.pacific.net.au> (125.255.94.122) 0 msec
>> GigabitEthernet3-1.ult1.Sydney.telstra.net <http://GigabitEthernet3-1.ult1.Sydney.telstra.net> (139.130.248.85) 0 msec
>> vl63.switch2.syd.pacific.net.au <http://vl63.switch2.syd.pacific.net.au> (125.255.94.122) 0 msec
>> 3TenGigE0-1-0-0.chw-core2.Sydney.telstra.net <http://TenGigE0-1-0-0.chw-core2.Sydney.telstra.net> (203.50.20.129) 0 msec
>> GigabitEthernet3-1.ult1.Sydney.telstra.net <http://GigabitEthernet3-1.ult1.Sydney.telstra.net> (139.130.248.85) 0 msec
>> TenGigE0-1-0-0.chw-core2.Sydney.telstra.net <http://TenGigE0-1-0-0.chw-core2.Sydney.telstra.net> (203.50.20.129) 0 msec
>> 4TenGigE0-1-0-0.chw-core2.Sydney.telstra.net <http://TenGigE0-1-0-0.chw-core2.Sydney.telstra.net> (203.50.20.129) 4 msec
>> Bundle-ether1.pad-gw1.Sydney.telstra.net <http://Bundle-ether1.pad-gw1.Sydney.telstra.net> (203.50.6.25) 4 <tel:%28203.50.6.25%29%204> msec
>> TenGigE0-1-0-0.chw-core2.Sydney.telstra.net <http://TenGigE0-1-0-0.chw-core2.Sydney.telstra.net> (203.50.20.129) 4 msec
>> 5i-0-0-0-peer.sydp-core01.pr.reach.com <http://i-0-0-0-peer.sydp-core01.pr.reach.com> (134.159.126.33) 0 msec
>> Bundle-ether1.pad-gw1.Sydney.telstra.net <http://Bundle-ether1.pad-gw1.Sydney.telstra.net> (203.50.6.25) 4 <tel:%28203.50.6.25%29%204> msec
>> i-0-0-0-peer.sydp-core01.pr.reach.com <http://i-0-0-0-peer.sydp-core01.pr.reach.com> (134.159.126.33) 0 msec
>> 6i-0-0-0-peer.sydp-core01.pr.reach.com <http://i-0-0-0-peer.sydp-core01.pr.reach.com> (134.159.126.33) 0 msec
>> i-0-1-1-0.sydp-core05.bi.reach.com <http://i-0-1-1-0.sydp-core05.bi.reach.com> (202.84.220.209) 4 msec
>> i-0-0-0-peer.sydp-core01.pr.reach.com <http://i-0-0-0-peer.sydp-core01.pr.reach.com> (134.159.126.33) 0 msec
>> 7i-0-0-1-0.sydo-core02.bi.reach.com <http://i-0-0-1-0.sydo-core02.bi.reach.com> (202.84.249.14) 4 msec
>> i-0-1-1-0.sydp-core05.bi.reach.com <http://i-0-1-1-0.sydp-core05.bi.reach.com> (202.84.220.209) 0 msec
>> i-0-0-1-0.sydo-core02.bi.reach.com <http://i-0-0-1-0.sydo-core02.bi.reach.com> (202.84.249.14) 4 msec
>> 8i-0-0-1-0.sydo-core02.bi.reach.com <http://i-0-0-1-0.sydo-core02.bi.reach.com> (202.84.249.14) 4 msec
>> i-7-1-1.hptw-core01.bx.reach.com <http://i-7-1-1.hptw-core01.bx.reach.com> (202.84.142.154) 24 msec
>> i-0-0-1-0.sydo-core02.bi.reach.com <http://i-0-0-1-0.sydo-core02.bi.reach.com> (202.84.249.14) 8 msec
>> 9 203.167.233.14 [AS 4768] 168 msec
>> i-7-1-1.hptw-core01.bx.reach.com <http://i-7-1-1.hptw-core01.bx.reach.com> (202.84.142.154) 24 msec
>> 203.167.233.14 [AS 4768] 168 msec
>> 10 203.167.233.14 [AS 4768] 168 msec
>> ie1-g-0-0-0.telstraclear.net <http://ie1-g-0-0-0.telstraclear.net> (203.98.50.1) [AS 4768] 168 msec
>> 203.167.233.14 [AS 4768] 188 msec
>> 11 *
>> ie1-g-0-0-0.telstraclear.net <http://ie1-g-0-0-0.telstraclear.net> (203.98.50.1) [AS 4768] 164 msec *
>> 12 *
>>
>> 121-73-114-1.cable.telstraclear.net <http://121-73-114-1.cable.telstraclear.net> (121.73.114.1) 180 msec *
>>
>>
>> On 28/05/2011 11:01 a.m., Don Gould wrote:
>>> Yip, it's back for me as well.
>>>
>>> The PN guys do monitor this list, so it would be NICE if they'd
>>> just drop a note on list to say "got it" so we don't have to
>>> chase everyone again.
>>>
>>> I'll check it from their looking glass a bit later and confirm
>>> it's the same issue and bump their guys an off list note. It
>>> will be effecting the same pplz again by the looks.
>>>
>>> I understand the issue is that they lost some transit because of
>>> a cable cut. I'm going to guess they got the transit back but
>>> it's stuff up their routing in the process.... but that really
>>> is just a guess (while trying to connect some dots that might or
>>> might not relate).
>>>
>>> D
>>>
>>> On 27/05/2011 11:56 p.m., Brett wrote:
>>>> Would appear this issue has resurfaced recently or is still
>>>> onging?
>>>>
>>>> 1 115.31.88.230 (115.31.88.230) 0.890 ms 0.960 ms 1.141 ms
>>>> 2 10.1.1.1 (10.1.1.1) 0.846 ms 0.838 ms 0.829 ms
>>>> 3 c-20784-2726-VAIES-303-464.pr2.melb.nxg.net.au
>>>> <http://c-20784-2726-VAIES-303-464.pr2.melb.nxg.net.au>
>>>> (203.176.97.53) 14.941 ms 15.438 ms 15.454 ms
>>>> 4 s-pr2-melb-1.br1.melb.nxg.net.au
>>>> <http://s-pr2-melb-1.br1.melb.nxg.net.au> (121.200.224.151)
>>>> 14.932 ms 15.382 ms 21.397 ms
>>>> 5 GigabitEthernet7-19.lon55.Melbourne.telstra.net
>>>> <http://GigabitEthernet7-19.lon55.Melbourne.telstra.net>
>>>> (165.228.205.81) 2.433 ms 2.432 ms 2.456 ms
>>>> 6 TenGigabitEthernet0-12-0-2.exi-core1.Melbourne.telstra.net
>>>> <http://TenGigabitEthernet0-12-0-2.exi-core1.Melbourne.telstra.net>
>>>> (203.50.80.1) 2.457 ms 4.003 ms 3.996 ms
>>>> 7 Bundle-Pos3.chw-core2.Sydney.telstra.net
>>>> <http://Bundle-Pos3.chw-core2.Sydney.telstra.net> (203.50.11.14
>>>> <tel:%28203.50.11.14>) 19.134 ms 19.161 ms 18.209 ms
>>>> 8 Bundle-ether1.pad-gw1.Sydney.telstra.net
>>>> <http://Bundle-ether1.pad-gw1.Sydney.telstra.net>
>>>> (203.50.6.25) 18.069 ms 18.067 ms 18.090 ms
>>>> 9 i-0-0-0-peer.sydp-core01.pr.reach.com
>>>> <http://i-0-0-0-peer.sydp-core01.pr.reach.com>
>>>> (134.159.126.33) 171.731 ms 171.750 ms 172.672 ms
>>>> 10 i-0-1-1-0.sydp-core05.bi.reach.com
>>>> <http://i-0-1-1-0.sydp-core05.bi.reach.com> (202.84.220.209)
>>>> 173.265 ms 172.752 ms 172.743 ms
>>>> 11 i-0-0-1-0.sydo-core02.bi.reach.com
>>>> <http://i-0-0-1-0.sydo-core02.bi.reach.com> (202.84.249.14)
>>>> 172.457 ms 172.486 ms 172.487 ms
>>>> 12 i-7-1-1.hptw-core01.bx.reach.com
>>>> <http://i-7-1-1.hptw-core01.bx.reach.com> (202.84.142.154)
>>>> 171.819 ms 171.923 ms 171.947 ms
>>>> 13 203.167.233.14 (203.167.233.14) 171.992 ms 171.983 ms
>>>> 171.969 ms^C
>>>>
>>>> On Tue, May 3, 2011 at 10:53 AM, Kevin Karp <ausnog at pps.com.au
>>>> <mailto:ausnog at pps.com.au>> wrote:
>>>>
>>>> Hi Don
>>>>
>>>> We have had a ticket open with Pacnet since early March
>>>> highlighting the
>>>> problem at
>>>>
>>>> pacifi121.lnk.telstra.net <http://pacifi121.lnk.telstra.net>
>>>>
>>>> I believe the ticket is still open. Pacnet have never
>>>> acknowledged the problem.
>>>> They have many times requested traces and we have responded
>>>> an equal number of
>>>> times with results such as the one you listed.
>>>>
>>>> Unfortunately, I have no idea what the cause or remedy may be.
>>>>
>>>> Regards
>>>>
>>>> KJK
>>>>
>>>> Kevin Karp
>>>> PPS Internet
>>>>
>>>> [p] +61 2 9281 3905 <tel:%2B61%202%209281%203905>
>>>> [e] kjk at pps.com.au <mailto:kjk at pps.com.au>
>>>> [w] pps.com.au <http://pps.com.au>
>>>>
>>>> _______________________________________________
>>>> AusNOG mailing list
>>>> AusNOG at lists.ausnog.net <mailto:AusNOG at lists.ausnog.net>
>>>> http://lists.ausnog.net/mailman/listinfo/ausnog
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> AusNOG mailing list
>>>> AusNOG at lists.ausnog.net <mailto:AusNOG at lists.ausnog.net>
>>>> http://lists.ausnog.net/mailman/listinfo/ausnog
>>>
>>>
>>> --
>>> Don Gould
>>> 31 Acheson Ave
>>> Mairehau
>>> Christchurch, New Zealand
>>> Ph:+ 64 3 348 7235 <tel:%2B%2064%203%20348%207235>
>>> Mobile:+ 64 21 114 0699 <tel:%2B%2064%2021%20114%200699>
>>>
>>>
>>> _______________________________________________
>>> AusNOG mailing list
>>> AusNOG at lists.ausnog.net <mailto:AusNOG at lists.ausnog.net>
>>> http://lists.ausnog.net/mailman/listinfo/ausnog
>>
>>
>> --
>> Don Gould
>> 31 Acheson Ave
>> Mairehau
>> Christchurch, New Zealand
>> Ph:+ 64 3 348 7235 <tel:%2B%2064%203%20348%207235>
>> Mobile:+ 64 21 114 0699 <tel:%2B%2064%2021%20114%200699>
>>
>>
>> _______________________________________________
>> AusNOG mailing list
>> AusNOG at lists.ausnog.net <mailto:AusNOG at lists.ausnog.net>
>> http://lists.ausnog.net/mailman/listinfo/ausnog
>
>
> --
> Don Gould
> 31 Acheson Ave
> Mairehau
> Christchurch, New Zealand
> Ph:+ 64 3 348 7235 <tel:%2B%2064%203%20348%207235>
> Mobile:+ 64 21 114 0699 <tel:%2B%2064%2021%20114%200699>
>
>
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net <mailto:AusNOG at lists.ausnog.net>
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
>
--
Don Gould
31 Acheson Ave
Mairehau
Christchurch, New Zealand
Ph: + 64 3 348 7235
Mobile: + 64 21 114 0699
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20110528/8222f3d0/attachment.html>
More information about the AusNOG
mailing list