[72167] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Peering point speed publicly available?

daemon@ATHENA.MIT.EDU (Tony Li)
Thu Jul 1 20:58:14 2004

In-Reply-To: <40C1034EE7C07D4587AE1F665D1B7E88013B08D9@gallatin.UPSTREAM.CUTTHROATCOM.COM>
Cc: <erik@myevilempire.net>, <nanog@merit.edu>,
	<network.support@oati.net>
From: Tony Li <tony.li@tony.li>
Date: Thu, 1 Jul 2004 18:02:06 -0700
To: "Cody Lerum" <clerum@transaria.com>
Errors-To: owner-nanog-outgoing@merit.edu



Is it really important to know the link speeds?  What good does it do=20
without knowing
about the loading on those links?

I would MUCH rather have an empty T1 than have to contend with a very=20
oversubscribed OC-768.

Tony



On Jul 1, 2004, at 5:25 PM, Cody Lerum wrote:

> DNS can sometimes give you a hint
> =A0
> [my nets snipped]
> =A04 t3-1-2-0.ar2.SEA1.gblx.net (64.211.206.113)=A0 20.436 ms=A0 =
18.309 ms=A0=20
> 17.605 ms=A0=A0 <------------DS3
>  =A05=A0 so1-0-0-2488M.ar4.SEA1.gblx.net (67.17.71.210)=A0 17.607 ms=A0 =
16.982=20
> ms=A0 16.971 ms=A0 <-----OC-48
> =A06=A0 p3-3.IR1.Seattle-WA.us.xo.net (206.111.7.5)=A0 17.864 ms=A0 =
19.491 ms=A0=20
> 17.181 ms
> =A07=A0 p5-1-0-3.RAR1.Seattle-WA.us.xo.net (65.106.0.197)=A0 17.723 =
ms=A0=20
> 17.632 ms=A0 19.045 ms
> =A08=A0 65.106.0.50 (65.106.0.50)=A0 38.133 ms=A0 39.197 ms=A0 49.961 =
ms=A0=A0=A0=A0=20
> MPLS Label=3D101549 CoS=3D0 TTL=3D1 S=3D1
> =A09=A0 p0-0-0d0.RAR1.SanJose-CA.us.xo.net (65.106.1.61)=A0 37.669 ms=A0=
=20
> 38.572 ms=A0 36.517 ms
> 10=A0 p7-0.DCR1.DC-SanJose-CA.us.xo.net (65.106.2.146)=A0 37.830 ms=A0=20=

> 36.524 ms=A0 37.743 ms
> 11=A0 ge1-1.CDR2.DC-SanJose-CA.us.xo.net (209.220.168.10)=A0 38.428 =
ms=A0=20
> 38.050 ms=A0 37.179 ms <-----Gig Ethernet
> 12=A0 205.158.6.100.ptr.us.xo.net (205.158.6.100)=A0 40.179 ms=A0 =
39.784 ms=A0=20
> 39.444 ms
> 13=A0 x218.cd9e6c.sj.concentric.net (205.158.108.218)=A0 39.188 ms=A0 =
39.723=20
> ms=A0 39.895 ms
> =A0
> However MPLS hidden hops may hide internal paths, and any connection=20=

> may be limited to slower than its line rate, and dns entries may be=20
> old....
> =A0
> It's not publicly available at one source that I'm aware of, and if=20
> there is they don't have my info.
> =A0
> -C
> From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf=20=

> Of Erik Amundson
> Sent: Thursday, July 01, 2004 6:10 PM
> To: nanog@merit.edu
> Cc: network.support@oati.net
> Subject: Peering point speed publicly available?
>
>
> NANOG,
>
> =A0
>
> I have a question regarding information on my ISP=92s peering=20
> relationships.=A0 Are the speeds of some or all peering relationships=20=

> public knowledge, and if so, where can I find this?=A0 By speed, I =
mean=20
> bandwidth (DS3, OC3, 100Mbps, 1Gbps, etc.).=A0 I am trying to transfer=20=

> large stuff from my AS, through my ISP, through another ISP, to=20
> another AS, and I=92m wondering how fast the peering point is between=20=

> the ISPs.=A0 I=92m working with my provider to get this information as =
we=20
> speak, but I=92m wondering if it=92s available publicly anywhere.=A0 =
If it=20
> were, this could be one way to evaluate providers in the future, I=20
> guess=85
>
> =A0
>
> Erik Amundson
> A+, N+, CCNA, CCNP
> IT and Network=A0Manager
> Open Access Technology Int'l, Inc.
> Phone (763) 201-2005
> Fax (763) 553-2813
>  mailto:erik.amundson@oati.net
>
>  =A0


home help back first fref pref prev next nref lref last post