rimetry logo — outage monitoringrimetry
Back

How accurate are we?

Most outage trackers don't publish their own accuracy. We do. These numbers are computed live from our monitoring database — they update as our system runs.

Vendor agreement
0%
How often our verdict matches the service's own status page (last 30 min)
Avg time to resolve
0 min
Mean incident duration over the last 30 days
Probe success rate
100.00%
622,424 checks in 24h
Monitoring regions
4
Multi-region consensus required for outage verdicts
Services monitored
680
680 in catalog
With vendor status
144
Cross-checked against official status pages
Active incidents
0
0 opened in 24h
Community reports
0
User-submitted reports in 24h

What makes our verdicts accurate

  • Multi-region consensus. No single probe ever decides an outage. A failure in one region with others healthy is treated as probe noise.
  • Persistence gate. An incident is only opened if the same region fails across ≥2 consecutive rounds — kills false positives from transient blips.
  • Vendor status ingestion. We pull the official status page (Statuspage.io, Slack, Heroku) every 2 minutes and weight it as the highest-trust signal.
  • Body fingerprinting. A 200-OK maintenance page is not "up." We verify expected HTML markers and detect known failure patterns.
  • Community signal engine. User reports are baseline-compared (5× normal volume + ≥3 countries triggers escalation), with anti-spam scoring.
  • Verdict explainability. Every service page shows exactly which signals drove the current status. No black box.

Honest limitations

  • Our probes run from cloud datacenters. Some vendors rate-limit those IPs, which can show as latency we'd never see from a real user. We compensate with retries and baseline learning.
  • We can't see inside a service — payment failures, login outages, regional CDN issues for end-user IPs are partly inferred from community reports.
  • Status page agreement is a quality signal, not ground truth. Vendors sometimes report green during real outages.

 

Public API

Anyone can pull our verdict for any tracked service — no auth, CORS-open, 30s edge cache.

GET /api/public/v1/status/<slug>{
  "service":   { "slug": "...", "name": "...", "domain": "..." },
  "status":    "online | slow | degraded | partial_outage | down",
  "confidence": { "confidence": 0-100, "message": "..." },
  "health":     { "score": 0-100, "label": "Excellent | ..." },
  "dns":        { "ok": true },
  "tls":        { "expires_at": "ISO" },
  "vendor":     { "status": "...", "checked_at": "ISO" },
  "verdict":    { "reasons": [ ... ] }
}