[AusNOG] Peering with AWS through MegaIX

Chad Kelly chad at cpkws.com.au
Sun Jan 10 16:26:32 EST 2021


Hi I am not sure what some of you are on about with AWS not peering. 
The connectivity through Sydney IX is working fine from my end. 
Generally if your doing larger amounts of traffic and if you can afford it getting direct connectivity to AWS and Azure will work better anyway. 
But it can be organized to connect through both Vic and Syd IX to AWS. 
All the Microsoft stuff connects through NSW Edgeix and then through Vocus they MS and AWS tend to prefer transit now a days.

Traceroute is below. 
2    10 ms    10 ms    10 ms  103.23.104.5
  3    21 ms    21 ms    21 ms  103.23.104.233
  4    21 ms    21 ms    22 ms  bdr01-te-0-0-0-vl200.syd01.nsw.iperium.co [203.31.115.138]
  5    23 ms    21 ms    21 ms  as16509.nsw.ix.asn.au [218.100.52.9]
  6    23 ms    24 ms    23 ms  54.240.203.217
  7    22 ms    21 ms    21 ms  150.222.112.141
  8    24 ms    23 ms    23 ms  150.222.112.128
  9    23 ms    23 ms    23 ms  52.95.36.25
 10    23 ms    22 ms    22 ms  52.95.38.224
 11     *        *        *     Request timed out.
 12     *

Chad Kelly 
Manager 
CPK Web Services 
Phone 03 52730246
Web https://www.cpkws.com.au

-----Original Message-----
From: AusNOG <ausnog-bounces at lists.ausnog.net> On Behalf Of ausnog-request at lists.ausnog.net
Sent: Sunday, 10 January 2021 12:00 PM
To: ausnog at lists.ausnog.net
Subject: AusNOG Digest, Vol 107, Issue 4

Send AusNOG mailing list submissions to
	ausnog at lists.ausnog.net

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.ausnog.net/mailman/listinfo/ausnog
or, via email, send a message with subject or body 'help' to
	ausnog-request at lists.ausnog.net

You can reach the person managing the list at
	ausnog-owner at lists.ausnog.net

When replying, please edit your Subject line so it is more specific than "Re: Contents of AusNOG digest..."


Today's Topics:

   1. Re: Peer with AWS through MegaIX (Tim Sandy)


----------------------------------------------------------------------

Message: 1
Date: Sun, 10 Jan 2021 10:51:05 +1100
From: Tim Sandy <timsandy at gmail.com>
To: Paul Holmanskikh <ausnog at pkholm.com>
Cc: ausnog at lists.ausnog.net, Andres Miedzowicz
	<Andres.Miedzowicz at gsn.com.au>
Subject: Re: [AusNOG] Peer with AWS through MegaIX
Message-ID:
	<CALLtzKMQPG4E79ipO_cGjKyQ=gM2cKQU6DYc=hq8x+MXdm__1w at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Completely a guess, but; Maybe something to do with automatic detection and remediation of incorrectly redistributed routes? Would be much easier to do this if you have a definitive list of bilateral peers.

On topic - We have bilateral peering with AS16509 over both Mel and Syd MegaIX, as well as IXAus Vic and EquinixIX Syd. These have all been stood up in the past 6 months, but it was ~8+ months after my initial request. I emailed the contact on the peeringdb page, the email seems to have changed so it's probably not prudent to share the old address. Unless we're talking about a significant traffic volume, I think patience is the only approach.

On Sat, 9 Jan 2021 at 10:35, Paul Holmanskikh <ausnog at pkholm.com> wrote:

> On 2021-01-09 01:14, James Murphy wrote:
>
> Our BGP sessions to Amazon are up with 700+ prefixes received from them.
> So physically they still around.  Microsoft pulled yourself from RS on 
> Megaport some time ago, now AWS. It becomes a trend now. What are they 
> win by reducing connectivity?
>
>
> Amazon stopped appearing under Mega IX Melbourne and Sydney on 
> December 10th - something must have changed then.. (thanks PeeringDB 
> backups <http://data.caida.org/datasets/peeringdb> [1][2])
>
> They appear on the MegaIX looking glass, but with 0 advertised routes.
>
> Anyone know anything more?
>
>
> [1] curl+jq for December 9th:
> curl -s
> http://data.caida.org/datasets/peeringdb/2020/12/peeringdb_2_dump_2020
> _12_09.json
> | jq -cr '.net as $net | ($net.data | INDEX(.id)) as $netmap |
> .netixlan.data[] | select(.ix_id == 779 or .ix_id == 780) | 
> ["netixlan", .ix_id, .name, "net", .net_id, ($netmap[(.net_id | 
> tostring)] | .name)] | @tsv'
>
> [2] curl+jq for December 10th:
> curl -s
> http://data.caida.org/datasets/peeringdb/2020/12/peeringdb_2_dump_2020
> _12_10.json
> | jq -cr '.net as $net | ($net.data | INDEX(.id)) as $netmap |
> .netixlan.data[] | select(.ix_id == 779 or .ix_id == 780) | 
> ["netixlan", .ix_id, .name, "net", .net_id, ($netmap[(.net_id | 
> tostring)] | .name)] | @tsv'
>
>
> On 8 Jan 2021, at 11:46 pm, Paul Holmanskikh <ausnog at pkholm.com> wrote:
>
> Hi,
>
> What do you mean under AWS ? Amazon AS16509? We have bilateral peering 
> with Amazon in Megaport Sydney. But it was setup years ago. I can try 
> to dig out old mails, but I bet everything is changed since then.
>
> On 2020-12-31 10:57, Andres Miedzowicz wrote:
>
> Hello everyone,
>
>
> Is someone aware if AWS will do bilateral peering over MegaIX in 
> Melbourne and Sydney? I noticed they are not in the Route Server and 
> peeringdb.com doesn't show them in those exchanges but the MegaIX 
> looking glass does. If they do peering, do you have a contact email I 
> can write to? I tried with peering-apac at amazon.com but haven't received a response.
>
>
> I saw a thread about this from 2018 in AusNOG that would indicate that 
> they won't peer over MegaIX but maybe things have changed in a few years.
>
>
> Regards,
>
>
> Andres
>
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
>
> ---
> NEXON - I.T. FOR THE DYNAMIC BUSINESS
> Paul Holmanskikh
> Senior Network Engineer
>
> Disclaimer: The contents of this email represent my own views and not 
> necessarily the views of my employer 
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
>
> ---
> NEXON - I.T. FOR THE DYNAMIC BUSINESS
> Paul Holmanskikh
> Senior Network Engineer
>
> Disclaimer: The contents of this email represent my own views and not 
> necessarily the views of my employer 
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20210110/aeae7f5c/attachment-0001.html>

------------------------------

Subject: Digest Footer

_______________________________________________
AusNOG mailing list
AusNOG at lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog


------------------------------

End of AusNOG Digest, Vol 107, Issue 4
**************************************


More information about the AusNOG mailing list