Status of the
services.
Uptime, latency, and error budget for the services I run, measured every few minutes by my own monitoring infrastructure. Real data, no touch-ups.
DobleYo Café
OperationalTLS · 51dlast checked 1 min agoGorillaz Motorbikes
OperationalTLS · 83dlast checked 1 min agoGrupofamaro
OperationalTLS · 57dlast checked 1 min agoMinimarket
OperationalTLS · 38dlast checked 1 min agoPortal (página de login)
OperationalTLS · 45dlast checked 1 min agoPortal de clientes
OperationalTLS · 45dlast checked 1 min agoPortfolio (codebymike.net)
OperationalTLS · 45dlast checked 1 min agoSlideHub
OperationalTLS · 77dlast checked 1 min agoWeb Toledo Producciones
OperationalTLS · 53dlast checked 1 min agoSecurity Operations
Detected and blocked intrusion attempts, OWASP breakdown, and SLOs for my own security pipeline.
An external cron probes each service every few minutes: expected HTTP status, response content, latency, and TLS certificate. A 200 with the wrong page also counts as down.
The SLO is 99.5% availability over 30 days. The error budget is the downtime that objective allows; this shows how much is left. Latency is reported as average and p95 - the percentile a slow user actually feels, never just the average.
The whole system - check engine, incidents, SLOs, and alerts - is a custom tool built on top of this same site. The data is served exactly as measured.