A status page that survives the outage it is reporting
Hosted separately from everything it monitors, so the page your customers check is not sharing a failure domain with the thing that failed.
Why it works this way
A status page served from the infrastructure it reports on is the one page guaranteed to be down exactly when it matters. It is a familiar failure: the site is unreachable, customers go to check the status page, and it is unreachable for the same reason.
Outage continuity puts the customer-facing page somewhere else entirely. When your own systems are unreachable, visitors still get a page, and that page can carry the message you want them to read instead of a connection error.
This is a separate capability rather than something quietly bundled, because it solves a specific problem and not everybody has it. If your status page already lives away from your production stack, you do not need it.
What it costs
Those capabilities and everything they depend on come to $7/month.
Build the plan around it.
Add what you need, drop what you do not, and read the total before you buy.