On this page
Last reviewed 2026-09-15. Corrections welcome: hello@perstat.io.
Decide by workflow
Perstat fits when regional confirmation, on-call ownership, status communication, and a curated availability record need to stay in one operational workflow.
UptimeRobot fits when a larger free plan, lower paid entry price, a basic uptime and status-page workflow, or its public API covers the decision you need to make.
UptimeRobot is an established uptime checker and cheaper at the entry. Its free tier carries 50 monitors to our 10, and Solo starts at €10 per month. Status pages on your own domain, maintenance windows, and SMS and voice credits start at Solo. White-label pages and subscribers start at Team, and 15 s intervals at Scale.
Perstat is what you switch to when someone asks for proof. It keeps a curated availability record with attributed exclusion windows and confirms outages with a configurable quorum across 11 regional check types. It runs on-call escalation to a phone call with post-mortems, and its status pages on your own domain start at Sentinel.
Perstat runs its control plane in the EU and is operated by a German company. Its net prices are on the page.
Compare the facts side by side
| Perstat | UptimeRobot | |
|---|---|---|
| Published monthly price | Pulse, €29/mo net: 50 monitors at 60 s, 3 regions | Solo, €10/mo (€9/mo annual): 50 monitors at 60 s, custom domain, 12-month data retention |
| Mid tier | Sentinel, €89/mo net: 150 monitors at 30 s, all 6 regions, on-call, gated pages | Team, €41/mo (€35/mo annual): 100 monitors at 30 s, 30 SMS and call credits, 24-month data retention |
| Fastest interval | 10 s on Enterprise through MCP, 30 s at Sentinel | 15 s on Scale. Faster on Enterprise, price on request |
| Alert confirmation | default quorum of 2 regions for 11 regional check types, configurable, Agent and Heartbeat excluded. Current topology published | one or more of 4 regions. A failed check is confirmed by multiple nodes within the affected region before an incident opens. No cross-region agreement required |
| Cron job monitoring | heartbeat monitors: your job calls a secret URL, period plus grace, missing call opens an incident | heartbeat monitors from Solo |
| On-call escalation | ladder to verified phone numbers, ack semantics, from Sentinel | SMS and voice credits from Solo, bundles per plan |
| Availability evidence | attributed, reversible exclusion windows in the curated record, editorial sample report, manual CSV plus manifest export on request | uptime history and reports. No equivalent curated exclusion-window register found in the official sources reviewed |
| Public history of resolved incidents | 7 days to 2 years by plan, public status-page history only. Other retention and deletion periods: current boundary | not stated separately. Data retention is 3 to 24 months by plan |
| Jurisdiction | German GmbH, EU control plane | UptimeRobot s.r.o., Bratislava, Slovak Republic (EU). Confirm hosting for your checklist |
| Automation interface | REST keys read 7 endpoints. Scoped API keys or OAuth with PKCE reach MCP reads and writes, with no delete | hosted MCP with OAuth or API key for monitor actions and incident detail. Public API and CLI. iOS and Android apps |
Figures reviewed 2026-08-27, prices and plan features again on 2026-09-15, from these official UptimeRobot pages:
UptimeRobot prices are in EUR as shown on 15 September 2026, with annual equivalents where published. Our figures come from the pricing page, net.
The table shows where UptimeRobot is ahead: free-tier size, entry price, custom domains and maintenance windows from Solo, SMS and voice credits from Solo, and breadth of client and automation interfaces.
Test the workflow in parallel
Perstat currently imports neither configuration nor history from other products. Set up the required monitors in Perstat. Export and archive any history you need before you switch off the old system.
- Monitor one representative endpoint in both products and match interval and locations where their plans allow it.
- Keep UptimeRobot’s notification path active while Perstat observes the same endpoint. Use a controlled test endpoint for a planned failure and recovery.
- Compare verification, incident boundaries, and acknowledgment. Then compare status communication and the retained record before you decide whether the broader workflow is worth the move.
Automatic incidents and acknowledgment are available on every plan. Testing an on-call rotation and phone escalation requires Sentinel or above.
Set up the first check and check the plan limits. When you are ready, start monitoring free.