Re: Amazon peering peeps on the list?

We had to do the same, a ticket and issue moved along quickly and a CO- worker had the peers up quickly. On Fri, Mar 9, 2018 at 9:16 AM Jason Kuehl wrote: > The better way to go ahead and get a hold of Amazon for peering issues is > to open a ticket with them via AWS

MANRS IXP Webinar: Tuesday, 13 March

Hail NANOGers! If you operate an IX in North America, this message is for you. (I'm passing it along on behalf of my former colleagues at the Internet Society.) Hope to "see" you on the webinar this Tuesday! ——— Hi, The MANRS IXP Partnership program is designed to invite and encourage

Re: Zayo zColo Xcon Pricing

On 3/7/18 9:00 AM, Ian Mock wrote: Everything is negotiable. NRC on a cross-connect is ridiculous. The cost to run should be made up with the amount they're charging monthly. I wouldn't pay more than $200/mo for copper. Actually, as a reflection of the provider's cost, NRC for a cross-connect

Weekly Routing Table Report

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG, IRNOG and the RIPE Routing WG. Daily listings are sent to

Re: Amazon peering peeps on the list?

The better way to go ahead and get a hold of Amazon for peering issues is to open a ticket with them via AWS account with business support. This is how I resolved issues with peering in the past. On Mar 9, 2018 8:27 AM, "Joe Nelson" wrote: > I've all but given up on

Re: BCP 38 addendum

Le 2018-03-07 16:19, Saku Ytti a écrit : Hey, How would this work? ISP1--ISP2---ISP3 || +---ISP4-+ In case poor rendering ISP1 connects to ISP2, ISP4 and ISP3 connects to ISP2, ISP4 - ISP3 receives ISP1 prefixes via ISP[24] - ISP3 advertises its prefix out

Re: Amazon peering peeps on the list?

I've all but given up on trying to get a response from peer...@amazon.com. If you do end up getting a contact, please share. On Wed, Mar 7, 2018 at 8:19 PM, Mike Lyon wrote: > Anyone on the list from Amazon peering? Have sent multiple emails to > peer...@amazon.com over the

Re: Zayo zColo Xcon Pricing

Everything is negotiable. NRC on a cross-connect is ridiculous. The cost to run should be made up with the amount they're charging monthly. I wouldn't pay more than $200/mo for copper. Ian Mock On Wed, Mar 7, 2018 at 9:10 AM, James Laszko wrote: > One of our colo’s in

Looking for a network abuse contact at CenturyLink

I know, it's a big place. I'd like to talk about something I'm seeing from your networks and see if you agree on what it could be. This includes legacy Qwest, CenturyTel, etc. I could list ASNs but it's kind of a long list, as you'd expect :) Thank you, and sorry for the noise. -- Bill Weiss

Google

I'm having a problem with some Google services that seems to be related to our public IP block. Anyone have a contact there that could check the IP block against any sort of google black list? Thanks Daniel Temple WISP Administrator CMB Systems, Inc 92-1 Hwy 64 West Cashiers, NC 28717