[1317] in North American Network Operators' Group
Re: Sprint Service Problems
daemon@ATHENA.MIT.EDU (Justin Newton)
Tue Dec 19 15:46:59 1995
Date: Tue, 19 Dec 1995 15:36:32 -0500 (EST)
From: Justin Newton <justin@rainbow.dgsys.com>
To: dlewis@Teir.COM
cc: nanog@merit.edu
In-Reply-To: <9511198193.AA819396459@ccgateva.teir.com>
I see either a routing loop or a wonderful !h (no route to host) on at
least a daily basis when going through sprint. I find it particularly
amazing that this never happens once I get into the MCI network or ANS or
etc etc (Well, ok it happens every few months from what I can see).
Right now the most frequent complaint about our service is Sprint f*cking
up. I am looking forward to Jan 2 when I switch companies and I won't
have to deal with Sprint anymore. (We're going right into MAE-East so
any screw ups will either be mine or will only effect traffic to the one
provider thats down and not everyone). Sprint and Net-99 should get
together sometime so that they can build a slow, unstable backbone, they
each seem to have mastered only one of the two.
On Tue, 19 Dec 1995 dlewis@Teir.COM wrote:
> Date: Tue, 19 Dec 95 10:04:42 EST
> From: dlewis@Teir.COM
> Cc: nanog@merit.edu
> Subject: Sprint Service Problems
>
>
> 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
> 9 sl-dc-6-F0/0.sprintlink.net (144.228.20.6) 16 msec 20 msec 16 msec
> 10 sl-dc-8-F0/0.sprintlink.net (144.228.20.8) 24 msec 16 msec 12 msec
> 11 sl-dc-6-F0/0.sprintlink.net (144.228.20.6) 16 msec 16 msec 16 msec
> 12 sl-dc-8-F0/0.sprintlink.net (144.228.20.8) 12 msec 20 msec 12 msec
> 13 sl-dc-6-F0/0.sprintlink.net (144.228.20.6) 12 msec 16 msec 16 msec
> 14 sl-dc-8-F0/0.sprintlink.net (144.228.20.8) 20 msec 24 msec 16 msec
> 15 sl-dc-6-F0/0.sprintlink.net (144.228.20.6) 16 msec 16 msec 20 msec
> 16 sl-dc-8-F0/0.sprintlink.net (144.228.20.8) 16 msec 20 msec 16 msec
> 17 sl-dc-6-F0/0.sprintlink.net (144.228.20.6) 16 msec 20 msec 16 msec
> 18 sl-dc-8-F0/0.sprintlink.net (144.228.20.8) 16 msec 16 msec 16 msec
> 19 sl-dc-6-F0/0.sprintlink.net (144.228.20.6) 16 msec 12 msec 16 msec
> 20 sl-dc-8-F0/0.sprintlink.net (144.228.20.8) 16 msec 20 msec 16 msec
> 21 sl-dc-6-F0/0.sprintlink.net (144.228.20.6) 20 msec 16 msec 16 msec
> 22 sl-dc-8-F0/0.sprintlink.net (144.228.20.8) 16 msec 16 msec 12 msec
> 23 sl-dc-6-F0/0.sprintlink.net (144.228.20.6) 20 msec 16 msec 16 msec
> 24 sl-dc-8-F0/0.sprintlink.net (144.228.20.8) 20 msec 28 msec 20 msec
> 25 sl-dc-6-F0/0.sprintlink.net (144.228.20.6) 16 msec 16 msec 16 msec
> 26 sl-dc-8-F0/0.sprintlink.net (144.228.20.8) 12 msec 12 msec 16 msec
> 27 sl-dc-6-F0/0.sprintlink.net (144.228.20.6) 20 msec 16 msec 16 msec
> 28 sl-dc-8-F0/0.sprintlink.net (144.228.20.8) 24 msec 16 msec 12 msec
> 29 sl-dc-6-F0/0.sprintlink.net (144.228.20.6) 16 msec 16 msec 16 msec
> 30 sl-dc-8-F0/0.sprintlink.net (144.228.20.8) 16 msec 20 msec 24 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
>
