If you've ever had a user tell you "your site is down" before you knew about it yourself, you know the problem. You need uptime monitoring, something that checks your site automatically and tells you the moment it stops responding.
The good news: setting this up takes about 5 minutes and you can do it for free.
What uptime monitoring actually does
An uptime monitor makes an HTTP request to your URL on a schedule, every 30 seconds, every minute, every 5 minutes, depending on your plan. If the server doesn't respond, or responds with an error code, it sends you an alert.
That's it. No agents to install, no code to deploy. You just give it a URL and it watches it.
Step 1: Sign up and add your first monitor
Go to app.pingvault.live and create a free account. The Hobby plan is free forever with 50 monitors, no credit card needed.
Once you're in, click Add Monitor and enter:
- URL, your homepage, API endpoint, or any URL you want to watch
- Check interval, how often to check (5 minutes on Hobby, 1 minute on Pro)
- Alert channels, where to send alerts (email, Slack, Discord)
Save it. PingVault will start checking immediately.
Step 2: Add your alert channel
Email alerts are on by default. If you want Slack or Discord alerts (recommended, you'll actually see them), go to Settings and paste in your webhook URL.
For Slack: create a new incoming webhook in your Slack workspace app settings, copy the URL, and paste it into PingVault.
For Discord: right-click any channel → Edit Channel → Integrations → Webhooks → New Webhook. Copy the URL and paste it into PingVault.
Step 3: Monitor your most critical endpoints
Don't just monitor your homepage. Think about what would actually hurt if it broke:
- Your login or signup endpoint
- Your main API endpoint
- Any webhook receiver
- Payment or checkout URLs
Each of these should have its own monitor. On the free plan you get 50 monitors, more than enough to cover all critical paths for a small SaaS.
Step 4: Set up SSL certificate monitoring
While you're at it, PingVault also tracks SSL certificate expiry. If your cert is about to expire, it alerts you before your site starts throwing browser warnings. This is included automatically, no extra setup needed.
Step 5: Create a status page (optional, but worth it)
On the Pro plan, you can create a public status page that shows your uptime history. This gives your users a place to check when something seems wrong, rather than emailing you.
A status page also shows you're professional about reliability, it's a trust signal, not just a utility.
What to do when you get an alert
When a monitor fires, PingVault sends you the URL that failed, the HTTP status code (or "no response"), and the timestamp. That's usually enough to start debugging.
Common causes:
- Server crash or OOM, check your hosting dashboard or logs
- Deployment that broke something, roll back or fix forward
- Database connection timeout, check DB health and connection pool
- DNS or CDN issue, check your DNS records and CDN status
- Expired SSL cert, PingVault will have warned you about this one in advance
Uptime monitoring is one of those things that takes 5 minutes to set up but saves you hours when something goes wrong. The free plan is enough for most indie projects. You can always upgrade later if you need faster checks or more monitors.