¿Qué tan precisos somos?

La mayoría de los rastreadores de caídas no publican su precisión. Nosotros sí. Estos números se calculan en vivo desde nuestra base de monitoreo y se actualizan en tiempo real.

Acuerdo con proveedor

Con qué frecuencia nuestro veredicto coincide con la página oficial (últimos 30 min)

Tiempo medio de resolución

0 min

Duración media de incidencias en 30 días

Tasa de éxito de sondas

100.00%

622,556 comprobaciones en 24h

Regiones de monitoreo

Se requiere consenso multi-región para veredictos de caída

Servicios monitoreados

680

680 en el catálogo

Con estado del proveedor

144

Verificados contra páginas oficiales

Incidencias activas

0 abiertos en 24h

Reportes de la comunidad

Reportes de usuarios en 24h

Lo que hace precisos nuestros veredictos

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.

Limitaciones honestas

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.

API pública

Cualquiera puede obtener nuestro veredicto para cualquier servicio — sin auth, CORS abierto, caché de 30s.

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": [ ... ] }
}