Uptime monitoring for Netlify sites
Netlify tells you when a build fails. SitePulse tells you when a successful deploy breaks your site in production. External 1-minute probes on your production URLs, with email alerts when functions 500, redirects break, or SSL expires. Free for 5 monitors.
The deploy that looks green but isn't
You pushed a change. Netlify built and deployed successfully. But you forgot to set a new environment variable in the Netlify UI. Your serverless function now 500s on every request — and Netlify has no way to know, because the build succeeded.
SitePulse hits your function endpoints from outside Netlify's network every minute. The moment a probe gets a 500 instead of a 200, you get an email. You fix the env var and redeploy before any customer opens a support ticket.
What to monitor on a Netlify site
Production homepage
Your most important URL. Catches broken redirects, missing assets from botched deploys, and accidental 404s on the root path.
Netlify Functions
Monitor /.netlify/functions/your-function or your rewrite path. Function failures are invisible in Netlify's dashboard until you dig into logs.
Form submission endpoints
If you use Netlify Forms, monitor the page that triggers form submissions. A broken CORS header or missing form attribute silently kills your lead capture.
API routes (if using Next.js on Netlify)
Monitor /api/health plus your critical API routes. Netlify's Next.js runtime occasionally has cold-start issues that cause transient 500s.
SSL certificate
SitePulse checks your SSL cert on every probe and emails you 14 days before expiry. Custom domain certs on Netlify sometimes fail to auto-renew.
Public status page
Free SitePulse status page shows 30-day uptime history. Share with clients or embed in your docs. Builds trust and cuts 'is X down?' questions.
Set it up in 60 seconds
- Sign up — free, no credit card.
- Add your production custom domain (not the *.netlify.app URL).
- Add any Netlify Function endpoints your app depends on.
- Free plan: 5-minute checks. Pro: 1-minute checks ($9/mo).
- Done — email fires the moment any monitor goes red.
What you get
1-minute checks
On Pro plan ($9/mo). Free plan checks every 5 minutes — enough for most Netlify side projects.
SSL expiry alerts
14-day advance warning before your custom domain cert expires. Netlify's auto-renewal sometimes fails silently.
Public status page
Free on every plan. Show clients real uptime data instead of just saying 'everything's fine.'
Know the moment a Netlify deploy breaks production
5 monitors, 5-minute checks, email alerts, public status page — free forever. No credit card.
Frequently asked questions
Netlify has deploy notifications — why do I need SitePulse?+
Netlify notifies you when a build succeeds or fails. It doesn't notify you when a successfully deployed site breaks in production — a missing environment variable, a function that 500s on real payloads, or a redirect rule that accidentally routes all traffic to a 404. SitePulse probes your production URLs continuously and emails you the moment any probe returns an unexpected response.
How do I monitor Netlify Functions?+
Add a SitePulse monitor pointing at /.netlify/functions/your-function or your rewrite path (e.g. /api/your-endpoint). Use a GET request with any required headers. If the function starts returning 500 or timing out, SitePulse alerts you within a minute. For functions that require POST bodies, consider adding a dedicated GET health-check path that exercises the same code path.
My Netlify site is static — do I still need monitoring?+
For a purely static site with no functions: probably not for uptime (Netlify's CDN is very reliable). But SitePulse's SSL certificate expiry alerts are useful — if your custom domain cert lapses, Netlify won't renew it until your next deploy. And if you ever add a function or form submission, monitoring the functional parts matters.
What about Netlify Edge Functions?+
Edge functions run at the CDN level and are harder to monitor in isolation. The practical approach: monitor the URL that triggers your edge function and check that the response body or status matches what a healthy edge function returns. If the edge function starts failing, the response changes and SitePulse fires an alert.
How does SitePulse handle Netlify deploy previews?+
Don't monitor deploy preview URLs — they're ephemeral and get a new URL on every push. Monitor your production custom domain and your main branch deploy URL. Those are stable and represent what real users see.