Create an account
Sign up with email and a password, or continue with Google, GitHub, or Apple. Your first status page is created automatically, so there is nothing to configure before you add your first check.
Add your first check
From the dashboard, choose Add check and pick a type: HTTP for a URL that should return a healthy response, TCP for a port that should accept a connection, DNS for a record that should keep resolving, or Heartbeat for a job that should keep checking in on its own schedule. Give it a name and a target, choose which of the four regions check it (all four by default), and save. See checks & monitors for what each type verifies and how it decides up from down.
RealUptime's own cloud probes run HTTP, TCP, and DNS checks. If what you need to watch sits behind a firewall or on a private network, the cloud probes cannot reach it: install the Monitor agent instead, on a server inside that network.
Watch it go live
The first result usually lands within a minute. Your dashboard shows the current state per region; your public status page shows the same reading to anyone who visits it. See status pages for the public address, custom domains, and subscriber notifications.
Get alerted
Add an email, Slack webhook, generic webhook, or PagerDuty integration key so a real change in status reaches you rather than requiring you to keep the dashboard open. See alerting & on-call for how each channel behaves and what fires it.
Next steps
- Install the Monitor agent for anything private the cloud probes cannot reach, and to chart your server's own CPU, memory, disk, and load.
- Attach a custom domain so your status page serves at your own hostname instead of a realuptime.io subdomain.
- Generate an API key to manage checks programmatically, or connect the MCP server so an AI agent can check status directly.