Monitoring Accuracy & Detection Tracking
Learn how StatusPage measures detection speed, tracks confirmations, and surfaces accuracy metrics so you can trust incident timelines.
Key Concepts
- Detection tracking: Records
detected_at,confirmed_at, anddetection_delay_msfor each incident - Quorum-based confirmation: Multiple locations must agree before an incident is confirmed
- Adaptive post-incident monitoring: Optional 15s checks for 5 minutes after recovery (paid plans)
How Detection Tracking Works
- A region detects a failure and logs detected_at
- Additional regions confirm the issue; when quorum is reached, confirmed_at is set
- The delay between the two is detection_delay_ms, which you can monitor over time
This prevents single-region blips from triggering false incidents.
Metrics & Dashboard
- Metrics endpoint:
/metrics/monitoring(IP-restricted) - Key signals:
adaptive_mode_count— monitors currently in the adaptive windowavg_detection_delay_ms— average detection delay over 24hdetection_delay_percentiles— p50 / p90 / p99 delaysmonitors_by_interval— breakdown of intervals in use
Use these to spot slow detections and tune intervals or locations.
Improving Accuracy
| Tuning | Why it helps |
|---|---|
| Add regions | Single-region issues won’t create false alerts |
| Shorten base interval (plan limits apply) | Faster first detection |
| Enable adaptive mode (paid) | Faster re-detection right after recovery |
| Set confirmation thresholds | Avoid flapping alerts from brief blips |
Related settings live in Monitors → Edit.
Plan Notes
- Adaptive monitoring requires Pro, Growth, Business, or Enterprise
- Detection tracking is available across plans, but shorter base intervals may be plan-limited
Troubleshooting
- High detection_delay_ms: Consider shorter intervals or more locations
- No detection data: Older incidents (pre-feature) won’t have tracking fields
- Adaptive not available: Check your plan or see the adaptive article below