OneBuck.dev
Website Monitor
Website monitoring for $1 per site and region
One URL. One optional origin IP. Checks every 60 seconds. OneBuck.dev watches your site's uptime, latency, DNS and TLS, then emails or Slacks you the moment something breaks. No free tier, no seat math: one monitor slot costs exactly $1 per month.
One slot includes 1 URL, an optional origin IP, 1 monitoring region and 30 days of raw history. Reassign slots to different sites at any time from the dashboard.
What a check measures
- Uptime and HTTP status — GET request every 60 seconds; 2xx and 3xx count as up, 4xx and 5xx count as failed.
- Total latency — time to the first byte of the response.
- DNS — whether the hostname resolves, how long it takes, and whether the resolved addresses change.
- Connect and TLS — TCP connect time plus TLS handshake, hostname and certificate validity.
- Certificate expiry — alerts at 14, 7, 3 and 1 day remaining.
- Origin probe — optional direct check against an origin IP that bypasses DNS and any CDN, preserving the original hostname for HTTP Host and TLS SNI.
Current limits
| Check interval | 60 seconds |
|---|---|
| Request timeout | 30 seconds |
| Redirects followed | Up to 5, each re-resolved and re-validated |
| Down threshold | 2 consecutive failed checks |
| Recovery threshold | 1 successful check |
| History included | 30 days of raw history |
| Alerts | Email and Slack webhook |
| Live region | Singapore |
| Targets | Public Internet HTTP and HTTPS only |
India, Tokyo, Hong Kong, Sydney, Los Angeles, San Jose, Chicago, Ashburn, Toronto, Amsterdam and Frankfurt are on the roadmap. Telegram, Discord, generic webhooks, SMS and phone alerts are coming after email and Slack.
Setup
- Add the public URL you want to watch.
- Optionally add an origin IP to probe your server directly behind a CDN or load balancer.
- Pick a region (Singapore today) and an alert channel: email or a Slack webhook.
- Allocate a $1 monitor slot. The first check runs within a minute.
The active 60-second schedule lives in the OneBuck.dev scheduler and is rebuilt automatically on restart, so your monitor keeps running without a cron job on your side.
Common use cases
- Watch a marketing site, API endpoint or webhook receiver around the clock.
- Detect TLS certificate expiry before a browser does.
- Notice DNS address changes in real time.
- Compare public CDN status with a direct origin probe during an incident.
- Monitor the same site from multiple regions as you expand, one $1 slot at a time.
FAQ
What counts as one $1 monitor?
One slot covers 1 URL, an optional origin IP, 1 monitoring region and 30 days of raw history. Monitoring the same site from two regions uses two slots.
How fast do you detect downtime?
Checks run every 60 seconds. A first failure marks the monitor degraded, and a second consecutive failure marks it down and sends an alert, so detection is typically within one to two minutes.
Which alert channels are supported?
Email and Slack webhooks in V1. Telegram, Discord, generic webhooks, SMS and phone alerts are on the roadmap.
Can you monitor a site behind a CDN or WAF?
Yes. The default check follows the public URL. If you supply an origin IP, OneBuck.dev also connects directly to that IP while preserving the original hostname and SNI, so you can tell whether a problem is in the edge or the origin.
Can I keep more than 30 days of history?
Yes. Each additional 30 days of raw history for a monitor allocation costs another $1 per month.
Start monitoring for $1
Allocate a monitor slot from the dashboard, or head back to the shop to see every service.