Best practice is to host the status page on completely separate infrastructure. This adds a lot of operational overhead often seen as disproportionately low benefit relative to the ongoing effort to maintain, until rare events like this actually happen.
Because hosting your own status page seems like a fine idea until your service goes down and 1 million people come to figure out what's wrong or even worse, just lose the entire status page along with your infrastructure.
