Why it happens
A failed deploy, a crashed process, a database the app cannot reach, a host outage, or DNS. The first error in the logs says which.
How to tell
- Two consecutive failed checks, five minutes apart.
- The host's status page.
- A publish minutes before the first failure.
The fix
- Check the host's status page, then the first error in your logs.
- Roll back the last publish if it coincided.
- Confirm the database is reachable from the host.
- If it will take a while, declare maintenance so the response clock pauses and nobody is paged twice.
The prompt for your builder
Paste this into Lovable, Bolt, Cursor, Claude Code or whatever built the app. Replace anything in capitals. It never asks you to paste a secret into a chat; keys go into your host’s environment, by you.
Prompt for your builder
Add structured logging to my app's server entry so the first error at startup or on the first request is logged with its cause, and add a /api/health route that reports database connectivity so my host and my monitoring can tell a crashed app from a slow one.
How Keelnest catches it
Critical after the failure is seen on two consecutive checks, so a single blip never pages anyone; resolved after two good ones.
Know the moment this happens.
Keelnest watches your production app every five minutes and tells you in plain English what broke — with the fix. Free for your first app.