RealUptime Status
Same outage. Two status pages.
RealUptime Status checks your service from ten live regions and publishes every one of them separately, so a customer in Asia-Pacific never reads “all systems operational” while their region is actually down.
Watch a region fail
This is the page your customers refresh. Here is what it does when one region goes.
Simulated regional readings at 09:00
No open incident. A healthy page stays quiet and takes up little room.
Four regions checking the same endpoint, each publishing its own reading.
Simulated timeline on an example domain, not a live reading and not a customer's page. A real page redraws these four readings on every check.
Checked from one region. The Asia-Pacific outage is invisible to it, so the badge stays green while customers there file tickets.
acme.dev
ExampleDegraded- US-EastOperational
- US-WestOperational
- EuropeOperational
- Asia-PacificDegraded
Incident drafted automatically: checks from Asia-Pacific are failing while three regions remain healthy.
What comes with the page
Built for a page your customers actually bookmark.
Maintenance windows
Schedule planned work ahead of time so it reads as maintenance, not an unplanned incident.
Subscriber updates
Customers can subscribe to your status page and get notified when its state changes, without following a support channel.
Your own domain and branding
Point status.yourcompany.com at your page and match it to your own brand instead of shipping it under someone else's.
A full uptime history
Every monitor keeps a running history bar customers can check before they decide to trust the current reading.
Incident communication
When a region fails, the incident writes itself.
The moment a regional check confirms a failure, RealUptime Status drafts the incident automatically instead of waiting for someone to notice, decide what to say, and write it by hand. It names the affected region, stays on the page while the failure continues, and closes itself out when the region recovers. Your customers find out from your status page, not from a support ticket.
How it works
From probe to page in three steps.
01
Add your endpoint
Point RealUptime Status at a URL. The probe fleet starts checking it from ten regions, US-East, US-West, Europe, Asia-Pacific, US-Central, Canada, UK, Southeast Asia, Australia, and South America, every 60 seconds, on every plan.
02
Every region published separately
Your public page shows each region's own reading and history. Nothing is averaged into one badge, so a regional outage cannot hide.
03
Incidents handle themselves
A confirmed regional failure drafts the incident, names the region, notifies subscribers, and closes itself when the region recovers.
Pricing
Flat pricing. No per-check metering.
All ten regions on every plan, including Free. These are RealUptime Status's own plans; the other products have their own on the pricing page.
Free
$0
No card required
Everything you need to publish an honest status page.
- 10 monitors
- All 10 regions: US-East, US-West, Europe, Asia-Pacific, US-Central, Canada, UK, Southeast Asia, Australia, and South America
- Public status page
- Email and Slack alerts
- 3 team members
- 100 status page subscribers
Growth
$28.99/mo
Billed monthly
Custom domains and programmatic access, on top of everything in Free.
- 25 monitors
- Everything in Free
- Custom domains
- Unlimited status pages
- Monthly SLA reports
- REST API and MCP access
- 10 team members
- 1,000 status page subscribers
Scale
$78.99/mo
Billed monthly
More room to grow, on top of everything in Growth.
- 150 monitors
- Everything in Growth
- Unlimited status pages
- Unlimited team members
- 10,000 status page subscribers
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.
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.
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 StatusYou are here
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
This page is monitored by the product it's selling.
realuptime.io runs on RealUptime Status. No staged screenshots: the same ten regions checking your service would be checking this one right now.