Uptime Monitoring
Monitor your sites and get alerted when they go down.
VibePing includes built-in uptime monitoring. It pings your URLs at regular intervals, records response times and status codes, and shows you when things go down. No separate tool needed — it's part of your dashboard.
How It Works
VibePing makes HTTP requests to your configured URLs on a schedule. For each check, it records:
- HTTP status code — the response code returned by your server
- Response time — how long the request took in milliseconds
- Timestamp — when the check ran
These results are stored and used to calculate uptime percentages, plot response time trends, and determine whether your site is currently up or down.
Adding Monitors
Go to Settings in your VibePing dashboard and find the uptime monitoring section. Add a URL you want to monitor — this can be your main site, an API endpoint, a webhook URL, or anything that responds to HTTP requests.
You can monitor multiple URLs per project. Each one is checked independently.
What Counts as "Down"
A URL is considered down if either:
- The response status code is not in the 2xx range (e.g., 500, 502, 503, 404)
- The request times out before getting a response
Redirects (301, 302) are automatically followed. Any final response with status < 400 counts as up.
Check Intervals
Checks run every 5 minutes via a Vercel cron job. This means:
- You'll know about outages within 5 minutes of them starting
- You get 288 data points per day per monitor
- Short blips (under 5 minutes) might not be caught
This interval is fixed in the current version. For most sites and side projects, 5-minute checks give you solid coverage without burning through resources.
Response Time Tracking
Every successful check records how long the request took. This gives you a response time history you can use to:
- Spot performance degradation before it becomes an outage
- See the impact of deployments on response time
- Identify slow periods (maybe your serverless functions have cold starts at 3 AM)
Response times are measured from the start of the HTTP request to receiving the full response. This includes DNS resolution, TLS handshake, and data transfer — the full round trip.
Uptime Percentage
VibePing calculates uptime as:
uptime % = (successful checks / total checks) × 100
A "successful check" is any check that returned a 2xx status code within the timeout window.
For context on what the numbers mean:
| Uptime | Downtime per month |
|---|---|
| 99.9% | ~43 minutes |
| 99.5% | ~3.6 hours |
| 99.0% | ~7.3 hours |
| 95.0% | ~36 hours |
If you're running a side project on a free tier, don't panic about 99.5%. If you're running a production SaaS, you probably want to be above 99.9%.
Dashboard Uptime Page
The uptime page in your dashboard shows:
- Current status — a clear up/down indicator for each monitored URL
- Response time chart — a time-series graph showing response times over the selected period
- Uptime history — the overall uptime percentage and a visual timeline of up/down periods
You can see at a glance if something is wrong, and drill into the timeline to find exactly when an outage started and ended.
Alerts
Coming soon: email alerts when a monitor detects downtime. You'll be able to configure who gets notified and set up rules like "only alert if the site is down for 2+ consecutive checks" to avoid noise from single failed checks.
For now, check your dashboard regularly — especially after deploys. The uptime page will show you any incidents you might have missed.
Tips
Monitor your actual user-facing URL, not just your API. If your CDN is down but your origin server is fine, monitoring the origin won't catch the problem your users are experiencing.
Add monitors for critical API endpoints too, not just your homepage. Your marketing site might be up while your /api/auth endpoint is returning 500s.
Check response time trends weekly. A gradual increase in response time often predicts an outage. If your average response time doubles over a week, something is going wrong — investigate before it becomes downtime.