Netlify uptime monitoring with outside checks and downtime alerts every 30 seconds
Short answer: Netlify tells you when a deploy starts, succeeds or fails. It does not tell you that your live site returns errors, that a function is failing, that a redirect rule broke checkout or that your custom domain stopped resolving. To know within seconds that a Netlify site stopped serving customers, you need a check that runs from outside Netlify and pages a person.
Netlify behavior checked against docs.netlify.com
alertping ▸ check preview
simulated
▸ type a domain to watch a check and an alert play out
▸ simulation of 3 regions · US East · EU Central · EU East
▸ waiting…▌
queued
probing▌
If ever goes down, you get:
Alert fired ▸ 2 channels · 6.2 s after first failure
AlertPing app
● DOWN : HTTP timeout confirmed from 3/3 regions (US East, EU Central, EU East). Incident opened.
sms · on-call
AlertPing: DOWN. Confirmed 3/3 regions . First fail: EU Central.
Simulation, not a measurement of your site: this preview runs entirely in your browser and the latencies are generated from the domain you typed. Real checks on your monitors run from our US East, EU Central and EU East regions.
read this first
A deploy notification is not an uptime monitor
Netlify documents its notifications clearly. You can send events to Slack, to an email address (available on Pro and Enterprise plans) or to any URL as a webhook. The events cover the deploy lifecycle: started, succeeded, failed, locked, restored, and a previously successful deploy that failed. Those are build and publish events.
They answer whether Netlify finished putting your files on its CDN. They do not answer whether a customer can load your pricing page right now. A deploy can succeed and still ship a page that throws a JavaScript error, a function that returns 500, or a redirect that sends every visitor in a loop. Nothing in the deploy notification list visits your public domain from outside and alerts you when it fails.
If you run a marketing site, a storefront or a SaaS front end on Netlify, the gap is concrete: the first person to notice is usually a customer.
the honest table
What Netlify catches and what only an outside check catches
| Failure | Netlify on its own | AlertPing from outside |
|---|---|---|
| A deploy fails to build | Yes, deploy failed notification, old version keeps serving | Not its job, use Netlify |
| A deploy succeeds but ships a broken page | No, the deploy counts as succeeded | Yes, with response assertions |
| A Netlify Function returns 500s | Only if you read function logs | Yes, checked every 30 seconds |
| A redirect or rewrite rule loops or hits the wrong target | No | Yes |
| Custom domain DNS breaks or the domain lapses | No | Yes |
| TLS certificate fails on a custom domain | No | Yes, with days of warning |
| A proxied API behind your site goes down | No | Yes, check the API route directly |
| Failure confirmed from a second region before paging | No | Yes, three regions |
Keep the Netlify deploy notifications for the build pipeline. Add an outside check for the question customers actually care about, which is whether the page loads and the function answers.
the mechanics
Setting up outside monitoring for a Netlify site
Step one, add your custom domain rather than the netlify.app address, so DNS and certificate failures are in scope. Step two, add a check for every route that earns money: the checkout or signup page, and each Netlify Function or proxied API the page needs. Step three, assert on a string in the response and on response time, not only the status code, because a redirect or a cached error page can return 200 for a broken site.
Step four, choose 30-second checks for anything customer-facing, confirmed from a second region before it counts as downtime, so a single network blip does not wake anyone. Step five, route alerts to SMS and Slack. SMS, email, Slack and webhook alerts are included on every AlertPing plan with no credit packs. Nothing is installed in your Netlify account and no code changes are needed.
Run a check right after each production deploy too. The deploy notification says the build landed, and the outside check says the site still works.
who needs this
Which Netlify teams need this
Agencies hosting client sites on Netlify, where a broken contact form or a failed redirect becomes a call from the client. Ecommerce and lead generation sites where an hour of downtime costs real orders. Product teams serving a SaaS front end from Netlify with functions behind it. If a missed outage costs you more than a monitoring plan, you are the reader this page is for.
scope
What AlertPing does not replace on Netlify
AlertPing does not read your build logs, deploy previews or function logs, and it does not replace Netlify deploy notifications for your build pipeline. It watches the public side: the URLs your customers and integrations call, how fast they answer and whether the certificate is healthy.
questions people ask
Netlify uptime monitoring questions
Does Netlify have uptime monitoring?
Not as an outside check of your live site. Netlify sends deploy notifications for events such as a failed deploy or a deploy that succeeded, through Slack, email on Pro and Enterprise plans, or a webhook. None of those visit your custom domain on a schedule and alert you when real requests fail.
How do I get alerted when my Netlify site goes down?
Point an external monitor at your custom domain, add checks for the routes that matter such as a Netlify Function or a proxied API, assert on a known response string, confirm failures from more than one region and send the alert to SMS or Slack. AlertPing does this every 30 seconds without changes to your Netlify account.
Does a successful Netlify deploy mean my site is working?
No. A deploy succeeds when Netlify finishes uploading it to the CDN. It says nothing about whether a function returns errors, a redirect loops or a third party API your pages depend on has failed. An outside check after every deploy catches what the build cannot.
Can AlertPing monitor a Netlify Function?
Yes. A function is reachable at a public URL, so AlertPing can request it every 30 seconds, assert on the status code and a string in the response, and alert you on a failure confirmed from a second region.
Can AlertPing monitor a custom domain on Netlify?
Yes, and you should. Monitoring the custom domain covers DNS changes, certificate renewal and the full path a customer takes, which the netlify.app address skips.
Watch your Netlify site from outside Netlify
AlertPing checks your custom domains, functions and API routes as often as every 30 seconds, confirms every failure from a second region, warns before your SSL certificate expires, and sends SMS, email, Slack and webhook alerts on every plan. Flat pricing from $49 a month, with 30-second checks from $59.