The most obvious way to implement this is to host the status page with a competitor using completely independent infrastructure. Another trick which can be implemented is that if any part of the status page fails in some way it will just fail by showing the service as failed. So for example with todays fastly issue when the front end servers worked but the backend network had issues the frontends can be configured to show a status page with everything failing if they can not find the back end servers. This obviously does not work if there is any errors very early in the pipeline but at that point it is likely a problem with the clients network provieder anyway and the status page would be of no help.
Latest Answers