Hey, I posted this on whirlpool but thought I would post it here for a more local (brisbane) audience.

Can anyone using iinet in Brisbane access www.newzbin.com ?

No.

Can anyone that is having problems e-mail me there username (bob342@gmail.com) so I can contact iinet so they can lodge a fault..apparently they need 3-5 people with the same problem to do this.

Or...if you dont' want to e-mail me the username, you could call them and quote job number 11930629

last edited by Tim Tibbetts at 23:17:00 21/Dec/05

Well this is interesting indeed. Here's the traceroute from my iinet account:

2 nexthop.qld.iinet.net.au (203.55.228.88) 14.657 ms 14.589 ms 15.471 ms
3 Gi2-4.bne-pipe-bdr1.chime.net.au (203.215.8.8) 15.991 ms 16.286 ms 15.003 ms
4 GigabitEthernet2-1.cha23.Brisbane.telstra.net (139.130.130.37) 16.689 ms 15.869 ms 16.721 ms
5 GigabitEthernet1-0.cha-core4.Brisbane.telstra.net (203.50.51.1) 16.264 ms 16.099 ms 15.976 ms
6 Pos-channel1.chw-core2.Sydney.telstra.net (203.50.6.225) 29.650 ms 29.569 ms 29.787 ms
7 10GigabitEthernet1-0.oxf-core1.Sydney.telstra.net (203.50.6.2) 29.804 ms 29.417 ms 29.780 ms
8 10GigabitEthernet6-0.syd-core04.Sydney.net.reach.com (203.50.13.34) 30.549 ms 30.905 ms 57.092 ms
9 i-5-0.paix-core01.net.reach.com (202.84.143.205) 189.703 ms 190.107 ms 188.683 ms
10 i-2-0.chi-core01.net.reach.com (202.84.249.78) 258.733 ms 259.767 ms 259.904 ms
11 unknown.net.reach.com (202.84.249.134) 280.313 ms 279.577 ms 280.055 ms
12 i-6-0.lnx01.net.reach.com (202.84.144.142) 350.549 ms 350.776 ms 351.033 ms
13 unknown.net.reach.com (202.40.148.53) 357.426 ms 357.223 ms 356.425 ms
14 ldn-s2-rou-1002.UK.eurorings.net (195.66.224.54) 368.010 ms 367.068 ms 367.760 ms
15 * * *

The site works fine using telstra's open proxy ( brisbane.cache.telstra.net:3128 ).

Also, when I use telstra's tracing site ( http://www.telstra.net/cgi-bin/trace ), it works fine:

1 vlan250.lon-service6.Melbourne.telstra.net (203.50.2.177) 0.36 ms 0.225 ms 0.241 ms
2 10GigabitEthernet9-0.win-core1.Melbourne.telstra.net (203.50.79.129) 170.356 ms 168.079 ms 0.578 ms
3 Pos-Channel2.ken-core4.Sydney.telstra.net (203.50.6.21) 12.914 ms 12.988 ms 12.965 ms
4 10GigabitEthernet3-0.pad-core4.Sydney.telstra.net (203.50.6.86) 13.07 ms 13.021 ms 12.963 ms
5 10GigabitEthernet2-2.syd-core02.Sydney.net.reach.com (203.50.13.42) 13.21 ms 13.187 ms 13.111 ms
6 i-0-0.wil-core02.net.reach.com (202.84.144.101) 161.383 ms 161.31 ms 161.34 ms
7 i-2-0.dal-core01.net.reach.com (202.84.143.66) 192.965 ms 202.781 ms 193.159 ms
8 i-10-0.chi-core01.net.reach.com (202.84.143.69) 242.655 ms 242.692 ms 242.658 ms
9 unknown.net.reach.com (202.84.249.134) 268.864 ms 268.838 ms 268.83 ms
10 i-6-1.lnx01.net.reach.com (202.84.249.94) 333.802 ms 333.926 ms 333.849 ms
11 unknown.net.reach.com (202.40.148.53) 339.744 ms 339.773 ms 339.702 ms
12 ldn-s2-rou-1002.UK.eurorings.net (195.66.224.54) 351.428 ms 351.349 ms 351.396 ms
13 134.222.109.222 (134.222.109.222) 350.265 ms 350.357 ms 350.296 ms
14 www3.newzbin.com (212.13.207.121) 345.21 ms 345.109 ms 345.611 ms

Seems that both traceroutes show an identical final path for the packets ... but the iinet one fails.


last edited by parabol at 23:45:45 21/Dec/05

hmm Gripping Stuff.