Failures we've personally diagnosed
Our own WhatsApp bridge, today. It was 7 releases stale.
WhatsApp rejected every send with "Client outdated (405)" — and every health surface we had
kept reporting
ok:true the entire time. The owner got nothing for hours; nothing
we monitored told us. This page exists because that gap is exactly what it checks for.A session silently logs out. The bot process stays up, the API
keeps returning 200, and it quietly stops sending anything at all.
An endpoint returns HTTP 200 while blocking delivery. A
form-delivery API returned 200 on every call while its own JSON body said
success:"false" — the status code lied, only the body told the truth.Try it live — two real endpoints, one genuinely healthy, one silently broken
Both fixtures below report
ok:true. Click each and watch what the probe actually finds — it ignores the
ok flag entirely and checks the real delivery timestamp instead.
healthy-bot
A genuinely live target — its timestamp updates every request.
zombie-bot
Reports ok:true, but its timestamp is frozen — silently dead.
Try your own URL
Works today for any endpoint
that already exposes a JSON lastDelivered timestamp field — most health-check
or status endpoints don't yet, which is usually the actual finding. Paste one to see.
Pricing
$49 / month
One monitored bot/webhook. A probe on a schedule you set, an alert the moment delivery goes silent — not when the process dies, when it stops delivering.
- Send $49 via PayPal to
admin@deemwar.com(use "Send & Receive" / friends & family or goods — either works). - Tell us what to monitor: deemwar.com/contact — the URL or webhook, and what a "delivered" response from it looks like.
- We wire up the probe and confirm your first real alert within the hour. Prefer an invoice instead? Say so on the same contact form — Skydo invoice, same price.
Not ready to pay yet? Leave your email
Tell us what you'd want monitored and we'll follow up — no payment, no obligation.