1. Create the page and pick its components
From the dashboard, create a status page and attach the checks that should appear as components. Each component shows its regional health separately: a regional outage is visible as exactly that, not averaged into one badge.
2. Choose the address
Every page gets its own <slug>.realuptime.io subdomain; paid plans can verify a custom domain instead.
3. Publish and share
The page is server-rendered, fast, and carries no third-party scripts. Subscribers can sign up for incident notifications, within your plan's subscriber allowance.
4. Open incidents when things break
Incidents attach to a component and region. Note that resolving an incident while realuptime's own probes still measure the component as down is refused unless forced (error RU-5003): the page must not say resolved while the measurement disagrees.
Go deeper
The full reference lives in the docs: Status pages documentation. Error codes named above are each explained in the error-code reference.