Uptime checksHTTP, keyword and TLS checks on your addresses, with the evidence of every failure kept.
Cron heartbeatsOne curl line at the end of a job. Silence past the grace window is the alert.
Status pagesA page your customers read, on your own domain, with the incident in plain words.
ExplanationsA written reason with the alert: what failed, what the checks saw, what to look at first.
on every plan Alerts to six channelsImportTeams
APIRead, pause, acknowledge and post updates from your own scripts.
MCP serverAsk your AI assistant what is down, then acknowledge or post an update.
WebhooksSigned JSON when an incident opens, is acknowledged or recovers.
Heartbeat guidescrontab, GitHub Actions, Railway, Node, Go, WordPress and Kubernetes.
DocsShort guides, each one task, with the lines to copy.
GuidesWhy monitors send false alarms, why cron jobs stop, and the fix.
ChangelogThe big things we shipped, newest first.
Trust and securityWhere your data lives, who processes it, how long we keep it.
Referral program soonRecommend Upglory to another team. In the works.
Contact
Docs menu Start here / Import

Bringing your checks over from another tool

Export a CSV where you are now, drop it into Import on the monitors list, and read the preview before anything is created. Nothing is overwritten and nothing alerts until you say so.

3 minute read Guide

Where the export lives

ToolWhereWhat comes out
UptimeRobotDashboard, then the three dots at the top right of the monitor list, then Export monitors as CSV.The file holds a friendly name and a URL per row. We read the URL column and ignore the rest.
PingdomExperience Monitoring, then Uptime, then the Export button over the list.Uptime checks come out with their hostname or full address. A TCP or ping check is not an HTTP address and is left out of the preview.
Better StackMonitors, then the three dots beside New monitor, then Export to CSV.The URL column comes across as it is. Heartbeats are not in this file; add those from Cron job or service.
ChecklyThe CLI: checkly checks list, or the checks in your repository.Paste the addresses the checks call. Anything that is not an HTTP address is shown as skipped.

What we read

A CSV needs one column of addresses; every other column is ignored. We look for a column called url , address , target , host , and failing that we take the first field in each row that reads as an address. A JSON export works the same way: we walk it for addresses. You can also paste a list, one address per line.

What the preview tells you

will be created
A new monitor on your plan's schedule and locations.
already here
You watch that address already, and it is left exactly as it is.
not an address
The line is not an http or https address.
not now
Your plan is full; the line stays on screen so you can see what was left.
we cannot check this address
It points inside a private network, which we never call.

Imported monitors are created paused unless you turn the tick off, and the toast after an import offers Undo for ten minutes. Undo removes only the rows nobody has touched since.

Heartbeat guides

Nothing here matches your export? Send us the file and we will read it. Write to us