[32761] in North American Network Operators' Group
Re: Alter.net and Verio peering in Sacramento?
daemon@ATHENA.MIT.EDU (john heasley)
Mon Dec 11 16:48:55 2000
Date: Mon, 11 Dec 2000 13:44:45 -0800
From: john heasley <heas@shrubbery.net>
To: Roeland Meyer <rmeyer@mhsc.com>
Cc: "'Randy Bush'" <randy@psg.com>,
Mathew Butler <mbutler@tonbu.com>,
"'nanog@merit.edu'" <nanog@merit.edu>, noc@verio.net
Message-ID: <20001211134445.T4441@shrubbery.net>
Reply-To: noc@verio.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9DC8BBAD4FF100408FC7D18D1F0922869AE9@condor.mhsc.com>; from rmeyer@mhsc.com on Mon, Dec 11, 2000 at 01:28:41PM -0800
Errors-To: owner-nanog-outgoing@merit.edu
> > > Heya, I'm getting a huge jump in ping times from alter.net
> > to Verio in what
> > > appears to be Sacramento:
> >
> > horrifying that neither of these providers don't have nocs,
> > eh? sheesh!
> >
> > randy
>
>
> Let's see, applying De Morgan's :
>
> randy: horrifying that these providers have nocs, eh?
>
> Boy, that's probably close to what he really meant <g>.
thanks, we all appreciate the content-free update(s).
matthew,
LSR traceroute seems to indicate the issue is between verio and
sprint. the path is assym.
10 p4-4-2.r02.sttlwa01.us.bb.verio.net (129.250.3.37) 27.260 ms 27.855 ms 27.835 ms
11 sl-gw11-sea-1-1.sprintlink.net (144.232.236.1) 305.753 ms 309.921 ms 302.746 ms
noc@verio.net gratuitiously Cc'd.