Live Engineering Lab
Fleet Status
Real HTTP checks of the lans.cloud production fleet, run by this site's own worker — on visitor demand from the lab, plus an automatic sweep every 10 minutes. Every service below is something I built and operate myself, from this portfolio to the shop and the analytics stack.
How to read a card: each bar in the strip is one sweep across the last 24 hours — green means the service answered with a healthy HTTP status, red means an error or no answer (hover a bar for the exact time and result). The line underneath is response time over the same window, and “uptime” is simply healthy checks divided by all checks.
Every number is real
A BullMQ worker (concurrency 1) behind the Live Engineering Lab sweeps all 7 services every 10 minutes, resolving via public DNS (1.1.1.1/8.8.8.8) to dodge the host's split-horizon aliases. Each sweep lands in a bounded Redis ring buffer — the last 288 sweeps, about 48 hours at the scheduled cadence — safe under noeviction. This page reads that buffer live: no mocks, no cached screenshots.
One honest caveat: the checks originate from the same VPS the fleet runs on, so the latencies measure server-side response time — TLS, Traefik routing, and each app doing real work — not what a visitor on another continent would see. That's a deliberate trade-off: it keeps the numbers about the software, not the network between you and it.
Powered by the same BullMQ worker behind the Live Engineering Lab. Every number is a real measurement — nothing is simulated.