Early access
Uptime monitoring that starts in our cloud and reaches into yours when you need it.
Add a check and it runs from our fleet of monitors worldwide — nothing to install. Have something behind a firewall? Run our small open-source agent next to it. Already running Uptime Kuma? Have it phone home, so you'll know when the thing watching everything else goes quiet.
Paid plans aren't open for checkout yet — the free plan is the way in for now.
Start with our fleet. Add your own if you need to.
Your own monitors are a feature, not a requirement. Most public endpoints never need one.
Our shared fleet
Included on every plan · nothing to run
Paste a URL and choose where it runs from. Checks run from monitors we operate worldwide, and when a check runs from more than one location, an alert needs two of them to agree, so one bad route doesn't page you.
Best for anything reachable from the public internet: your site, your API, your certificates.
Your own monitors
Optional · free and unlimited on every plan
monitor is one open-source binary. Run it on a server, a
colo box or a branch office network and it checks what our fleet can't reach: an
internal admin panel, a VPN-only service, a site-to-site link. It only makes outbound
connections, so there's nothing to open in your firewall.
Best for anything on a private network, or anything you'd rather not point a third party at.
Choose per check, not per account: run one on your own monitors, on ours, or on both. A check aimed at an internal address is kept on your own monitors automatically.
Running Uptime Kuma? Let it phone home.
Kuma is great at watching your internal network. But it lives there too — if its host or its uplink dies, nothing tells you. A heartbeat check closes that loop.
- Create a heartbeat in 10pm uptime and copy its URL.
- In Kuma, add an ordinary HTTP(s) monitor pointed at that URL.
- Every time Kuma runs it, that's a beat. When the beats stop, we alert you — by email, ntfy, webhook or Slack.
Keep Kuma for everything it already does. The same URL works for a cron job or a
backup script that can curl when it finishes — or a
tool built to call a Kuma push URL, since ours accepts the same
?status=up|down convention. Every plan includes heartbeats,
including one on Free.
What you get
Alerts you can trust
Agents check their own connection before blaming your service, and when a check runs from several locations, a down alert needs two to agree. You get a recovery notice, and optional reminders while it's still down.
Alerts where your team is
Email and ntfy push on every plan, signed webhooks and Slack on the higher ones. Route each check to the channels that should hear about it.
More than "is it up?"
HTTP(S), TCP and bare-TLS checks. Match response content, set a latency ceiling, assert an exact status code, get certificate-expiry warnings, or invert a check to confirm a port stays closed.
A public status page
Publish only the checks you choose, at a link you can share with customers. On paid plans.
Built for teams
Invite colleagues by email. If you belong to more than one organisation, switch between them from the nav bar.
Keeps running when things break
Your own monitors buffer results and keep checking through a network or server outage, then catch up. And if a monitor itself goes quiet, we tell you.
Careful with what you point us at
Monitoring touches sensitive things. We'd rather hold less of it.
Private definitions
For a check on one of your own monitors, you can keep its URL, headers and match rules off our servers entirely. We store a name; the definition lives only on your monitor.
Your network stays yours
Our shared fleet refuses to connect to private, loopback or link-local addresses, so it can't be turned into a way into anyone's network — ours or yours.
Your organisation, only yours
Customers are isolated from each other in the way the code is built, not by convention, and an automated test fails if that boundary is ever weakened.
No secrets kept in the clear
Passwords are hashed, and so are API keys and enrollment tokens — each is shown to you once, when it's created.
Early access, honestly
10pm uptime is new. The free plan is open, paid checkout isn't switched on yet, and the prices on the pricing page may move before general availability. If you sign up now, you'll help shape what it becomes — and we'd like to hear what you think.