Is the database accepting WRITES? 503 if not.

/health never touches the database, so on 2026-09-12 it stayed 200 for eight hours while a split-brained cluster refused every write and every authenticated request 500'd — and the public status page, which watches /health, said Operational. This is the endpoint that page should watch. Accepts HEAD because UptimeRobot's free tier can only send HEAD (a paid plan is needed to choose GET), and every /v1 route 405s on HEAD.

It reads two settings and writes nothing (no usage_logs row, no auth), so it is safe to poll and cannot itself fail on a read-only primary. A connection failure is also 503: the write address is not serving.