[alexdumitru]

Everything Google-related is down for me, so I can't open that page.

[pentium10]

The issue started occurring intermittently at 08:26 US/Pacific. The issue is impacting Google’s Backbone network and may impact various services when accessing them from a different region or from the internet. Impacted services include Cloud Services (Workspace, Firebase, GCP) as well as other Google properties.

Connectivity within a zone should not be impacted.

Our engineering team has implemented a mitigation and is now monitoring the effectiveness of the change.

[paxys]

Hosting your status page on the same infrastructure it is reporting on is the most idiotic thing a service can do.

[tpmx]

Seems like the status page was on separate infra (I could access it while the GCP services were down), but Google Public DNS (8.8.8.8) was also down.

Perhaps alexdumitru was using 8.8.8.8?

[alexdumitru]

You're right, I'm using 8.8.8.8.

[macintux]

It's tough, though. The PR embarrassment of hosting your Google Cloud status page on AWS, say, would be substantial.

[dilyevsky]

I’m sure google can afford some colo space (probably would be cheaper too)

[dylan604]

Makes me think of a calculus word problem: As the things Google cannot afford approaches 0...

[macintux]

Sure, but what’s more likely to be reliable: GCP/AWS or a colo?

It’s also embarrassing (and can cause stress for your customers) when your status page is down.

[dilyevsky]

Imo for simple deployment colo with a major provider (equinix, coresite, etc) and redundant transit beats any cloud on reliability hands down

[jeffbee]

How do you know that there isn't a disaster plan under which Google routes requests for status.cloud.google.com to some other, non-Google host?

[closeparen]

A separate failure domain / uncorrelated failure can be more important than the absolute rate of failure.