Uptime, on-call and status pages · one product

Know it's down
before your customers do.

Uptimely checks your services every minute, pages the right person when one breaks, and shows your customers a status page — replacing a Pingdom + PagerDuty + Statuspage stack. On-call and status pages are included on every plan, never billed per seat.

  • 1-minute checks on the free plan
  • /v1 REST API + OpenAPI 3.1
  • Official TypeScript SDK
  • MCP server for AI agents (early access)
  • Two failed checks before we page you
Add to Claude
All systems operationalChecking every minute · around the clock
Watching 4 services1-min interval · synchronized sweep
api
128ms
checkout
214ms
auth
96ms
cdn
42ms
Uptime · sample99.000%
Check interval1min
Check types14
Latency · sample214ms
SlackDiscordEmailSMSWeb PushWebhooksOpenTelemetryPrometheusTwilioGoogle OAuthSlackDiscordEmailSMSWeb PushWebhooksOpenTelemetryPrometheusTwilioGoogle OAuth
00 Every minute

One missed check is a blip. Two is an incident.

Every monitor is checked as often as once a minute. A failed check shows on your status page right away, but by default nobody is paged until a second check in a row fails. Then an incident opens, whoever is on call is paged, and it all resolves itself once checks pass again.

01 Real-time

The dashboard's never not refreshing

This is the live view your workspace gets — response times wiggling as checks run minute by minute, around the clock.

workspace · all monitors
Last check · just now
api.example.com
Primary API
128ms
checkout.example.com
Customer checkout
242ms
auth.example.com
OAuth + sessions
78ms
cdn.example.com
Asset delivery
25ms
webhooks.example.com
Outgoing events
341ms
5/5 operationalhttp · tcp · dns · ssl · ping · heartbeat · +8 more
02 Coverage

Watch anything, anywhere

Point a check at anything with a URL, hostname, or IP — wherever in the world it runs. HTTP, TCP, DNS, SSL, ping, and heartbeat checks, from once a minute to once a day, around the clock.

Illustration — your services, wherever they run.

What every check runs through
Runs on your interval
From every minute to once a day, per monitor.
Confirms before it flips
A failing check runs again before a monitor goes down.
Judges your criteria
On the check that ran, or across a window you choose.
Suppresses the noise
Muted monitors and known-down dependencies don't page.
Tells you once
The flip and the incident it declares arrive as one message.
03 AI Copilot · live

Ask the monitoring it monitors itself

A built-in AI that knows your monitors, your incidents, your on-call. Ask what broke, when it happened before, who's on call. It quotes your own data back at you with timestamps — and every write needs your in-chat approval.

CopilotLIVE
  • What's down right now?
  • When was checkout-api last down?
  • Who's on call right now?
  • Draft a postmortem for the outage
  • Create a monitor for our new API
  • + New conversation
Context window
42 monitors · 30d history · on-call rotas
Is anything down right now?
04 MCP · early access

An MCP server for the agents you already use

Uptimely exposes your monitors, incidents, status pages, and on-call as an MCP server. Claude Code, Cursor, your own agent — point it at app.getuptimely.com/api/mcp and it reads your runtime.

— on-call@laptop — claude mcp
$claude mcp add --transport http uptimely https://app.getuptimely.com/api/mcp
▶Opening browser — sign in and approve access to your workspace …
✓Connected — 20 Uptimely tools available
$claude 'is anything down right now?'
→Calling uptimely_monitor_list
←5 Operational · 1 Offline (checkout-api)
→Calling uptimely_incident_list({ activeOnly: true })
←1 open incident · “checkout-api is offline” · declared 12m ago
$Yes — checkout-api is down and its incident is already open.
Exposed tools · 20 total
  • uptimely_monitor_listread the current status of every monitor
  • uptimely_incident_listopen & recent incidents at a glance
  • uptimely_incident_declaredeclare an incident from an agent
  • uptimely_monitor_createregister a new Website / API / DNS check
  • uptimely_monitor_status_historywhen was it last down, and for how long
  • uptimely_incident_postmortem_savesave an incident's postmortem note
05 Platform

Everything you need to keep something up

One platform — the monitor, the alert, the status page, the postmortem. No five different SaaS bills.

01

Synthetic checks, minute by minute

HTTP, TCP, DNS, SSL and heartbeats. Checks every minute on every plan, with response-time history so you can tell a slow burn from a real outage.

02

Status pages that look like yours

Public or private. Custom domain. Real RSS. Subscribers see the same numbers your operators do.

03

Alerts where you actually look

Slack, Discord, SMS, email, webhook. Escalation, and ack from the alert.

04

Incidents, automated

An incident opens itself when a check fails. Closes itself when health returns. Keeps the timeline for the post-mortem.

05

On-call that runs itself

Rotations, escalation chains, and layers that cover only the hours you set. The right person gets paged — and an ack stops the chain.

06

Logs & traces, one pane

OpenTelemetry-native. Search by trace id, by service, by span attribute. Free-text query, no DSL.

Read more about website monitoring, status pages, SSL certificate monitoring, cron job monitoring, DNS monitoring, or every feature.

06 Custom domains

Your status page, on your own domain

status.acme.com instead of a vendor URL. Add a subdomain, point one CNAME record, and Uptimely serves your page there — HTTPS included.

Guided DNS setup

An embedded setup flow walks you through the records at your DNS provider and flips the page live the moment they verify — or copy the one CNAME record and add it yourself.

HTTPS, handled

The certificate is issued and renewed for you once your DNS verifies. Nothing to upload, nothing to rotate, nothing to remember next year.

Watched after it goes live

Your page's getuptimely.com address keeps working alongside the custom domain. And if the DNS record ever drifts, the dashboard flags it — put the record back and the domain recovers on its own.

On every plan

Custom domains aren't paywalled — the Free plan's status page can use one too. Pro adds unlimited status pages, each with its own domains.

07 Incident lifecycle

From “check failed” to postmortem published

Most monitoring tools page you and leave. Uptimely runs the incident — opens it, escalates it, updates your status page, closes it, keeps the record.

00:00
00:15
00:18
00:42
04:12
04:14
00:00 UTC

Check fails

/v1/checkout/healthz starts returning 503.

08 Wire it in

However you ship, that's how you add monitors

Click in the dashboard, ask the in-app Copilot, call the /v1 REST API, or connect your AI tools over MCP. Same data model under all of them.

# One command — OAuth happens in your browser
claude mcp add --transport http uptimely \
  https://app.getuptimely.com/api/mcp

# Then just ask:
#   "Is anything down right now?"
#   "Create a monitor for our new API"
09 Pricing

Simple, honest pricing.

Start free and upgrade to Pro when you need room to grow. We never bill per-seat, per-incident, or per-alert.

Free$0Free forever · for solo builders
  • Up to 10 monitors
  • 1 status page
  • Up to 3 team members
  • 1-minute checks
  • Incidents, alerts & on-call
Start free
EnterpriseCustomFor larger fleets
  • Everything in Pro
  • Custom monitor volume and terms
Talk to us

Prices are shown in USD. See pricing in your own currency.

Monitoring, status pages, incidents and on-call in one product — replacing a Pingdom + PagerDuty + Statuspage stack.

Do I need a card to sign up?

No. Start on the Free plan with no card at all. A card is only required when you choose to begin the Pro trial.

How does the free trial work?

The 14-day Pro trial needs a card, and the card on file is charged when the trial ends — unless you cancel first. Pro is $29/month. Cancel anytime in one click from Billing.

What happens when my trial ends?

You move to the Free plan automatically and your data stays intact. You just can't add resources beyond the Free limits until you upgrade.

Can I cancel anytime?

Yes. Cancel whenever you like and you keep Pro until the end of your current billing period.

How is Uptimely different from UptimeRobot, Better Stack, or Pingdom?

Uptimely is one product where those are usually two or three. Monitoring, branded status pages, the full incident lifecycle, on-call escalation, scheduled maintenance and OpenTelemetry telemetry are all included on every plan — including Free, which also runs checks at 1-minute frequency. Pricing is flat rather than assembled from per-responder seats and per-resource add-ons: $0 on Free, $29/month on Pro with unlimited monitors and unlimited status pages. Uptimely also has a public REST API, a TypeScript SDK, signed outbound webhooks, a Prometheus metrics endpoint and a remote MCP server for AI agents. There is a detailed side-by-side page for each of these products at getuptimely.com/compare.

Is Uptimely an alternative to self-hosted Uptime Kuma?

Yes, if you would rather not run it. Uptime Kuma is free and MIT-licensed and it is a genuinely good self-hosted checker — the cost is a server to run, a database to back up and upgrades to schedule, and the monitor watching your infrastructure lives on your infrastructure. Uptimely is hosted, and adds the things Kuma has no model for: incidents with states and timelines, on-call duty policies with escalation, postmortems, multi-user accounts with roles, alert-noise controls such as per-monitor mute and monitor dependencies, and a REST API and SDK that create, update and delete monitors.

You build it.
We watch it.

Start free — no credit card. When you're ready, try Pro free for 14 days.