[30978] in North American Network Operators' Group
Re: Ameritech Service Quality Report
daemon@ATHENA.MIT.EDU (Kevin Day)
Sun Sep 3 12:58:44 2000
From: Kevin Day <toasty@temphost.dragondata.com>
Message-Id: <200009031657.LAA87622@temphost.dragondata.com>
To: billf@chimesnet.com (Bill Fumerola)
Date: Sun, 3 Sep 2000 11:57:41 -0500 (CDT)
Cc: msa@samurai.sfo.dead-dog.com (Majdi S. Abbas), nanog@merit.edu
In-Reply-To: <20000903124735.Q33771@jade.chc-chimes.com> from "Bill Fumerola" at Sep 03, 2000 12:47:35 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu
> > > What I find interesting isn't Ameritech's long repair times, but how
> > > do providers promise 4 hour repair times when the dominant local loop
> > > provider takes over a day to fix something on a good day.
> >
> > You're presuming they answer the phone.
> >
> [... all too familiar story of ameritech sucking deleted ...]
> >
> > Ameritech repair is useless. While living and working in
> > Michigan, I frequently had to go to the PSC over stupid issues
> > Ameritech should have been able to resolve quickly.
>
> Not to turn this thread into a Ameritech old war stories (I've got
> 'em though...), but...
>
> I plan either attending the one public commission meeting nearest to me
> eor at least writing the commission at the address provided from Sean's
> URL, and I'd encourage other Michiganders[1] who have been screwed over
> to do so as well.
>
If anyone here in Illinois is interested in doing something like this for
Ameritech, I'd be interested in joining up.
I've had T1's down for WEEKS, and am currently down because of a missed
install date after we moved. They told me the lines were up, we packed up,
moved, then found out "Oops, we didn't actually finish the install.".
-- Kevin
