Switching from UptimeRobot
DownForReal hosts Uptime Kuma for you, imports the monitor list you already keep in UptimeRobot, and then adds the step UptimeRobot leaves out: every down alert is checked by probes in three regions before it reaches you, so a routing problem near the checker stops posing as your outage. The price is one flat $10 a month for up to 100 monitors.
The switching path
The list you maintain in UptimeRobot is the input to the move, so there is nothing to retype and no weekend project standing between you and a working second opinion on your alerts.
Pull your monitor list out of UptimeRobot as an API export or a CSV file, whichever you already use, and bring that file to DownForReal.
The importer recreates each monitor inside your own Uptime Kuma instance with its name, type, target, and interval intact, and it shows you the result so you can check the move before anything depends on it.
Keep your UptimeRobot account running through the trial while DownForReal watches the same services, and compare the alerts each service sends before you cancel anything.
UptimeRobot does not export notification channels in a form Uptime Kuma can take, so your email, Slack, and webhook alert channels are set up once by hand inside your new instance. Everything that watches your services moves automatically, and the channels take a few minutes to reconnect on the other side.
Why people switch
A monitor that checks from one place can only report what that one place can see, and a broken network path between the checker and your site reads exactly like a dead site from where the checker sits.
When your instance reports a monitor down, probes in New York, Frankfurt, and Singapore check the same address at the same moment, and the alert goes out only when at least two of the three probes also fail to reach it. When the vote fails to confirm, the alert is held back, and the suppression is written into your own instance as a log entry you can read, because an alerting system that hides its decisions cannot be audited. A real outage looks the same from everywhere, so genuine failures still page you within seconds.
Multi-location checking is the oldest open request in the Uptime Kuma project. Issue #1915 asked for it in 2021 and was closed as not planned, and self-hosters have been stitching together second installs by hand ever since. DownForReal builds the confirmation into the alerting path itself, which is the part you cannot bolt onto UptimeRobot from the outside either.
Pricing, in structure
UptimeRobot sells tiers, and the tiers are built around how many monitors you run, with shorter check intervals and further features placed in the higher tiers as the list grows. DownForReal sells one plan, and the plan already contains the confirmation vote, the status pages, and the interval most people switch for.
| Question | UptimeRobot | DownForReal |
|---|---|---|
| How the price is counted | Tiered plans built around monitor counts, with interval and feature differences between the tiers | One flat price: $10 a month, or $75 a year |
| Monitors included | Set by the tier you buy, and the bill grows as your list grows | Up to 100 monitors on the single plan |
| Check interval | Shorter intervals sit in the higher tiers | A 60-second minimum interval on the single plan |
| Before a down alert fires | The alert fires on the word of the checking location | Probes in New York, Frankfurt, and Singapore re-check, and at least 2 of the 3 must agree |
| Status pages | Offered as part of the service | Included, and mirrored onto a separate host so the page stays up while your services are down |
| Moving your monitors in | Coming the other way, the list is rebuilt by hand | An importer converts your UptimeRobot export into a running instance |
UptimeRobot plan details change over time, so confirm their current tiers on their own pricing page before you decide. The DownForReal column describes the single plan we sell today, and the trial runs the full plan for 14 days.
Start the trial, import your list, and let the two services watch the same sites for two weeks. The alerts that only one of them sends will tell you more than this page can, and you can walk away with your UptimeRobot account untouched if the vote earns nothing.