Switch from Pingdom to Uptrack

Step 1 — Get your checks as a CSV

Uptrack’s importer reads a plain CSV with a column for the check name, the URL or host, and the type. You can pull that from Pingdom’s API (the GET /checks endpoint returns every check with its name, hostname, type, and resolution), or just build the file yourself in a spreadsheet. A typical export looks like:

Name,URL,Type,Resolution
Marketing site,https://example.com,HTTP,1
Checkout API,https://api.example.com/health,Keyword,1
Mail server,mail.example.com,Ping,5
Database,db.example.com:5432,TCP,1

The headers don’t have to match exactly — Uptrack auto-detects Pingdom, UptimeRobot, and generic column names (name / URL / type / interval / keyword), so an export straight from Pingdom, or a file you typed by hand, both work. Pingdom’s common check types map over directly: HTTP(S), ping (ICMP), TCP port, and keyword checks all have a native equivalent in Uptrack.

Step 2 — Import it into Uptrack

In your dashboard, open Uptime Monitors → Import, and drop the CSV onto the page. Uptrack parses it client-side, shows you a preview of every check it found, and lets you confirm before anything is created.

On import it skips any URL you’re already monitoring (so re-running the same file is safe), fills up to your plan’s monitor limit, and reports exactly what was created, skipped, or had a problem. No half-finished state, no duplicates.

Step 3 — Set up alerts and go

Checks come over with their URL, type, and name. The last step is telling Uptrack where to reach you: add an alert channel (email, Slack, Discord, and Telegram are on every plan, including free) under Alerts, and you’re done.

A couple of things you get on the way in: every check runs at 30-second intervals on the free plan — tighter than Pingdom’s one-minute floor — and an alert only fires after consecutive checks from multiple regions agree it’s really down, so the move usually comes with fewer false alarms, not more.

Prefer it in version control?

If you’d rather keep your checks as code, the same data works as a YAML file you can apply from CI with the Uptrack CLI — define monitors in a file, review changes in a pull request, and sync on merge. The CSV import is the fastest way to get started; the CLI is there when you want it.