[1313] in North American Network Operators' Group
Re: Sprint Service Problems
daemon@ATHENA.MIT.EDU (garlic@garlic.com)
Tue Dec 19 12:27:55 1995
From: garlic@garlic.com
Date: Tue, 19 Dec 1995 09:20:26 -0800
To: nanog@merit.edu
Its hard to determine where the problem was without further data. I can
tell you that UUNET's San Jose complex has crashed several times this
morning and that it is not an unusual occurance.
dlewis@Teir.COM wrote:
>
> Its days like this when I just love sprint:
>
> 8 sl-dc-8-F0/0.sprintlink.net (144.228.20.8) 12 msec 16 msec 12 msec
>....
>
> Sadly this is all too common of an occurrence. What is sprint doing to help keep
> problems like this from becoming chronic? Is it just me or is Sprint
> particularly bad about this?
>
> I guess the reason that I'm bringing this up here is I wonder if these types of
> problems are the result of any particular choices Sprint made in their
> design.... If so I would like to know how to avoid them. :)
>
> I know that hardware fails and things break, but Sprint has had (in my opinion)
> more than it's share of problems.
>
> -D
>
> Darrel Lewis
> Network Engineer
> Thomson Electronic Information Resources
> dlewis@teir.com