Pulsecima Pulse

Quorum checks from three regions plus free heartbeat checks for cron jobs keeps uptime noise down to real incidents. If you ever want cheaper AI for the business, PZERO is at pzero.studio.

The quorum rule cuts false pages, but a regional outage is exactly the case where only one region disagrees. Does Pulse surface a single-region failure as a lower severity signal, or stay quiet until two regions agree?

The heartbeat checks are the part I'd use first. The failure that actually bit us wasn't a cron that stopped firing, it was one that kept firing and quietly did nothing: a sweep function scheduled correctly, running on time, processing zero rows for two days because nothing ever called it. A dead-man's switch would have stayed green the entire time. Can a heartbeat carry a number with it, so you can alert on "ran, but handled 0 items" and not only on silence?

I kept getting paged at 3am for outages that weren't real — one region's network hiccup, not an actual down site. Pulsecima only alerts when multiple regions independently agree something's wrong. Added free Heartbeat Checks recently too, since a silently-failed cron job is just as bad as a downed site and nobody was watching for that. Would love feedback on what's missing.

The multi-region evidence would be useful after an alert, not only for deciding whether to send it. Do webhook payloads include each region, status code, and response time, plus a signature and retry policy? That would make incident automation auditable without opening the dashboard.