Skip to content
Error codes · Status pages & incidents

RU-5011: Last status page cannot be deleted

Every account keeps at least one status page, because incidents, maintenance, subscribers and the badge all hang off one. The delete was refused rather than leaving the account with none.

On the wire

Ships with HTTP status 409, carrying "code": "RU-5011" in the response body alongside the human-readable error message. Existing fields are never replaced by the code: it is additive.

Common causes

  • Destroying every status page in an infrastructure-as-code run.
  • Deleting the page before creating its replacement.

How to fix it

  1. Create the replacement page first, then delete this one.
  2. Or rename and re-brand this page instead of deleting it.

Related codes

  • RU-5009: Status page or component not found

Still stuck?

Ask support and mention RU-5011: the code pins down the exact refusal path, so you skip the diagnostic back-and-forth.