Migrate · RealUptime Monitor
Migrate from Pingdom
Pingdom customers are being moved onto SolarWinds Observability on a vendor-set timeline, and after the transition window closes Pingdom becomes read-only. If you would rather leave now than ride that migration, here is the real, current path: what to pull out of Pingdom before it goes read-only, and exactly what RealUptime Monitor does and does not do with it once you have it.
Export your check list from Pingdom
There is no CSV-export button in the Pingdom dashboard for your check inventory. The complete list lives behind Pingdom's own public REST API (version 3.1): a signed-in account can generate a Bearer token under Pingdom's API settings, then call GET https://api.pingdom.com/api/3.1/checks to get back every check's id, name, hostname, type (HTTP, HTTP Custom, TCP, Ping, DNS, UDP, SMTP, POP3, or IMAP), and its resolution (check interval, in minutes). That response is the export: save it, and you have the full inventory to re-create elsewhere.
Do this before Pingdom's migration into SolarWinds Observability finishes for your account. SolarWinds' own migration documentation says Pingdom becomes read-only once your account's transition window closes, and that historical data is not carried over into the new platform, so the check configuration you can read out today is not guaranteed to be readable in the same form later.
Add the checks to RealUptime
Say plainly what RealUptime's importer does today: it is a two-step, live API-key flow that fetches a preview from the competitor's own API and lets you pick which monitors to create. As of this page, it supports exactly two providers -- UptimeRobot and StatusCake. There is no Pingdom adapter, so a Pingdom export cannot be pulled in through that importer automatically, and this page is not going to pretend otherwise.
What that means in practice: re-add each check by hand, using the hostname and resolution values from your Pingdom API export, through the same add-check form every RealUptime Monitor check goes through -- the identical form the importer's own second step calls into. For a handful of checks this is a few minutes of copy-paste; for a large inventory it is the honest, if slower, path until a Pingdom adapter exists.
Map each check type
The table below maps every Pingdom check type this page could verify against RealUptime's own check types (http, tcp, dns, smtp, ping, heartbeat). Where a Pingdom type has nothing to map to here, or a RealUptime type has nothing to map to in Pingdom, that is stated as "No equivalent" rather than stretched into a partial match.
Feature mapping
Pingdom check types, mapped to RealUptime Monitor
HTTP / HTTP Custom
http · Have
Full URL checks, including custom headers and expected-response assertions.
TCP
tcp · Have
Host-and-port reachability checks.
DNS
dns · Have
Resolves a hostname and checks the result.
Ping
ping · Have
ICMP reachability checks.
UDP
No equivalent · Don’t have
RealUptime has no UDP check type today.
SMTP / POP3 / IMAP
smtp only · Partial
RealUptime has an smtp check type; POP3 and IMAP have no equivalent here today.
(none: Pingdom has no dead-man's-switch check)
heartbeat · Don’t have
RealUptime's heartbeat checks (for cron jobs and background workers pinging in) have no Pingdom equivalent, per Pingdom's own published check-type list.
Not covered here: Pingdom's Real User Monitoring product and its public status pages. RealUptime Status covers the status-page half on its own plans (see the full comparison linked below); there is no RUM equivalent in the RealUptime product line today, and this page is not claiming one.
Verified August 29, 2026. Sources: Pingdom REST API, GET /checks (go-pingdom client reference), SolarWinds Observability: Migrate from Pingdom, Pingdom pricing.
Ready to move your checks over?
For the full, sourced pricing and feature comparison against Pingdom, see Full Pingdom comparison. For why a check should run from more than one region at all, see why a status page can show all green during a real outage.