3 days after launching Webhook Watch, I looked at the real numbers — not what I assumed, the actual ones.
62% of visitors are on mobile.
The site wasn't built with that in mind at all. I had to rework the dashboard tables, the navigation, resize everything so it stayed usable on a small screen. It's fixed now — because of that one number.
The other stat that stood out: 81% of visitors are from Guinea. That wasn't the plan — the tool is meant for any developer, anywhere — but if the local community is the one showing up first, maybe that's the community worth listening to first.
Webhook Watch watches your webhooks (Stripe, GitHub, your own API...): it tells you exactly when a delivery fails, retries automatically, and alerts you before your customer notices — no code changes needed on your side.
You can try it free here: https://webhook-watch.vercel.app
🔒 15 founding member spots, price locked for life, until September 30.
Top comments (1)
Reworking the tables because of that 62% number is the right call. One thing that helped me on mobile dashboards like this: collapse each delivery row to status, endpoint and time, and put the payload and retry history behind a tap. On a phone people mostly want to know "did it fail, and is it retrying?", not the body.
Curious where the Guinea traffic came from - one community post, or search? That tells you a lot about where to show up next.