[195847] in North American Network Operators' Group

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

Re: IOS new versions and network load

daemon@ATHENA.MIT.EDU (Job Snijders)
Mon Sep 18 04:37:24 2017

X-Original-To: Nanog@nanog.org
Date: Mon, 18 Sep 2017 09:37:17 +0100
From: Job Snijders <job@ntt.net>
To: Christopher Morrow <morrowc.lists@gmail.com>
In-Reply-To: <CAL9jLaaJynd4OKSNS58jarOE+3VZiXUnRoLLg7zB+RakbVjPXQ@mail.gmail.com>
Cc: "Nanog@nanog.org" <Nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

On Mon, Sep 18, 2017 at 12:48:45AM -0400, Christopher Morrow wrote:
> On Sun, Sep 17, 2017 at 11:05 PM, JASON BOTHE <jbothe@me.com> wrote:
> > My best experience with Apple has been directly peering with them.
> > Definitely handles the update issue without putting strain on transit
> > links. Apple is very well connected.
> >
> > https://www.peeringdb.com/net/3554
>
> apple is AS714 though, right? or are they having the trucking company
> do their delivery of bits?

You may be shuffling the opaque peeringdb 'net_id' that is assigned to
each network with the ASN of such a network.

These entry points lead to the same information:

    https://www.peeringdb.com/asn/714
    https://as714.peeringdb.com/
    https://www.peeringdb.com/net/3554

Kind regards,

Job

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