Status
All systems operational.
Checked when you opened this page: the app, the database, the geocoder, map tiles and the jobs tick. Road distances aren't checked here, so that server can sleep between routes; each route shows whether it used real road distances or estimates. Reload to check again.
App
OperationalServing requests. The route planner runs in-process, so alive means it can plan.
Database
Operational485 msReachable; a round trip answered.
Geocoder
Operational601 msNominatim (nominatim.openstreetmap.org) answered in 601 ms. Probed at most every 5 minutes.
Map tiles
OperationalMapLibre with the style at tiles.openfreemap.org (OpenStreetMap data).
Road distances
On demandSelf-hosted OSRM (porch-route-osrm.fly.dev) sleeps when idle and wakes when a route is planned. We don't check it here so it can stay asleep. If it can't wake in time, routes use estimated distances, labeled as estimates.
Jobs tick
Operational529 mspg_cron fired the tick 5 min ago (every 5 minutes is normal).
What this page does and doesn’t tell you
Every line is a real check made on this request, except the geocoder, which is probed at most once every five minutes. Map tiles are a configuration check — browsers fetch tiles directly, so the only thing the server can vouch for is which tiles it points them at. Road distances on the self-hosted server aren’t checked here, so that server can sleep between routes. The line says “On demand”. If it can’t wake in time, routes use estimated distances, labeled as estimates — the app stays up. Production still on the public demo is marked down on purpose. The jobs tick is read from the database scheduler’s own run log where the tick is scheduled that way; where it isn’t, the line says “not tracked” rather than guessing.
There is no uptime history or incident log yet — that is on the roadmap. What changed recently is on the changelog; how the service is protected is on the security page.