Looking for a AS15169 Google contact to update their PeeringDB records

Rubens Kuhl rubensk at gmail.com
Thu Mar 14 04:02:30 UTC 2019


While I hope you get the contact you asked for, you can use IX.br
communities to manipulate how your route announcement reaches them or not,
so that even with the lack of other network cooperation, you might be able
to achieve your goals.


Rubens


On Thu, Mar 14, 2019 at 12:43 PM Siyuan Miao <aveline at misaka.io> wrote:

> Hi,
>
> We're noticed that PeeringDB records of AS15169 in IX.br (PTT.br) São
> Paulo is outdated.
>
> I've tried to contact AS15169 to update it via IX Session Turnup ticket
> and noc at google.com but didn't get a reasonable response.
>
> That's what I got from noc at google.com:
>
> > Dear Team,
> > Thank you for contacting the Google NOC, as 15169.
> >
> > With the details provided we were unable to identify the relevant link.
> >
> > Please provide following items to identify which session is impacted:
> >
> >  * Peering City
> >  * BGP peering ASNs, including your own AS
> >  * BGP peer IP addresses
> >
> > Thanks & Regards,
> > [redacted]
> >
> > Google Network Operation Center (GNOC) |noc at google.com |
> > [redacted]
>
> Can someone contact me off list about this issue?
>
> Regards,
> Siyuan Miao
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190314/d37faf5b/attachment.html>


More information about the NANOG mailing list