And not just the ones that that backend was handling, but also some % of the overall traffic for re-balancing.
The degree of connection affinity from the ECMP is limited, and there's no "reliance" on it. If a connection flip-flopped between two or more load balancers, there would be no drops, thanks to the consistent fashion.
Internal use (2011) http://www.pcworld.com/article/245848/usenix_google_deploys_...
Internal and some datacentres (2009) http://www.networkworld.com/article/2238936/lan-wan/google-a...
Backbone dual stack (2010) https://www.nanog.org/meetings/nanog49/presentations/IPv6atG...
Facebook internal ipv6 http://www.internetsociety.org/deploy360/wp-content/uploads/...
[1] https://cloudplatform.googleblog.com/2014/11/cloudsql-instan...
[2] https://code.google.com/p/google-compute-engine/issues/detai...
As an aside, I couldn't help noticing these lines on adjacent pages:
> Maglev has been serving Google’s traffic since 2008. It has sustained the rapid global growth of Google services, and it also provides network load balancing for Google Cloud Platform.
> Maglev handles both IPv4 and IPv6 traffic, and all the discussion below applies equally to both.
In that case, any chance GCE will be getting IPv6 support soon? ;)