Every 5 minutes
Each site is requested every five minutes from our servers. If a request fails it’s tried once more straight away, so a single dropped connection doesn’t wake you up.
Add a web address and Pingvella requests it every 5 minutes. When it errors, times out or stops answering, you’re alerted straight away, before your customers have to tell you.
Five website checks on every plan, including the free one.
No scripts and nothing to install. Give Pingvella the address of your site, API or health page, choose where alerts should go, and it starts straight away.
Each site is requested every five minutes from our servers. If a request fails it’s tried once more straight away, so a single dropped connection doesn’t wake you up.
Server errors, timeouts, refused connections, addresses that stop resolving and expired SSL certificates all count as down. A healthy site returns a 2xx response, after redirects.
Every request records how long the site took to answer, so a page that is slowly getting slower shows up in the run history long before it falls over.
Pause a check during planned maintenance, and resume it when you’re done. Pingvella requests the site again straight away, so you know it came back.
Pingvella needs an address that answers with a normal page when your site is up. Your homepage works, but a dedicated page keeps it simple and stops a busy page being fetched every few minutes. Download a ready-made one, upload it to your website, and add its address as the check.
pingvella-health-check.html to the root folder of your website.https://your-site.example/pingvella-health-check.html in a browser. You should see the words “Pingvella Health Check”.It’s a plain page that says “Pingvella Health Check” in the middle of the screen, and tells search engines not to index it. Because it’s a static file it proves your web server is answering, not that your application or database is working. To check those too, point the check at a page that uses them, such as a status route in your app.
Because Pingvella makes the request for you, it only ever requests public web addresses. Anything that points at a private network, a loopback address or a cloud provider’s internal service is refused, redirects are checked at every step, and credentials in a URL aren’t accepted. Pingvella can’t be used to probe your, or anyone else’s, internal systems.
For an internal site, run the request yourself and check in to Pingvella only when it succeeds. curl -f fails on any error response, so a broken site never checks in, and the silence raises the alert.
This uses a regular cron or heartbeat check, so it works for anything you can test from a script: APIs, queues, databases, login pages.
Yes. Add a website check with the address of your site or health page and Pingvella requests it every 5 minutes. A non-2xx response, a timeout or a connection or certificate error marks it down and sends your alerts, with a recovery notice when it is back. Every account can have five website checks. For sites that are not reachable from the internet, run the request from your own scheduler and check in only when it succeeds.
Every 5 minutes. If a request fails it is tried once more straight away, so a single dropped connection doesn’t raise a false alarm.
Anything other than a successful 2xx response once redirects are followed: an error page, a timeout, a refused or dropped connection, an expired or invalid SSL certificate, or an address that no longer resolves.
Not directly: Pingvella only requests public web addresses. For an internal site, run the request from your own server or scheduler and check in to Pingvella only when it succeeds. If the site stops answering, the check-ins stop and you are alerted.