~~~ Forum Announcement - Everyone with an @home.com address - WE NEED YOUR HELP! ~~~

[Justin]

Here's a quote from the catalog.com ( a big webhosting company ) message board.



<< The network problems have been due to problems with the @home network on all occassions this week. The first time it went down on 10/31 was due to Cox upgrading the Sonnet Ring. As it was explained to me by our network engineers BGP did not take over because our routers were still able to ping the @home router. This is what Cox had to say &quot; but the BGP session between you and me is fine. And the BGP session between me and @Home is fine. It's that the advertisement into @Home's core is getting lost somewhere, but the BGP between you and me doesn't know that since it's interface-state driven.&quot; The second instance on 10/31 was Cox upgrading the Sonnet Ring once more. We have contacted Cox about these unacceptable downtimes. Cox will be bringing in a CISCO technician to examine their setup and optimize it to keep this from happening in the future.
>>



Maybe that'll explain it a bit more.

 

[cgclausen]

@home has been having trouble with their e-mail lately it has been up and down a lot recently.

EDIT: I seem to be receiving subscription updates just fine.

 

[skemlawn]

I have lots of probs with my @home email server too.

ttt

 

[reitz]

^

Someone, please, explain to me why anyone should consider signing up for @home service.

 

[ChrichtonsGirl]

Because I have a choice between crap 56K dial-up and cable, and I choose something faster than the 26K I averaged while on dial-up. We don't have any other choices where I live. I love paying $40 a month for such crap service, but I just don't have any other option yet.

 

[Poontos]

I think @Home speed is about the only reason to switch from dialup to cable.

 

[Adul]

I am glad I purchased my own dowmain. I can use my own e-mail account has back up. I been having problems too. Slow mail delivery.

 

[SuperGroove]

Has this been resolved yet?

Paul