Upclock
Uptime Monitoring, your CEO would love.
Start new thread

Upclock - Uptime Monitoring, your CEO would love.

byβ€’
Know before your users do. Upclock checks HTTP, TCP, DNS, and ICMP endpoints down to every 10 seconds, opens incidents automatically, alerts your team, and publishes live real-time updating status pages. Free for 10 monitors.

Add a comment

Replies

Best
Maker
πŸ“Œ
Hey Product Hunt! πŸ‘‹ I'm Ayush, and I built Upclock. Every monitoring tool I tried was built for the engineer holding the pager. But the people asking "is everything up?" most often aren't engineers. They're your CEO glancing at the wallboard, and your customers wondering whether it's them or you. So I built Upclock around the part everyone else actually sees: the status page. It's real time by design. Live status, incident timeline, uptime history, and it updates the moment something changes, for everyone looking at it, with nobody hitting refresh. Clean enough to put on the office TV next to your revenue dashboard, and polished enough that sales can send it to a prospect without checking with you first. For B2B it does the things you actually need: your own custom domain, your branding, password-protected private pages scoped to a single customer, and email subscriptions so your customers hear about an incident from you rather than from their own users. Underneath is a real monitoring engine. HTTP, TCP, DNS and ICMP checks down to 10 second intervals, incidents opening automatically after a configurable number of consecutive failures, and alerts to email, Slack, ntfy and webhooks. Free tier is 10 monitors and a status page, no card. NEWUSER50 takes 50% off your first three months. I'd love feedback on the status page in particular: what would stop you from putting yours in front of a customer today?

The 10 second check interval is a nice touch, but it would be even more useful if you let users set custom check locations instead of defaulting to a single region. That way teams spread across different countries can catch outages that only affect specific geographies before their users do.

Maker

Thanks !

Multi-region probing is definitely next on the roadmap.

The nice part is that the underlying architecture was designed with this in mind from day one, so exposing custom probe locations should be as easy as firing up a few machines.

Beyond that, I also want to ship per-region latency and availability breakdowns, along with configurable quorum rules (e.g. only trigger an incident if 2 of 3 regions detect a failure) to reduce noise from localized routing or ISP issues.

I'm putting a lot of thought into getting these details right before rolling it out.