Global multi-region checks for more reliable alerts
Built for teams that want fewer false alarms and faster confirmation.
Verify outages from multiple locations before you escalate, separate regional network issues from real downtime, and see how your service behaves across the world.
No More False Alarms
We verify downtime from multiple locations before waking you up.
Want the strategy behind quorum checks and regional validation? Read the University uptime monitoring guides.
Global Coverage
Primary checks from Munich, with verification nodes across Europe, US, and Asia.
Double Verification
If one region fails, we check from others. It's only an incident if it fails globally.
Network Isolation
Distinguish between a local ISP outage and a real server crash.
Reliable Alerts
Trust your alerts. When we page you, it means there is a real problem.
Detection Tracking
Every incident records detection timing, confirmation delay, and accuracy metrics.
How Verification Works
Single-location monitoring is prone to false positives due to transient network issues. Our system solves this.
- Primary check fails (e.g., from Munich).
- System marks monitor as "Unconfirmed Down".
- Immediate requests are sent to verification nodes (e.g., Amsterdam, New York, Singapore).
- If verification nodes also fail, the monitor is marked "Down" and alerts are sent.
Beyond Basic Multi-Region Checks
Professional features that make a difference
Adaptive Post-Incident Monitoring
After a monitor recovers, adaptive mode kicks in automatically to catch flapping issues that often occur right after service restoration.
How it works:
- Monitor recovers from downtime
- Adaptive mode activates for 5 minutes
- Checks run every 15 seconds instead of normal interval
- Automatically returns to normal after window expires
Detection Accuracy & Metrics
Track exactly how fast incidents are detected and confirmed, with comprehensive metrics to help you optimize monitoring.
Tracked metrics:
detected_at– When first region noticed the issueconfirmed_at– When quorum was reacheddetection_delay_ms– Time between detection and confirmation- Performance percentiles (p50, p90, p99)
/metrics/monitoring endpoint.