SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : The *NEW* Frank Coluccio Technology Forum

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Hal Barnett who wrote (4095)10/18/2001 12:28:15 AM
From: Frank A. Coluccio  Read Replies (1) of 46821
 
Hi Hal, and thanks for weighing in on the VoIP thread, btw.

I must be dense this evening, more so than at other times, but at first I thought that this was a <user>@ATT.com thing (their dialup service), until I read in the article AT&T Broadband, and AT&T High Speed services, which then led me to believe they were referring to a <user>@Home thing. Do you or anyone else here know which? I've not read a boo about this on any of the ISP boards, btw. Then again, AT&T is not one to make public their problems there, either.

In the Southwest Cox's @home services manifested the same symptoms for a very long time, but now seem to have those resolved. Right, ftth (the person)?

Several years ago AT&T went through another one of these types of problems that principally affected the New England region, again, but that time it was a domain name services (DNS) problem when they acquired another SP's customer base, I believe. For some reason I want to say it was when they acquired IBM's IP network, but I'm not sure. Does anyone recall?
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext