Skip to content

RealUptime Monitor

Your provider's dashboard says fine. Your server disagrees.

RealUptime Monitor is uptime monitoring for your team, not your customers. It checks your endpoints from the same ten live regions as RealUptime Status and alerts your team directly. Nothing gets published anywhere unless you want it to. Signing up for Monitor on its own isn't available yet.

A single-location checkOne probe, no signal
Everything looks fineExample

Checked from one US region while Europe fails for real users. No alert fires, because nothing this check can see is wrong.

With RealUptime MonitorEvery region, separately

api.acme.dev

Example
Degraded
  • US-EastOperational
  • US-WestOperational
  • EuropeDown
  • Asia-PacificOperational

Alert sent the moment Europe failed. The other three regions staying healthy never delayed or suppressed it.

The server agent

Inside the box and outside the front door, on one screen.

An uptime check tells you the front door answered. The agent tells you the disk is at 88%, that PostgreSQL answers in 3ms on a private address nothing outside your network can reach, and what the same app measures from ten regions outside it. One install per server, outbound only, nothing exposed.

Your fleet5 servers, one agent eachSimulated
web-01All thresholds clearup 42 days

Resources

CPU34%
Memory61%
Disk47%

Private services, checked from inside your network

  • PostgreSQL10.0.1.14:54323ms
  • Redis10.0.1.21:63791ms

Never exposed to the internet to be watched. The agent connects outbound and reports in.

The same app, from outside, in 10 regions

  • US-East118ms
  • US-West96ms
  • Europe142ms
  • Asia-Pacific121ms
  • US-Central104ms
  • Canada101ms
  • UK129ms
  • Southeast Asia137ms
  • Australia156ms
  • South America148ms

All of it, on 5 servers, for $0. Free includes 5 servers with 14 days of history. Simulated values on example hosts, not a live fleet.

What Monitor actually measures

One check, broken into the phases that make it slow.

What comes with it

Everything the product ships with.

Four-region checks, private

US-East, US-West, Europe, and Asia-Pacific on every plan, readings kept separate. Nothing is published.

Server agent

CPU, memory, load, and disk with charts, plus checks against private targets behind your firewall.

Heartbeats and TCP

Catch a cron job or worker going silent, and watch ports that are not HTTP.

Alerts where you work

Email and Slack, Webhooks, and PagerDuty, with disk and memory thresholds.

How it works

From setup to signal in three steps.

01

Add a check or install the agent

Point Monitor at a URL or TCP port, or install the agent on a server to watch CPU, memory, load, disk, and targets behind your firewall.

02

Ten regions, separate readings

Every check runs from ten regions and the readings stay separate, so a regional failure cannot hide in an average.

03

Your team knows first

The moment any region disagrees, alerts go to email, Slack, webhooks, or PagerDuty. Nothing is ever published.

RealUptime Monitor

Watch your own servers, privately.

Monitor is a separate product with its own plans. You install a small agent on each server; it checks services behind your firewall and reports CPU, memory, load and disk, and none of it appears on a public page unless you put it there.

Monitor Free

$0

No card required

For a homelab, a side project, or the first server you want to stop guessing about.

Install the agent and watch your own machines, free forever.

  • 5 servers
  • 14 days of history
  • CPU, memory, load and disk, with charts
  • Checks against private targets behind your firewall
  • Disk and memory threshold alerts
  • Email, Slack, webhook and PagerDuty alerts
Start free

Monitor Scale

$48.99/mo

or $489.90/yr, 12 months for the price of 10

For a fleet big enough that a year of history is how you answer questions.

Forty servers and a full year of history, on top of everything in Growth.

  • 40 servers
  • 1 year of history
  • Everything in Monitor Growth
  • Extra servers at $1.50 per server per month
Cancel anytimeMonitor Free needs no cardSeparate from your Status plan

Four products, one incident

Three products hold a piece of the answer. The fourth one publishes it.

Every product here is worth running on its own. Run more than one and they stop being separate graphs: signals that share a time window get joined into a single window with a verdict, so the question an incident actually asks, is this us or is this upstream, has an answer instead of three tabs.

  • RealUptime MonitorYou are here

    Your infrastructure looks healthy

    Regional checks and the server agent's own CPU, memory, and disk thresholds, so an incident can be ruled IN or OUT on your side.

  • One issue's rate just jumped

    The issue that started throwing, when it started, and which release it arrived in, counted honestly including what was dropped.

  • A vendor you depend on is degraded

    Our own independent probes on the services you named as dependencies, not the vendor's own status feed.

Correlated windowExample

Probable upstream incident. Your infrastructure appears healthy.

The window names every signal it used and every one it could not get, and it says probable, never confirmed, because a joined time window is evidence and not proof.

RealUptime Status

The incident your customers read, drafted from what was actually measured, with the affected regions named.

RealUptime Complete is what paying for more than one of these is called, and the bundle discount is on the pricing page. The discount is the small part. The reason to run them together is the sentence above.

See it live

The same network watching this page watches yours.

realuptime.io runs on RealUptime Status, checked by the same ten regions RealUptime Monitor uses privately for endpoints that never need a public page. Signing up for Monitor on its own isn't available yet.