Uptime monitors

UptimeClarity runs HTTP, HTTPS, and TCP checks from the Uptime view. A monitor can be created directly or copied from an existing UptimeRobot account.

Import from UptimeRobot

Choose Import in the Uptime view and enter a read-only UptimeRobot API key. UptimeClarity uses the key to retrieve a fresh preview. The key is kept only for the open import session and is never saved as a source connection.

The preview selects supported monitors by default. Review any interval, duplicate-target, or omitted-setting warnings before importing. A monitor previously imported from the same UptimeRobot account is skipped using its source monitor ID. A manually created monitor with the same target is shown as a warning but can still be imported.

URL query parameters are shown in the authenticated preview and copied into the new monitor. UptimeClarity audit records continue to redact query values.

The import is atomic: either every newly selected monitor is created or none of them are. Plan monitor limits and minimum check intervals still apply.

Supported configuration

The first importer supports:

• HTTP and HTTPS checks, including methods, response codes, redirects, timeouts, supported request bodies, headers, and Basic or Bearer auth.
• Case-sensitive keyword checks.
• TCP port checks.
• Paused monitor state.

Ping, heartbeat, DNS, API assertion, UDP, Digest-authenticated, and case-insensitive keyword monitors remain visible in the preview but cannot be selected. Configuration that UptimeClarity cannot preserve exactly is never silently approximated.

Monitors with fixed UptimeRobot regions or per-region thresholds can be imported. Those regional settings are listed as an import note and omitted; UptimeClarity runs checks from available Cloudflare locations.

Not copied

An import copies monitor configuration only. Historical results, incidents, alert contacts and integrations, maintenance windows, status pages, tags, groups, custom fields, and provider-specific region settings remain in UptimeRobot.