Guide

How to monitor a Vercel deployment

Vercel handles deployments, edge functions, and CDN. But it doesn't tell you when your site is down for users in Singapore, or when your edge function is timing out from Europe. External monitoring fills that gap.

YOUR PRODUCTION URL

Monitor your live domain, not the Vercel URL

Create an HTTP monitor pointing at your production domain (e.g. https://yourapp.com), not the .vercel.app URL. You want to test what your users actually hit — including DNS, CDN routing, and edge function execution.

API ROUTES

Monitor your API routes separately

If you're using Vercel's API routes or serverless functions, monitor them independently. Your marketing page might be serving fine from the CDN cache while your /api/auth endpoint is throwing 500s. Create separate monitors for your critical API routes with keyword validation to verify the response body, not just the status code.

GLOBAL PERFORMANCE

See response times from every region

Vercel's analytics show you aggregate performance. Larm shows you response times from each probe location independently — Nuremberg, Virginia, Singapore, São Paulo. You can see if your edge function is fast in the US but slow in Asia, or if a specific region's CDN cache is stale. The full request waterfall (DNS, TCP, TLS, TTFB, transfer) pinpoints exactly which phase is slow.

SSL & STATUS PAGES

Certificate monitoring and status pages included

Larm monitors your SSL certificate and alerts you before it expires. Vercel auto-renews certificates, but auto-renewal can fail — DNS misconfiguration, domain transfer issues, rate limits. You also get a status page tied to your monitors that updates automatically when something goes down. Your users can check status without filing a support ticket.

Monitor your Vercel app from multiple continents.

Multi-probe voting, full request waterfall, SSL monitoring. Free to start.