Well, apparently it isn't up anymore. I lost my connection at around 10:00 AM EST this morning (Saturday). I am now using Comcast's "backup service". Netzero. Whoopee (don't you just love popup ads?). Ironically, the Excite@Home homepage (home.excite.com) is still up and running, though there is no new news on the news page.

With luck, @Home will be back up soon. If any of you cable guys do have service, say something. I am not sure as of yet whether @Home is down nationwide or just locally. For now, I guess I just have to live with 56K.

News flash- @Home is not down (for Comcast users in SE Mich, at least)! I was looking online using my 56K, and found a solution to the problem.

Apparently AT&T was not negotiating with @Home, and they shut down their servers. Comcast, however, is negotiating, and the Comcast DNS servers are still running. Now, as those of you with Comcast@Home in MI know, AT&T used to run the service in some parts of Oakland County. My guess is, @Home did not know or realize that the Royal Oak servers were no longer AT&T-run, and shut them down.

Now, for the solution: change the DNS server addresses from the AT&T DNS to the Comcast DNS. If you are experiencing problems go to Control Panel/Network and Select TCP/IP, and click properties. Go under the DNS tab, and remove your DNS Server addresses. They should be:

24.2.248.33 (or something close to that)

Change them to:

24.2.68.33 and
24.2.68.36

Your @Home connection should work fine now. Time for a return to cable speeds!

(note: as far as I know, this only works in for Comcast in SE Michigan)

Comcast @HOME in Indy is running STRONG. :D It seems to be going a lot faster than it was before. I'm still crossing my fingers and hoping for the best :p

Never had any downtime here in Ypsilanti, MI...of course, I've been running everything server-assigned since I started with cable...