Mailing List Archive

Utah outage (fwd)
Anyone know what happened this time?
---------- Forwarded message ----------
Date: Tue, 21 Nov 1995 21:55:09 -0700 (MST)

To: cook@cookreport.com
Subject: Utah outage (fwd)

Forwarded message:
Re: Utah outage (fwd) [ In reply to ]
Re: Utah outage (fwd) [ In reply to ]
Chris -

Thanks for your note; you're right on the ball.

outage-request@sprint.net I believe typically will subscribe
anybody who's interested. There are several sizeable lists
which are on the exploder here, so adding more probably is a non-issue.

Why so many people want to see my rantings and ravings is
beyond me though. :-)

Sean.
Re: Utah outage (fwd) [ In reply to ]
Sean wrote:
> outage-request@sprint.net I believe typically will subscribe
>anybody who's interested. There are several sizeable lists
>which are on the exploder here, so adding more probably is a non-issue.

Make that:

To: majordomo@sprint.net

with message text:

subscribe outage

-- Walt
Re: Utah outage (fwd) [ In reply to ]
You know if Sprint is gutsy enough (maybe customer centered would be a
better word?) to do this, why can't MCI? I had private mail today from a
network manager at a major MCI customer lamenting that the MCI higher ups
refused to allow MCI to show their customers this courtesy (creation of an
MCI outtage list). Is this attitude part of what HWB was complaining about?

********************************************************************
Gordon Cook, Editor & Publisher Subscript.: Individ-ascii $85
The COOK Report on Internet Non Profit. $150
431 Greenway Ave, Ewing, NJ 08618 Small Corp & Gov't $200
(609) 882-2572 Corporate $350
Internet: cook@cookreport.com Corporate. Site Lic $650
Newly expanded COOK Report Web Pages http://pobox.com/cook/
********************************************************************


On Wed, 22 Nov 1995, Walter O. Haas wrote:

> Sean wrote:
> > outage-request@sprint.net I believe typically will subscribe
> >anybody who's interested. There are several sizeable lists
> >which are on the exploder here, so adding more probably is a non-issue.
>
> Make that:
>
> To: majordomo@sprint.net
>
> with message text:
>
> subscribe outage
>
> -- Walt
>
Re: Utah outage (fwd) [ In reply to ]
> You know if Sprint is gutsy enough (maybe customer centered would be a
> better word?) to do this, why can't MCI? I had private mail today from a
> network manager at a major MCI customer lamenting that the MCI higher ups
> refused to allow MCI to show their customers this courtesy (creation of an
> MCI outtage list). Is this attitude part of what HWB was complaining about?

i dont' think anyone at mci is refusing to do this. we've had many
customers and even non-customers ask for this and i've passed this on to
management. i do believe mci's provisioning group is working on making this
happen in the near future. it certainly is a good idea.

(these comments do not necessarily reflect those of mci)

-brett

> ********************************************************************
> Gordon Cook, Editor & Publisher Subscript.: Individ-ascii $85
> The COOK Report on Internet Non Profit. $150
> 431 Greenway Ave, Ewing, NJ 08618 Small Corp & Gov't $200
> (609) 882-2572 Corporate $350
> Internet: cook@cookreport.com Corporate. Site Lic $650
> Newly expanded COOK Report Web Pages http://pobox.com/cook/
> ********************************************************************
>
>
> On Wed, 22 Nov 1995, Walter O. Haas wrote:
>
> > Sean wrote:
> > > outage-request@sprint.net I believe typically will subscribe
> > >anybody who's interested. There are several sizeable lists
> > >which are on the exploder here, so adding more probably is a non-issue.
> >
> > Make that:
> >
> > To: majordomo@sprint.net
> >
> > with message text:
> >
> > subscribe outage
> >
> > -- Walt
> >
Re: Utah outage (fwd) [ In reply to ]
>You know if Sprint is gutsy enough (maybe customer centered would be a
>better word?) to do this, why can't MCI? I had private mail today from a
>network manager at a major MCI customer lamenting that the MCI higher ups
>refused to allow MCI to show their customers this courtesy (creation of an
>MCI outtage list). Is this attitude part of what HWB was complaining about?

Distributing such email is certainly gutsy/nice, and may be the right
thing for now, but in the long run it will not be the right thing,
unless you like to drown in email. Gordon, say you connect to a random
location X across the country. As a plain user. You perceive a problem
(packet loss, connection drop, whatever). You may not even know what it
means in every detail, but you sure know there is a problem. In a
perfect world, what would you like to see? Send a query (email, phone,
finger, servqualityport, whatever) to your local service provider
"problem to reach X," and a kinda immediate (perhaps machine generated)
response "we know of a flood in Kansas, 90% likelihood the cause for
your problem. Will be fixed in 30 minutes by rerouting." Fine, you'd
think, I'll take a nap and try again in 45 minutes. What are you
getting instead? Standard is that a user has no clue of either the
cause for the problem, or a procedure for problem resolution. If I
send email to *any* (well, many, can't claim I have tried them all)
service provider I may on a good day get a response within several
hours. Typically saying they forwarded it to their service provider
(who may rarely respond to them, based on experience).

I *really* don't care who's fault a specific incident is. I would like
to know that people are aware of it and working on it, and an expected
repair time. Just like with lots of other things in life. That too
much to ask for as a user?
Re: Utah outage (fwd) [ In reply to ]
On Wed, 22 Nov 1995, Gordon Cook wrote:

> You know if Sprint is gutsy enough (maybe customer centered would be a
> better word?) to do this, why can't MCI? I had private mail today from a
> network manager at a major MCI customer lamenting that the MCI higher ups
> refused to allow MCI to show their customers this courtesy (creation of an
> MCI outtage list).

Since Sprint is likely to know something about MCI outages, then they can
report the details on the SPRINT outages list. If MCI would like to tell
their side of the story, they know what to do ;-)


Michael Dillon Voice: +1-604-546-8022
Memra Software Inc. Fax: +1-604-542-4130
http://www.memra.com E-mail: michael@memra.com