Uptime, Core Web Vitals, and build-output monitoring for Next.js sites.
What breaks on Next.js sites
Common failure modes
ISR revalidation stuck on stale content
Edge runtime cold-start spikes after deploy
404s from missing dynamic route params
Image Optimization API throttling under traffic bursts
Where these sites usually run
Vercel
Netlify
AWS Amplify
self-hosted Node
How Lemwatch detects a Next.js stack
Lemwatch fingerprints your stack on the first check — for Next.js that means _next/static asset paths and x-powered-by: Next.js header. Once detected, the Next.js preset turns on the checks that matter for this stack and skips the ones that produce noise.