Amazon Peering

Mon Jan 28 23:32:45 UTC 2019

I also saw sessions come up this weekend, no routes yet though.

On Mon, Jan 28, 2019 at 4:56 PM Tom Beecher <beecher at beecher.cc> wrote:

> Mike-
>
> Definitely moving forward now. Someone from Amazon was working with my
> peering group and things started coming up this weekend, so it seems like
> they're catching up pretty good now.
>
> On Thu, Jan 24, 2019 at 2:45 PM Mike Hammett <nanog at ics-il.net> wrote:
>
>> Let us know your success as well. I'll hold off following up on my
>> requests until I see that other people are successful. I don't want to
>> contribute to flooding them with requests.
>>
>>
>>
>> -----
>> Mike Hammett
>> Intelligent Computing Solutions
>> http://www.ics-il.com
>>
>> Midwest-IX
>> http://www.midwest-ix.com
>>
>> ------------------------------
>> *From: *"Tom Beecher" <beecher at beecher.cc>
>> *To: *"Jason Lixfeld" <jason+nanog at lixfeld.ca>
>> *Cc: *"North American Network Operators' Group" <nanog at nanog.org>
>> *Sent: *Thursday, January 24, 2019 1:38:51 PM
>> *Subject: *Re: Amazon Peering
>>
>> Thanks Jason. I'll have my peering team take another crack at reaching
>> out and see what happens. Appreciate it!
>>
>> On Thu, Jan 24, 2019 at 2:21 PM Jason Lixfeld <jason+nanog at lixfeld.ca>
>> wrote:
>>
>>> We circled back with them yesterday on a request we made in late
>>> November where at the time they said they wouldn’t be turned up until 2019
>>> due to holiday network change freeze.
>>>
>>> They responded within about 4 hours, thanked us for our patience and
>>> understanding and said we should expect them to be turned up in about 6
>>> weeks, which is apparently their typical timing.
>>>
>>> On Jan 24, 2019, at 2:13 PM, Tom Beecher <beecher at beecher.cc> wrote:
>>>
>>> I hate to necro-thread , but has anyone seen any movement from Amazon on
>>> this? I just got a Strongly Worded Message about it, and according to my
>>> peering team , it's been radio silence for months.
>>>
>>>
>>> On Sat, Nov 24, 2018 at 12:32 PM JASON BOTHE via NANOG <nanog at nanog.org>
>>> wrote:
>>>
>>>> This is a note I received on Oct18 when checking on a peering request
>>>> submitted on Aug7..
>>>>
>>>> “Apologies for the delays here. We have temporarily frozen IX peering
>>>> as we revise some of our automation processes. I’m hopeful this will be
>>>> unblocked by early November. Thank you for your continued patience.”
>>>>
>>>> On Nov 24, 2018, at 10:59, Darin Steffl <darin.steffl at mnwifi.com>
>>>> wrote:
>>>>
>>>> It seems wasteful for Amazon to connect to an IX but then ignore
>>>> peering requests for a year.
>>>>
>>>> They have 40G of connectivity but are unresponsive. I'll try emailing
>>>> all the other contacts listed in peeringdb.
>>>>
>>>> Thanks
>>>>
>>>> On Sat, Nov 24, 2018, 10:38 AM Mike Hammett <nanog at ics-il.net wrote:
>>>>
>>>>> I've e-mailed my contacts there a couple times on people's behalf. No
>>>>> response yet.
>>>>>
>>>>> It seems like a lot of organizations need 1 more person in their
>>>>> peering departments.
>>>>>
>>>>>
>>>>>
>>>>> -----
>>>>> Mike Hammett
>>>>> Intelligent Computing Solutions
>>>>> http://www.ics-il.com
>>>>>
>>>>> Midwest-IX
>>>>> http://www.midwest-ix.com
>>>>>
>>>>> ------------------------------
>>>>> *From: *"Darin Steffl" <darin.steffl at mnwifi.com>
>>>>> *To: *"North American Network Operators' Group" <nanog at nanog.org>
>>>>> *Sent: *Friday, November 23, 2018 10:21:51 PM
>>>>> *Subject: *Amazon Peering
>>>>>
>>>>> Hey all,
>>>>>
>>>>> Does anyone have a direct contact to get a peering session established
>>>>> with Amazon at an IX? I sent a peering request Dec 2017 and two more times
>>>>> this Sept and Nov with no response.
>>>>>
>>>>> I sent to peering at amazon.com and received one automated response back
>>>>> so I know they received my email but nothing since.
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Darin Steffl
>>>>> Minnesota WiFi
>>>>> www.mnwifi.com
>>>>> 507-634-WiFi
>>>>> <http://www.facebook.com/minnesotawifi> Like us on Facebook
>>>>> <http://www.facebook.com/minnesotawifi>
>>>>>
>>>>>
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190128/a1b480e7/attachment.html>