Tallwatch is uptime monitoring that only pages you when an outage is real.
That sentence is carrying most of the product, so let me unpack the part that matters: "only when it is real." It is the whole reason Tallwatch exists.
I did not set out to build a monitoring company
I set out to stop getting paged for nothing.
If you have ever been on call, you know the pattern. Your phone goes off at 2am. You open the laptop, half awake, and the site is fine. It was fine the entire time. Some checking server on the other side of the world had a bad thirty seconds, decided your service was down, and woke you up to tell you about it.
Do that enough times and something quietly breaks. You stop trusting the alert. You start swiping it away before you are even properly awake. And the night a real outage finally lands, it looks exactly like all the false ones you have been ignoring.
This is not a fringe problem. In a 2025 survey of DevOps and SRE teams, two thirds of engineers admitted they had dismissed an alert without investigating it. Most teams said the majority of their alerts were false positives, and the average on-call engineer was fielding around 50 a week, only a handful of which needed a human at all.
So the bar for a new monitoring tool is not "can it detect a failure." Everything detects a failure. The bar is "can I trust it enough to get out of bed." That is the only thing Tallwatch is really designed around.
How it decides something is actually down
Most uptime checks run from one place, and a single location measures two things at once without being able to tell them apart: whether your site is down, and whether the network path between that one spot and your site is healthy. Usually those agree. Occasionally a slice of the internet in between has a bad minute, and that gets reported as your downtime.
Tallwatch checks each target from several regions and treats every result as a vote, not a verdict. An incident opens only when a configurable majority of those regions agree the target failed inside a short window. One region having a rough moment cannot page you, because the others outvote it.
We call this multi-region consensus, and here is the part I care about most: it is on every plan, including the free one. An alert is only worth having if you trust it, and trust is a strange thing to put behind a paywall.
What you actually get
Tallwatch is the whole on-call stack, not just a checker:
- Website and API monitoring over HTTP and HTTPS, with checks on status, latency, and what the response actually says.
- Alerts in the places you already live: email, Slack, Discord, Microsoft Teams, Telegram, PagerDuty, or a signed webhook. Seven channels.
- Webhooks you can shape with a template, so an incident lands in whatever internal tool you have built.
- On-call rotations and escalation, so the right person gets paged and, if nobody answers, the next person does.
- Status pages on your own domain, so customers can check for themselves instead of opening a ticket.
- Maintenance windows, so the deploy you scheduled does not page the whole team at midnight.
Who I built it for
Tallwatch is for people who have felt the 2am false alarm and decided they are done with it. Dev teams who outgrew a basic checker. Indie hackers running a side project that quietly matters. The backend and platform folks who carry the pager and care about signal quality more than another dashboard.
If you are technical, allergic to marketing language, and the type to check a claim before believing it, you are exactly who I have in mind.
The honest part
Tallwatch is pre-launch. It has rough edges, and I would rather say that plainly than pretend otherwise. The free tier is real, though, not a countdown. It includes multi-region consensus across three regions, minute-by-minute checks, on-call and escalation, and a status page on your own domain. No card, no trial clock.
If a pager you can actually trust sounds good, point Tallwatch at something you care about and watch how it behaves the next time one corner of the internet has a bad day.