3 ms·
Hosting your status page on the same infrastructure it is reporting on is the most idiotic thing a service can do.
by paxys 6y ago
Hosting your status page on the same infrastructure it is reporting on is the most idiotic thing a service can do.
- macintux 6y agoIt's tough, though. The PR embarrassment of hosting your Google Cloud status page on AWS, say, would be substantial.
- dilyevsky 6y agoI’m sure google can afford some colo space (probably would be cheaper too)
- macintux 6y agoSure, 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.
- closeparen 6y agoA separate failure domain / uncorrelated failure can be more important than the absolute rate of failure.
- dilyevsky 6y agoImo for simple deployment colo with a major provider (equinix, coresite, etc) and redundant transit beats any cloud on reliability hands down
- jeffbee 6y agoHow 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?
- dilyevsky 6y agoI honestly have no idea, hope they do. My point is aws is not the only alternative (and not even the best one) for setting this up.
- dylan604 6y agoMakes me think of a calculus word problem: As the things Google cannot afford approaches 0...
- deleted 6y ago[deleted]
- tpmx 6y agoSeems 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 6y agoYou're right, I'm using 8.8.8.8.