Features
Everything you need to keep your services online
Checks from multiple nodes, alerts without the noise, incidents handled through to resolution and a status page for your customers.
How it works
-
1
You configure
Add monitors from the dashboard and choose interval, regions, contacts and escalation.
-
2
Nodes check
Check nodes receive the configuration and run checks on their own, even if the central platform isn’t responding.
-
3
We confirm and alert
The outage is confirmed, an incident is opened, notifications go out and the status page updates.
Monitoring
Nine check types with advanced options, run from nodes in multiple regions.
- Advanced HTTP options
- Request method, headers and body, basic or bearer authentication, JSON field assertions, self-signed certificates allowed per monitor.
- Regions and quorum
- Choose which regions check your service and how many must agree before an outage is declared.
- Confirmation threshold
- How many consecutive checks must fail before alerting: you choose the trade-off between speed and noise.
- Tags
- Group monitors by client, project or environment and filter them instantly.
- Monitor page
- Uptime over 24 hours, 7, 30 and 90 days, latency chart, latest results per region and status changes.
- Maintenance
- One-off or recurring windows (daily, weekly): no alarms, and uptime is calculated without them.
Reliability
How we avoid false alarms
A one-off error isn’t enough to wake you up: before opening an incident, MonitoraRE asks for confirmation. Here is what happens, for example, when an API stops responding.
-
1 eu-fra · 503
A check fails
The Frankfurt node gets an HTTP 503 from the API.
-
2 eu-fra · 503
It retries
The next check fails again: the confirmation threshold is reached.
-
3 eu-mil · 503
Another region agrees
The Milan node sees the problem too: the quorum is met.
-
4 incident opened
Incident and alerts
The incident opens, escalation starts and the status page updates.
Confirmation threshold and quorum are set per monitor.
MonitoraRE · now
Alerts and incidents
Every confirmed outage opens an incident and alerts the right people, in the right order.
- Notification channels
- Email, Slack, Microsoft Teams, Telegram, PagerDuty and webhooks to your own systems.
- Escalation
- Up to five levels: if nobody acknowledges within the set time, the next level is alerted.
- On-call
- Rotations across team members, with temporary cover for holidays and the unexpected.
- Anti-flapping
- An unstable service produces a single alert, then an update when it’s stable again.
- Acknowledgement
- Whoever steps in acknowledges the incident and stops the escalation, from the dashboard or via API.
- Timeline
- Detection, notifications sent, escalations, acknowledgement and recovery in a single timeline.
Status pages
Share the status of your services transparently, without exposing technical details.
- Components with public labels
- Show “Customer area”, not your server’s internal address.
- Custom domain
- status.yourdomain.com, with domain verification via a DNS record (Pro and Business).
- Branding
- Logo, accent colour and footer text.
- Subscriptions
- Your users get incident and recovery emails, with one-click unsubscribe.
- Private pages
- Password protected, for clients or internal teams.
- 90-day history
- Uptime per component, recent incidents and upcoming maintenance.
Team and security
Built for teamwork, with security switched on from the first login.
Sign in with a passkey
Face ID, Touch ID, Windows Hello or a FIDO2 key. Or an authenticator app. Two-factor authentication required for everyone, with passkeys or TOTP codes and recovery codes.
Who can do what
| Owner | Admin | Responder | Read-only | |
|---|---|---|---|---|
| View monitors and incidents | ||||
| Acknowledge, schedule maintenance | — | |||
| Configure monitors and status pages | — | — | ||
| Team, API and billing | — | — |
Audit log
Multiple organisations
One account to look after different clients, with separate data.
Reports and API
The numbers to prove your service quality, and the tools to automate.
- Monthly SLA report
- Uptime per monitor against the target you choose, downtime minutes, MTTA and MTTR.
- CSV export
- SLA reports and audit log ready to download for your clients or your accounts.
- REST API
- Monitors, incidents, maintenance, status pages and reports via API, with an OpenAPI 3.1 specification.
- Scoped tokens
- Read-only or write tokens, with expiry, revocable at any time.
Notifications where you already work
Start monitoring in minutes
Create your account, add your first monitor and choose who to alert.
Create a free accountFree forever plan · no credit card · 5 monitors included