Is www.digg.com working for anyone.

Last time it worked for me was yesterday (last time i tried).

With Bigpond Cable. Sydney.

Can't ping it or anything, and no other sites i can find have anything relating to digg.com being down :S

Others i know are having problems accessing it.

Cheers,
Phil

.... same here. I'm with iiNet in Hobart.

Revision 3 is down too.

Queer.

Working here... iiNet Melbourne

Fine here.

Optus Cable.
Melbourne.

Read this.

Vegemite on Toast writes...

Read this.

Already have.

It does 2 hops and then nothing.
Stops at 10.140.224.1

And various people have had mixed results :s

Fine here, Adelaide.

Stops here for me

traceroute to digg.com (64.191.203.30), 30 hops max, 40 byte packets
1 172.18.112.37 (172.18.112.37) 38.903 ms 38.400 ms 37.568 ms
2 172.18.66.18 (172.18.66.18) 36.808 ms 36.559 ms 39.183 ms
3 cht-core-1.nsw.bigpond.net.au (61.9.195.7) 38.322 ms 38.951 ms 37.554 ms
4 TenGigabitEthernet4-1.chw44.Sydney­ .telstra.net (165.228.107.89) 37.790 ms 37.838 ms 36.912 ms
5 TenGigE0-1-0-0.chw-core2.Sydney.te­ lstra.net (203.50.20.129) 38.164 ms 38.268 ms 38.693 ms
6 10GigabitEthernet1-0.oxf-core1.Syd­ ney.telstra.net (203.50.6.2) 37.669 ms 38.383 ms 38.061 ms
7 10GigabitEthernet6-0.syd-core04.Sy­ dney.reach.com (203.50.13.34) 38.907 ms 38.865 ms 37.780 ms
8 i-5-0.syd-core02.net.reach.com (202.84.144.249) 38.063 ms 38.717 ms 37.375 ms
9 i-9-0.sydp-core01.net.reach.com (202.84.221.89) 38.247 ms 37.737 ms 38.969 ms
10 i-0-0.wil-core03.net.reach.com (202.84.143.209) 185.999 ms 191.044 ms 188.756 ms
11 i-4-1.wil03.net.reach.com (202.84.251.214) 219.262 ms 219.101 ms 218.770 ms
12 ge-6-21.car3.LosAngeles1.Level3.ne­ t (4.68.111.137) 223.811 ms 224.637 ms 226.491 ms
13 ae-2-52.bbr2.LosAngeles1.Level3.ne­ t (4.68.102.33) 221.494 ms 219.685 ms ae-2-56.bbr2.LosAngeles1.Level3.ne­ t (4.68.102.161) 225.209 ms
14 as-2-0.bbr2.SanJose1.Level3.net (4.68.128.157) 235.585 ms ae-0-0.bbr1.SanJose1.Level3.net (64.159.1.129) 241.548 ms 240.962 ms
15 ge-11-2.ipcolo1.SanJose1.Level3.ne­ t (4.68.123.169) 239.900 ms ge-7-1.ipcolo1.SanJose1.Level3.net­ (4.68.123.73) 231.473 ms ge-11-1.ipcolo1.SanJose1.Level3.ne­ t (4.68.123.105) 231.399 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *

Happy first post Deads!

Tracing route to digg.com [64.191.203.30]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms home.gateway [192.168.1.254]
2 17 ms 15 ms 15 ms nexthop.sa.ii.net [203.173.60.88]
3 16 ms 16 ms 15 ms gi0-1-700.ade-pipe-bdr1.ii.net [203.215.10.4]
4 44 ms 44 ms 44 ms gi0-14-0-3.syd-stl-core1.ii.net [203.215.20.70]

5 45 ms 45 ms 45 ms 202.139.19.37
6 202 ms 202 ms 202 ms 203.208.148.141
7 207 ms 205 ms 204 ms so4-2-0-622M.ar2.PAO2.gblx.net [208.50.13.185]
8 208 ms 206 ms 249 ms so2-1-0-2488M.ar1.SJC2.gblx.net [67.17.74.158]
9 * * * Request timed out.
10 208 ms 207 ms 210 ms digg.com [64.191.203.30]

Trace complete.

1 1 ms 1ms 1ms 192.168.0.1
2 14ms 13ms 9ms 10.140.224.1
3 * * * Request timed out

working here!

Tracing route to digg.com [64.191.203.30]
over a maximum of 30 hops:

1 * * * Request timed out.
2 37 ms 37 ms 37 ms dslgw-211.29.137.25.optusnet.com.a­ u [211.29.137
25]
3 38 ms 39 ms 40 ms mas4-vl600.gw.optusnet.com.au [211.29.137.2]
4 37 ms 41 ms 40 ms mas3-ge1-2.gw.optusnet.com.au [211.29.129.241]
5 186 ms 186 ms 187 ms 203.208.148.97
6 188 ms 199 ms 197 ms mzima.net.any2ix.crgwest.com [206.223.143.2]
7 196 ms 197 ms 199 ms eos1-20.cr02.sjc02.mzima.net [216.193.255.161]
8 197 ms 209 ms 199 ms xe1-0.cr01.sjc01.mzima.net [216.193.255.222]
9 198 ms 199 ms 199 ms ge4-0-0.br01.sjc01.mzima.net [64.235.224.122]
10 198 ms 197 ms 198 ms equinix-pri.revision3.com [206.223.117.76]
11 196 ms 195 ms 196 ms digg.com [64.191.203.30]

Trace complete.

no probs here, bundaberg, optusnet.

Just use duggmirror.com for now for those who can't access digg (although no good if all you wanted was the videos section)

Tracing route to digg.com [64.191.203.30]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 13 ms 13 ms 13 ms nexthop.tas.ii.net [203.173.62.88]
3 14 ms 14 ms 14 ms gi0-1-700.hba-pipe-bdr1.ii.net [203.215.13.8]
4 15 ms 14 ms 15 ms FastEthernet3-2.dav9.Hobart.telstr­ a.net [139.130
.25.45]
5 16 ms 15 ms 16 ms GigabitEthernet3-2.dav-core4.Hobar­ t.telstra.net
[203.50.109.5]
6 30 ms 30 ms 29 ms POS0-5-0-1.win-core1.Melbourne.tel­ stra.net [203.
50.76.25]
7 42 ms 43 ms 41 ms Bundle-Pos1.ken-core4.Sydney.telst­ ra.net [203.50
.6.21]
8 42 ms 41 ms 41 ms Port-Channel1.pad-gw2.Sydney.telst­ ra.net [203.50
.6.29]
9 42 ms 41 ms 42 ms 10GigabitEthernet2-0.sydp-core02.S­ ydney.reach.co
m [203.50.13.50]
10 41 ms 42 ms 40 ms i-9-0.sydp-core01.net.reach.com [202.84.221.89]

11 190 ms 188 ms 188 ms i-14-0.wil-core03.net.reach.com [202.84.143.246]

12 189 ms 189 ms 188 ms i-3-4.wil03.net.reach.com [202.84.251.162]
13 194 ms 195 ms 194 ms ge-6-20.car3.LosAngeles1.Level3.ne­ t [4.68.111.13
3]
14 189 ms 189 ms 188 ms ae-2-54.bbr2.LosAngeles1.Level3.ne­ t [4.68.102.97
]
15 202 ms 200 ms 201 ms as-2-0.bbr2.SanJose1.Level3.net [4.68.128.157]
16 203 ms 201 ms 201 ms ge-11-0.ipcolo1.SanJose1.Level3.ne­ t [4.68.123.41
]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

MickJT writes...

Just use duggmirror.com for now for those who can't access digg (although no good if all you wanted was the videos section)

lol Yeh i did want videos and the news.
Thanks for that idea, never thought about checking dugmirror

Hopefully whatever the problem is, it is fixed soon :s

Cheers,
Phil

Well philly, you could use kproxy.com or anonymouse.ws or something to access the videos section of digg.com

The site is sill down, been down since early yesterday for me.

I'm at a 'node hotspot, so I don't think I can trace

brian:~ sbolanos$ traceroute digg.com
traceroute to digg.com (64.191.203.30), 64 hops max, 40 byte packets
1 10.0.0.1 (10.0.0.1) 7.684 ms 7.557 ms 8.498 ms
2 10.193.83.1 (10.193.83.1) 5.190 ms 38.677 ms 5.075 ms
3 * * *
4 * * *
5 *^C

but I can browse it fine.

It's down for me, unless I use a proxy service to access it :\

Doesn't work from Hobart TAFE either:

Tracing route to digg.com [64.191.203.30]
over a maximum of 30 hops:

1 <1 ms 3 ms 3 ms 10.5.7.225
2 <1 ms <1 ms <1 ms 147.109.212.1
3 <1 ms <1 ms <1 ms 172.26.97.34
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
etc

Weird

Oww thanks, i was starting to worry i was the only person.

Anyone know what could be the cause of some of us not able to access it??

it seems like hobart and sydney cant access it

from melbourne with node

Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

Tracing route to digg.com [64.191.203.30]
over a maximum of 30 hops:

1 3 ms <1 ms <1 ms 192.168.1.254
2 19 ms 18 ms 19 ms loop0.lns2.mel4.internode.on.net [150.101.212.44
]
3 20 ms 18 ms 22 ms gi0-3.cor1.mel4.internode.on.net [150.101.212.57
]
4 217 ms 217 ms 219 ms pos2-3.bdr1.syd7.internode.on.net ­ [150.101.120.1
22]
5 215 ms 214 ms 215 ms pos4-0.bdr1.sjc2.internode.on.net ­ [203.16.213.45
]
6 247 ms 252 ms 253 ms eqix-peer.sjc01.mzima.net [206.223.116.62]
7 221 ms 217 ms 214 ms ge4-0-0.br01.sjc01.mzima.net [64.235.224.122]
8 216 ms 214 ms 215 ms equinix-pri.revision3.com [206.223.117.76]
9 217 ms 217 ms 220 ms digg.com [64.191.203.30]

Trace complete.

I can't access it either.

Bigpond Cable, Brisbane.

T©ßBù®LèiGh writes...

it seems like hobart and sydney cant access it

No problem here in Sydney on Optus ADSL ;)

Maybe they've changed something because Digg seemed to load alot quicker than usual from my connection...

Tracing route to digg.com [64.191.203.30]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 30 ms 25 ms 27 ms dslgw-211.29.137.25.optusnet.com.a­ u [211.29.137.25]
4 34 ms 32 ms 34 ms mas4-vl600.gw.optusnet.com.au [211.29.137.2]
5 25 ms 26 ms 26 ms mas3-ge9-3.gw.optusnet.com.au [211.29.129.249]
6 186 ms 184 ms 185 ms 203.208.191.5
7 184 ms 185 ms 184 ms 203.208.145.82
8 186 ms 185 ms 184 ms if-1-3.mcore4.LAA-LosAngeles.teleg­ lobe.net [216.6.85.17]
9 184 ms 185 ms 185 ms if-13-0.core1.SQN-SanJose.teleglob­ e.net [66.198.97.29]
10 182 ms 184 ms 185 ms if-13-0.core1.SQN-SanJose.teleglob­ e.net [66.198.97.29]
11 202 ms 321 ms 293 ms equinix-pri.revision3.com [206.223.117.76]
12 187 ms 185 ms 185 ms digg.com [64.191.203.30]

Trace complete.

Still down here. iiNet Hobart :(

I'm in Adelaide, with Bigpond, and can't access it.

Works fine for me TPG Adelaide

It is still down for me here in Adelaide on TLS Cable.

Could not get it yesterday either.

Cheers.

iiNet Sydney: working
Corporate network, Sydney: not working. (Telstra service, maybe?)

Working fine and dandy at Flinders Uni, Adelaide.

Not working for me. Bigpond Cable

-fronthouse- writes...

Not working for me. Bigpond Cable

Same here. I am in Bris.

Me too, Bigpond Cable Brisbane. Traceroute dies after:

ge-7-1.ipcolo1.SanJose1.Level3.net­ (4.68.123.73) 179.607 ms

My mother also told that certain parts of Neopets aren't working either.

Not working here for me at work, Telstra corporate internet in Perth.

Mine's working ok. Adam internet in adelaide.

Not working here on either BP ADSL or Telstra Corporate... Telstra blocking DIGG?

I got someone else to look up the IP address and couldn't even open that up....

no good on Telstra Internet, or bigpond internet, or telstra UTMS...

Who should be fixing this? Telstra?

I can't believe I haven't been able to browse digg for three days.

I can access it without any problem..

Can anyone using a telstra provider access it?

No Digg for me :-( Telstra cable Ashfield NSW.

I'm on iiNet ADSL2 and it doesn't work. But my trace routes mention telstra a bit.

This is fun. As I posted to a thread in the BigPond forum:
I can access Digg from both of my connections:
Telstra cable, 60.225 IP, Sydney
Internode ADSL, 59.167 IP, Sydney

HTTP is fine on both, and I can ping it from both, but traceroutes both die in San Jose. See this post if you want the traceroutes.

Hendikins writes...

HTTP is fine on both, and I can ping it from both, but traceroutes both die in San Jose.

Yes, that's because windows uses ICMP packets whilst Linux on the other hand uses UDP datagrams.

Some routers block ICMP packets.

I am happily Diggin' with AAPT Melbourne

MickJT writes...

Yes, that's because windows uses ICMP packets whilst Linux on the other hand uses UDP datagrams.

Some routers block ICMP packets.

Alas, no Windows to be found here :-)

Fine at home - Internode Hobart
No go at work (no, it's not blocked) - I think thats NetTas

Digg isn't working for me.

I'm with Telstra on Adsl.

But I just tried digg with a proxy out of sheer boredom, loaded the page :|

Our entire company are unable to access the site (same IP I guess), on Bigpond ADSL (Gosford).
Traceroute stops at San Jose, same as everyone else.
Ping doesn't work at all, though Digg.com may block pinging anyway.
None of the subsites seem to work either.
I have tested it at several locations, all with the same outcome, all with Telstra.
I have also contacted Telstra twice, and they are looking into it currently.
I have also contacted digg.com (through a proxy) and hopefully they are looking into it.

I have written an article about it at www.centralcoastlive.org/home, which will hopefully get some hits and sooner or later the right people will be aware of the problem.

its working on telstra internet now..

Digg and its subdomains are up and running again apparently, see here:
digg.com/tech_news/Digg_...stralia#c5608124

Yes, back up here.

Woot, what a way to end a friday :D

Shows you how much people can be effected, even though everyone should be able to access anything on the internet.

Should this thread not be in Telstra ISP?

I am confused.

©£ONeST@® writes...

Should this thread not be in Telstra ISP?

I am confused.

No because we originally were trying to determine which ISP's were effected, and then found others besides bigpond were also effected, as it wasn't on a local line possibly.