Adapter-aware uptime checks and route-level monitoring for SvelteKit.
What breaks on SvelteKit sites
Common failure modes
Adapter mismatch between dev (node) and prod (edge)
+server.ts endpoints returning HTML on 404
CSRF rejection after hosting platform changes Origin header
Where these sites usually run
Vercel
Cloudflare Pages
Netlify
self-hosted Node
How Lemwatch detects a SvelteKit stack
Lemwatch fingerprints your stack on the first check — for SvelteKit that means /_app/immutable/ asset paths and sveltekit:data attributes. Once detected, the SvelteKit preset turns on the checks that matter for this stack and skips the ones that produce noise.