Hi Darin,

As Jay mentioned our caching presence at MSP is going away. 

Once our AS15169 peering became active with MICE route servers last week, we disabled peering from AS36040 to the MICE route servers. That gracefully shifted traffic from our caches to our AS15169 connection.

We still have some BGP sessions up on AS36040 but shortly those will be removed/changed to AS15169, as we remove AS36040 presence in MSP and at MICE.

One item to share, if not widely known, is that AS15169 serves all Google traffic, where as AS36040 is only cachable traffic. So, if you happen now to see more traffic from Google AS15169 compared to AS36040 that is likely the cause. 

This is explained here: https://peering.google.com/#/infrastructure

Thanks,
Dave

--

Dave Schwartz
Peering & Content Distribution
Google AS15169
+1-650-253-7615
+44 20 3820 9224


On Thu, Aug 8, 2019 at 4:48 PM Darin Steffl <[log in to unmask]> wrote:
Good to know. I thought maybe it would just be adding backbone while keeping a local cache at the same time.

I haven't noticed any problems at all though.

On Thu, Aug 8, 2019 at 6:43 PM Jay Hanke <[log in to unmask]> wrote:
Google is migrating to backbone only at MICE. The old caching as is going away. 

I did see a pretty good performance improvement on google drive and gmail after the new peering came up...

On Thu, Aug 8, 2019, 6:33 PM Darin Steffl <[log in to unmask]> wrote:
Question on how this changes where YouTube traffic comes from...

When we peered with 36040 before, it was mostly just YouTube traffic and it came from Google Cache nodes in MSP. Now that we turned down that peer and turned up 15169, it appears all traffic is now coming from Chicago instead of YouTube traffic staying local to MSP. I would expect YouTube to still come from local cache servers and other stuff like Gmail, Google Drive, etc. to come from Chicago.

Is this expected behavior as I was hoping we didn't lose the performance benefit of having video traffic coming direct from MSP instead of CHI. Is there any benefit to continuing to peer with 36040 for YouTube out of MSP?

Thanks

On Wed, Aug 7, 2019 at 8:47 PM [log in to unmask] <[log in to unmask]> wrote:

The interface was already graphing but I’ve just updated the weathermap now.

 

Thanks for the reminder,

anthony

 

signature_522626184

 

From: MICE Discuss <[log in to unmask]> on behalf of Darin Steffl <[log in to unmask]>
Reply-To: MICE Discuss <[log in to unmask]>
Date: Wednesday, August 7, 2019 at 5:32 PM
To: MICE Discuss <[log in to unmask]>
Subject: Re: [MICE-DISCUSS] Google AS15169 at MICE is up

 

Thanks for getting this turned up! I've submitted our request to migrate from 36040 to 15169.

 

I checked the traffic graphs and I don't see the 15169 port in there yet, just the existing 36040.

 

Is this supposed to be setup yet or does that typically follow a few days after the port is active?

 

Thanks

 

On Wed, Aug 7, 2019 at 4:56 PM Dave Schwartz <[log in to unmask]> wrote:

Hi MICE Participants,

 

Our 100G link from AS15169 to MICE is now live. We are peered and announcing/accepting routes from the route server. We welcome you to request public peering with us. 

 

Public peering with Google is encouraged as we do not announce all prefixes to our route server, only summary routes. We do however announce all Google prefixes on our direct IX peering sessions. When you peer with us you also will be able  to obtain access to the Google ISP Portal where you can manage your traffic, view your networks YouTube performance, among other features.

 

There are two ways to request public peering.

 

1. If you already have access to the Google ISP Portal please visit tickets --> request new IX interconnection and submit your details on your ASN and IP.

 

2. If you do not have access to the ISP Portal please visit isp.google.com/iwantpeering . On the form select Peering --> IX Peering and select Minneapolis from the dropdown. In the comments section please notate that you are part of MICE.

 

While we have paused IX peering due to IRR validation we will be reviewing MICE requests on a case by case basis for approval since we are changing ASNs. 

 

Please send me a direct message should you have any specific questions or concerns on your request.

 

Thanks,

Dave

 


--

 

Dave Schwartz

Peering & Content Distribution

Google AS15169

+1-650-253-7615

+44 20 3820 9224

 


To unsubscribe from the MICE-DISCUSS list, click the following link:
http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1


 

--

Darin Steffl

Minnesota WiFi

507-634-WiFi

 


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



--
Darin Steffl
Minnesota WiFi
507-634-WiFi


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



--
Darin Steffl
Minnesota WiFi
www.mnwifi.com
507-634-WiFi
 Like us on Facebook


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