as15169

This post costs information about Google’s plan to stop peering via route servers as well as possible speculation around why they are doing that.

This post analyses Google Cloud routing tiers and how they relate in the BGP world

I am in Bangalore for two days. While there are many things packed into these two days short schedule, one of the most exciting ones is Google Global Network India Innovation Summit. While Google has presented across various events in past talking about their AS15169 backbone, this is the first summit where they are covering it in detail and that too with the Indian context! Must say that I find AS15169 quite fascinating on the BGP side of things.

Back in 2017 Google shared details about Espresso which is their SDN solution for scaling up their routing. Saw this fascinating presentation from Google at SIGCOMM 2017. This blog post covers it in detail besides the talk. Key design principles for their routing platform Hierarchical control plane consisting of both global as well as local control. Global takes care of overall traffic flow, inputs coming from performance metric etc while local take care of failure of BGP sessions, port/device failure etc.

Railtel (the telecom arm of Indian railways) is running free wifi hotspots across the country in collaboration with Google. It’s there since last two years and started with the MoU between Railtel and Google (news here) back in 2015. Fast forward to 2018 - the free wifi project railway stations seems to be doing quite well with so many users using it. The project covers 361 stations and is expected to reach it’s target of 400 stations soon.