nabz watches your websites, APIs, servers, DNS, and scheduled jobs — checking from more than one region, agreeing across zones before it calls anything down, and paging you on Slack, Telegram, email, and more the moment it happens. Built for people who run their own things.
No signup — watch it work, then create an account to keep it. Free during beta.
Point nabz at whatever you run — a URL, a host and port, a DNS name, or a scheduled job — and it watches the details that matter, not just up or down.
HTTP/HTTPS checks with a full DNS → connect → TLS → first-byte timing breakdown, status codes, response-body keyword checks, and a heads-up before either a TLS certificate or the domain registration expires.
Is a TCP port open, and how fast does it connect? Plus ping-style reachability for the hosts behind your services.
Check that a name resolves to the answer you expect — A / AAAA / CNAME / MX / TXT / NS — from the system resolver or one you name.
Scheduled jobs check in to a private URL each run. If one goes quiet past its window, you hear about it.
A single checker on a bad network path will see failures that aren't real. nabz checks from several zones and only calls a monitor down when the zones agree. One flaky path doesn't wake you up.
Alerting doesn't hang off a single checker. And if an entire checking zone goes silent, nabz notices the missing heartbeat and tells you — so you're never left wondering whether it's your service that's down or the monitor itself.
Email, webhook, Slack, Telegram, Discord, and PagerDuty — and you can send a test to any of them with a click.
Page one channel first, then more if nobody acknowledges — so a missed alert doesn't become a missed outage.
Planned work shouldn't wake anyone. Schedule a window and checks keep running while alerts stay quiet.
Get warned when p95 latency creeps past a threshold you set — before slow turns into down.
A URL, a host and port, a DNS name, or a cron check-in — plus an interval. That's the setup.
nabz probes the endpoint on your interval, from more than one region at once.
The zones' results are combined — agreement, not a single reading, sets the status.
On an incident nabz pages your channels — Slack, Telegram, email, and more. When it recovers, you get the all-clear.
Not built yet — listed honestly so you know where it's headed.
Shareable uptime & incident history for a chosen set of monitors.
Manage monitors and pull status programmatically — for the people who automate everything.
SMTP / POP3 / IMAP reachability for the people running their own mail.
Free during beta.