Monitors → Import. Four sources:
- UptimeRobot: paste a read-only API key. We read the monitor list and do not store the key.
- updown.io: the same, with a read-only key.
- Uptime Kuma: upload the backup JSON that Kuma exports.
- CSV: upload a file. Comma or semicolon separated, header row optional.
Files are limited to 2 MB and 5,000 rows.
CSV columns
url, name, interval, group, type, host, port, keyword, paused
Without a header the order is url, name, interval, group. Interval takes values like 30s, 5m or 1h and defaults to 5 minutes. Type is http unless you say otherwise; for tcp, smtp, dns and tls give host and port.
What happens to the drafts
The import shows every monitor as a draft before anything is created. Intervals snap to 15 seconds or slower (never 10), targets that are already monitored are flagged as duplicates, and credential headers are never imported. The cost in credits is shown before you confirm. Drafts for hosts on domains you have not verified get the unverified limits, so verify your domains first if you want fast intervals.
The 14-day comparison
After an import from UptimeRobot or updown.io you can opt in to a comparison: for fourteen days their alerts are set against what our probes saw at the same moment and each is labelled confirmed, not confirmed or unjudged. It is the simplest way to see how many of the alerts you used to get were real. The switch page explains the method.
Quick add
The one-line box at the top of the Monitors page takes one or more bare addresses, with or without a scheme. Ports 80, 443, 8080 and 8443 become HTTP monitors, 25, 465 and 587 SMTP, and any other port a TCP check. Up to 20 drafts at a time, each confirmed before it is created. On accounts where the AI features are turned on, the box also reads free text ("the shop and the API every minute, the blog every 5"); the AI never sets headers, bodies, credentials or write methods.
Last change: 31 October 2026.