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. RealUptime's importer connects live to Pingdom's own API and pulls in your HTTP checks directly. Most accounts do not need to re-type anything by hand.
Already have a RealUptime account? Open Import from another service and paste a read-only Pingdom API key to bring your monitors across.
Rather send us the list? Email it to support@realuptime.io and we will import it within 48 hours.
Generate a Pingdom API token
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. That token is what both this page's manual walkthrough and RealUptime's own importer use to call GET https://api.pingdom.com/api/3.1/checks and read 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).
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.
Import the checks into RealUptime
RealUptime's importer is a two-step, live API-key flow: paste the token, it fetches a preview from Pingdom's own API, and you pick which checks to create. As of this page, it supports three providers (UptimeRobot, StatusCake, and Pingdom), so a Pingdom account moves over the same way the other two do, no manual re-entry required for the checks it can read.
One real limitation, stated plainly: the importer reads Pingdom's plain HTTP check type only, the same limitation it already has for UptimeRobot and StatusCake. HTTP Custom, TCP, Ping, DNS, UDP, SMTP, POP3, and IMAP checks are not pulled in automatically; they show up in the importer's preview, flagged as not imported, so nothing silently vanishes. For those, or for any check you would rather hand-type from a list, the same dashboard page also accepts a plain CSV file (columns: name, url, type, interval) as a bulk-import path.
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 31, 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.
From the blog