Quelle est notre précision ?
La plupart des trackers de pannes ne publient pas leur propre précision. Nous, oui. Ces chiffres sont calculés en direct depuis notre base de monitoring et se mettent à jour en temps réel.
Concordance fournisseur
0%
À quelle fréquence notre verdict correspond à la page de statut officielle (30 dernières min)
Temps moyen de résolution
0 min
Durée moyenne des incidents sur 30 jours
Taux de réussite des sondes
100.00%
622,136 vérifications sur 24h
Régions de surveillance
4
Consensus multi-régions requis pour un verdict de panne
Services surveillés
680
680 dans le catalogue
Avec statut fournisseur
144
Croisés avec les pages de statut officielles
Incidents actifs
0
0 ouverts en 24h
Signalements communauté
0
Signalements utilisateurs sur 24h
Ce qui rend nos verdicts précis
- 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.
Limites honnêtes
- 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 publique
Tout le monde peut récupérer notre verdict pour tout service suivi — sans auth, CORS ouvert, cache edge 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": [ ... ] }
}