Skip to content
Knowledge base

What realuptime is

A status-page and monitoring company built on one premise: the reading you publish must match the reading we measured, even when the truth is inconvenient.

Who we are

realuptime builds uptime and reliability tools for developers and small companies who need to tell their own customers the truth about an outage. We are not an enterprise observability suite: the product is flat-rate, fast to set up, and honest by construction.

The product family

  • realuptime status: public status pages and incident communication. Regional health is the default view, because a status page that collapses four regions into one badge can say “operational” while an entire region is down.
  • realuptime monitor: private multi-region uptime monitoring: HTTP, TCP, and heartbeat checks, response assertions, an on-host agent for private networks, and server-health metrics.
  • realuptime errors: application error tracking with honest drop accounting: every dropped event is counted and shown, never silently discarded.
  • realuptime outages: a free public outage tracker answering “is X down?” from our own first-party measurements, with a citable URL and no third-party ads, ever.

How probing works

Probes run in four named regions: US-East, US-West, Europe, and Asia-Pacific: and make real requests to each monitored target on its configured interval. Every region reports separately, and the product never invents a reading: a region that has not reported yet shows as awaiting data, a probe that was blocked shows as blocked, and “we do not measure this” is answered as exactly that. The full methodology for the public tracker is at /outages/methodology.

Honesty principles

  • Per-region truth by default: no collapsing four readings into one badge.
  • No fabricated data: a missing measurement is shown as missing, never guessed.
  • Dropped data is counted where you can see it: quota and rate-limit drops appear on your dashboard, never in a black hole.
  • A status page cannot say “resolved” while our probes still measure the component as down, unless you explicitly force it.
  • Flat-rate pricing: no per-subscriber or per-check metering.

The reasoning is written up in full at why status pages lie.

Contact and support

Questions, catalog requests, or anything broken: /support. Plans and pricing live at /pricing, and common questions at /faq.