 |
 |
We're trying to track down specific reports. We have a local cache so I think that is masking most of the potential issues. One or two folks mentioned some Youtube buffering after being informed of a potential issue so it seems likely there is some impact, but I couldn't say with complete certainty that congestion through MICE is the cause.I did open a ticket with Google as well to see if they would make a specific recommendation or otherwise comment on their suggested course of action to minimize customer impact. We'll see what they say.We've needed an excuse to review how we are advertising our prefixes to Google anyway.Our interest was in taking a (semi) proactive stance to attempt to prioritize other sources until this issue is resolved.
Ben Wiechman
On Fri, Feb 24, 2017 at 8:54 PM, Andrew Hoyos <[log in to unmask]> wrote:
Ben, is Arvig seeing problems too?Seems like at this scale and number of complaints, Google should work their black magic to shed some traffic to different GGC nodes, rather than all of us having to actively try and coerce traffic elsewhere.There clearly seems to be an issue here, and Google has yet to ack.
--Andrew HoyosTo confirm what others have found to be effective.Are you advertising community 15169:13000 to the route servers, and on any direct peering sessions with AS36040?
Ben Wiechman
On Fri, Feb 24, 2017 at 3:29 PM, Mike Horwath <[log in to unmask]> wrote:
On Fri, Feb 24, 2017 at 10:38:43AM -0600, Andrew Hoyos wrote:
> > On Feb 24, 2017, at 10:26 AM, Mike Horwath <[log in to unmask]> wrote:
> >
> > On Fri, Feb 24, 2017 at 08:56:33AM -0600, Andrew Hoyos wrote:
> >> 36040 is a customer of HE.net in MSP, so you'd need to send those to
> >> HE as well if you peer with them or are a customer. Otherwise they
> >> will learn your prefixes that way too, sans communities.
> >
> > Why is a customer sending other peoples' routes into HE to then go
> > into the exchange?
>
> 36040 is a customer of HE.net. So, HE.net is sending them a full
> table or some subset (including their peers and customers), as
> expected.
I misread and now understand.
Thank you!
I had taken it the other way which was making no freakin' sense at all
in todays world of interconnectivity.
To unsubscribe from the MICE-DISCUSS list, click the following link:
http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
To unsubscribe from the MICE-DISCUSS list, click the following link:
http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
To unsubscribe from the MICE-DISCUSS list, click the following link:
http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
To unsubscribe from the MICE-DISCUSS list, click the following link:
http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1