PDA

View Full Version : Internode issues?



Disko
16th August 2004, 10:12 AM
Is anyone else having issues with internode this morning? I can't connect to my instant messenger networks, or irc. I can only browse a handful of sites (and whirlpool is not one of them).

This is what my traceroute to whirlpool.net.au looks like at the moment...


PB17:~ Disko$ traceroute whirlpool.net.au
traceroute to whirlpool.net.au (202.139.232.71), 30 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 7.509 ms 2.26 ms 2.22 ms
2 loop0.lns1.adl1.internode.on.net (203.16.215.216) 19.741 ms 10.725 ms 12.93 ms
3 gi0-2-13.cor1.adl1.internode.on.net (203.16.212.213) 12.38 ms 11.608 ms 12.478 ms
4 * * *
5 * * *
6 * as7496.brisbane.pipenetworks.com (218.100.0.20) 58.5 ms 54.867 ms
7 gi0-2-6.xr3.wic.server-web.com (203.147.255.123) 61.044 ms 57.24 ms 63.267 ms
8 * * *
9 vl5.mls1.bne.server-web.com (203.147.255.45) 54.688 ms 240.901 ms 206.633 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *

I just want to make sure its not me before i phone the node.

Ozi
16th August 2004, 10:24 AM
Thats got some big issues! I would be calling them up. Im not on internode, but i have had problems with optus and you just have to be persistant and by nagging them enough, they will fix it. Is internode an ISP?

MacDave
16th August 2004, 10:26 AM
[c-67-160-223-74:~] davepere% timein Sydney
Mon Aug 16 10:26:22 EST 2004


traceroute to whirlpool.net.au (202.139.232.71), 30 hops max, 40 byte packets
1 10.144.248.1 (10.144.248.1) 9.561 ms 9.669 ms 9.156 ms
2 12.244.97.113 (12.244.97.113) 7.594 ms 7.782 ms 8.942 ms
3 12.244.67.86 (12.244.67.86) 37.835 ms 30.808 ms 11.733 ms
4 12.127.32.45 (12.127.32.45) 12.307 ms 11.885 ms 13.091 ms
5 tbr1-p012301.sffca.ip.att.net (12.123.13.173) 20.791 ms 17.732 ms 18.136 ms
6 ggr1-p360.sffca.ip.att.net (12.123.13.65) 12.108 ms 12.554 ms 11.226 ms
7 pos4-2.br5.sac1.alter.net (204.255.174.177) 15.145 ms 17.424 ms 15.81 ms
8 0.so-2-1-0.xl1.sac1.alter.net (152.63.52.226) 44.482 ms 15.913 ms 53.171 ms
9 0.so-3-0-0.tl1.sac1.alter.net (152.63.53.250) 26.841 ms 20.411 ms 18.384 ms
10 0.pos6-0.ir1.sac1.alter.net (152.63.0.113) 39.377 ms 16.728 ms 66.696 ms
11 so-7-0-0.ir1.sac2.alter.net (137.39.31.189) 22.209 ms 16.46 ms 19.591 ms
12 0.so-4-0-0.tr1.syd2.alter.net (210.80.48.190) 171.069 ms 170.61 ms 213.849 ms
13 so-3-2-0.xr1.syd2.alter.net (210.80.48.134) 169.922 ms 173.37 ms 172.177 ms
14 so-0-0-0.xr1.bne1.alter.net (210.80.33.2) 186.918 ms 184.403 ms 187.192 ms
15 411.atm8-0-0.gw2.bne1.alter.net (210.80.32.54) 193.371 ms 191.468 ms 197.5 ms
16 webcentral1-bne-gw.aspac.customer.alter.net (203.166.92.74) 188.839 ms 183.882 ms 187.751 ms
17 gi0-2-6.xr3.wic.server-web.com (203.147.255.123) 190.56 ms 194.44 ms 189.978 ms
18 gi0-0.xr3.bne.server-web.com (203.147.255.233) 196.227 ms 204.541 ms 197.031 ms
19 vl5.mls1.bne.server-web.com (203.147.255.45) 197.541 ms 185.108 ms 185.697 ms
20 bne606d.server-web.com (202.139.232.71) 197.626 ms 190.908 ms 192.465 ms

decryption
16th August 2004, 10:41 AM
Internode's Advisories List:
http://cgi.internode.on.net/advisories/list.html

Disko
16th August 2004, 10:45 AM
yeah, i looked at the advisories list...

Doesn't seem to be anything affecting adelaide right now apart from that telstra thing from last week which didn't have any impact here. I've heard that my home connection works fine at the moment as well...

I've done a restart, and that didn't fix anything. Going by those traceroute's it seems to be a problem outside of my office anyway.

decryption
16th August 2004, 10:48 AM
Hmm, well I'd ring up Internode's help desk (they actually help) and let them know. Maybe they can investigate further.

Disko
16th August 2004, 11:03 AM
Yep. waiting on a call back right now. :)

Disko
16th August 2004, 01:31 PM
Well, i've called internode and they didn't have much of an idea either. :/

I emailed them some of my traceroute results from around the web, and am waiting on a reply. Apologies anyone on my IM lists - they just wont stay connected.

Disko
17th August 2004, 09:55 AM
After a day of 1/2 internet, it seems to have fixed itself. Oh well - i guess i'll never know what the problem was.