There was internal loss, but it was the combo of these: > resulted in announcing some Google Cloud Platform IP addresses from a single point of presence in the

There was internal loss, but it was the combo of these: > resulted in announcing some Google Cloud Platform IP addresses from a single point of presence in the southwestern US. > not yet configured to handle Cloud Platform traffic and applied an overly-restrictive packet filter. that caused the real pain. Other traffic that ended up in the Southwest would have routed crazily, but wouldn't get stopped (filter). If it had just been a route thing for GCE (and related services) we would have just seen slowdown, etc. like any other routing mistake. Disclosure (and Disclaimer): I work on Compute Engine, but I'm not on our networking teams.