Pingeko: give the alert a next step

An uptime check is half of a monitoring setup. The other half is what happens when it fails: which channel receives the signal, whether that channel was ever tested, and who is expected to look. A monitor can be configured with care and still alert into an inbox nobody reads.

A small monitor with a deliberate shape

Pingeko is a small uptime monitoring product owned by VMCSoft Digital and published and operated by ViWeb Technology. It is free, with its limits stated up front: up to five monitors with five-minute checks, one email channel and one webhook channel. You sign in with GitHub, create a monitor for a site or endpoint you own or administer, attach a channel, and verify that the route actually delivers before you depend on it. The dashboard shows monitors, channels and incidents and not much else.

That shape is intentional. Five monitors can cover a public site, an API health endpoint, a status page and a couple of critical dependencies. Verifying the route before you rely on it confirms that the address is right and that a test message arrives there. It does not guarantee that anyone reads the next real alert, which is why the rest of the setup is about people.

Decide who investigates before the first incident

An illustrative case: a two-person team runs a product site and an API. They add both to Pingeko, point the email channel at a shared address and the webhook at an incoming-webhook endpoint for the chat tool they already use. Pingeko sends a generic webhook; wiring it into a particular tool is their side of the integration to set up and maintain. The remaining decision is not technical. When an incident opens at two in the morning, who looks, and what do they check first? Writing that down next to the monitor, even as one line, is the step that makes the alert useful. Pingeko supplies the signal and a verified place for it to land. The owner and the next step come from you.

Read the limits as limits

Five-minute checks are not continuous observation, and they are not a promise that a failure is detected or resolved within five minutes. Pingeko’s terms describe it as an early free service in a proof-of-concept and beta period, provided as-is. Checks, queue dispatch and alert delivery can be slowed or reduced when the service is under load, when an upstream provider has an incident or during abuse handling, and the data itself can arrive late, incomplete or not at all. The terms ask you not to make it your only incident detection system, and that is the right way to use it: one clear signal beside your platform’s own health checks and logs, not a staffed response service. Monitor only endpoints you own, administer or are authorized to test.

The numbers on the homepage dashboard preview show what the product looks like. They are not a record of anyone’s uptime.

If you run a site that matters and nothing is watching it, Pingeko gives you a check and a verified channel at no cost. Add the monitor, confirm the route delivers, then write down who answers it.