Sprint traffic

If I may intrude...

(I'm not a member of NANOG, just an evesdropper..)

Does anyone have the email for the NOC @ sprint(link).

There seems to be "som'in screwwy" with traffic
about their system at Cheyenne. (But I'm no techie)

11:Received echo from ? [] in 610 msec.
12:Received echo from ? [] in 278 msec.
13:Received echo from ? [] in 2644 msec. (WOW!)
14:Received echo from ? [] in 312 msec.
15:Received echo from ? [] in 288 msec.
16:Received echo from ? [] in 397 msec.
17:Received echo from ? [] in 455 msec.
18:Received echo from ? [] in 320 msec.
19:Received echo from ? [] in 296 msec.
20:Received echo from ? [] in 363 msec.
21:Received echo from ? [] in 298 mse

Thanks in advance!

Richard Newcomb


Sprintlink's noc.



<from whois on sprintlink-dom>

   Alternate Contact:
      Sprint Network Info. & Support Center (SPRINT-NOC)
      (800) 669-8303

HOWEVER, if you are not a client, tell your provider. That will allow
equally technical people to talk and get things resolved as quickly as
possible. They are going to want to know what you did to get this

Just looking at it, and not knowing from where you are getting this, it
may be normal. Pings are a low priority for most hardware, and are subject
to being dropped.

Finally, this is a forum for discussing North American Network operations,
not operations within a provider. I would always suggest going to your
upstream provider first for operational difficulties. That is what you pay
them for.

network operations

The general lesson to be derived from this is to check whois
information first, then try the standard addresses documented in
and only if these fail, should you ask on the list.

Does everybody on this list support all the addresses in the above draft?

Michael Dillon - Internet & ISP Consulting
Memra Software Inc. - Fax: +1-250-546-3049
http://www.memra.com - E-mail: michael@memra.com

They weren't being dropped though, they were getting bounced back and
forth between two addresses. There was indeed a problem, but Sprint has
stabilized it and assumes it is fixed. The problem lasted from at least
2am PST early this morning until after noon today.

/* John */