Why it happens
A cold function, a heavy page doing work on every request, or a redirect rule written with the wrong scheme.
How to tell
- Response time above the check's threshold, repeatedly.
- A redirect chain ending on http://.
The fix
- Find the slow route in the host's analytics; cache it, or move the work out of the request.
- Fix any redirect rule whose target is http://.
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
Profile my app's slowest routes and propose caching or moving work out of the request path for the top three. Also check my redirect rules and make every redirect target https.
How Keelnest catches it
Degraded is shown on your screens and never sent to anybody's inbox. It becomes an incident only if the site stops answering.
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.