Migrate from UptimeRobot

In UptimeRobot, go to Integrations and API and create an API key. A read-only key is enough and is the one to use: the import only ever lists monitors, so nothing in your UptimeRobot account is changed, paused, or deleted by moving. Platform API access is included on every UptimeRobot plan including Free, so this step costs nothing even if you never paid them. Keep the key in your clipboard for the next step and revoke it in UptimeRobot once the import is done.

In your RealUptime dashboard, open the Import from another service page, pick UptimeRobot, and paste the key. RealUptime pages through UptimeRobot's monitor list and shows you a preview before creating anything. HTTP and HTTPS monitors come across with their name, URL, and check interval. Keyword, ping, port, and heartbeat monitors come back listed and marked unimportable with the reason, rather than being silently skipped or created half configured, so the preview is an accurate picture of what your account will look like when you press the button.

Your check interval carries over in seconds. If a monitor was on UptimeRobot's 5-minute free-plan cadence, it lands here at 5 minutes and you can drop it to 60 seconds, which is the floor on the Free plan here as well as on Growth.

This is the part worth doing deliberately, because it is the difference that made you look. UptimeRobot's own help center describes multi-location monitoring as rotational: a check runs from one selected region at a time, cycling through the regions assigned to it. RealUptime reads every region your plan includes on the same run and publishes each region's answer separately, so "down in Europe, fine in US-East" is a thing you can see rather than a thing you infer. Our fleet runs ten live regions. Free checks from four of them (US-East, US-West, Europe, Asia-Pacific), Growth from eight, and Scale from all ten. Say that plainly rather than sell it: our free plan gates regions too. What it does not do is show you one rotating reading and call it the answer.

The mapping table below is the full list. The one that needs a moment of planning is heartbeats: a heartbeat is a token, and a token cannot move between vendors, so each cron job or worker gets a new ping URL here and its schedule line has to be edited. A brand new heartbeat monitor sits in "awaiting first ping" and pages nobody until the job checks in for the first time, so you can create them all and roll the URLs out at your own pace without a wall of false alarms.

Leave both services running for a few days and compare. When the readings agree, cancel there. Nothing here is a trap on the way out either: see what leaving RealUptime looks like before you commit to us, not after.