"Hmmmm, that's interesting," I said to myself. Soooo, then I tried to load the webpage itself. No dice. "What's going on here?" (I said to myself once again.)
So off I went to the blog of Digg to see if Kevin Rose had posted any news. Low and behold, I was met with zip, zilch, zero.
So, then I decided to ping the site and see if I even got a response. You can do it too if you like. Just hit START in windows, then type "ping" and then the IP address you are pinging. A ping will tell you how much time it takes for one packet of information to be sent and bounce back. Here's what I got when I pinged Digg.com (184.108.40.206)
Ping #1: * [No response]
Ping #2: * [No response]
Ping #3: * [No response]
Ping #4: * [No response]
That's not a good sign, no, not at all. I did find out
some interesting information
regarding Digg.com's IP address though. Here it is verbatim
IP address: 220.127.116.11
Reverse DNS: www.digg.com.
Reverse DNS authenticity: [Unknown]
ASN Name: REVISION3
IP range connectivity: 1
Registrar (per ASN): ARIN
Country (per IP registrar): US [United States]
Country Currency: USD [United States Dollars]
Country IP Range: 18.104.22.168 to 22.214.171.124
Country fraud profile: Normal
City (per outside source): Santa Monica, California
Private (internal) IP? No
IP address registrar: whois.arin.net
Known Proxy? No
Link for WHOIS: 126.96.36.199
So, no Digg for anyone this morning.
I'll keep you posted when something changes.