Live data from Hacker News

Show HN: Peeng – like Pingdom, but the other way around and simpler

peeng.sh

31–40 of 79 posts

Re: Show HN: Peeng – like Pingdom, but the other way around and simpler

#31
post #26

Sounds like https://deadmanssnitch.com with a bigger free plan, or is there a fundamental difference?

This is the MVP which is not much different except a better UX (we hope). The next version gonna have lot of other things such as nested subdomains and status page per endpoint/subdomain.

Re: Show HN: Peeng – like Pingdom, but the other way around and simpler

#32

How does Peeng differentiate between 'pings' from different services coming from the same IP? Payload? For example, if I wanted to use this for an appserver and db server and both have a NAT gw as the source, would I need to separate Peeng domains or can Peeng operate on the payload?

[deleted]

Re: Show HN: Peeng – like Pingdom, but the other way around and simpler

#33
post #14

I don’t currently need something like this, but I like the simplicity and it seems handy. Tech aside, I’m compelled to say that I don’t like the name. It is one letter off from a bodily function, and the pronunciation is even closer. Edit: the menu button on the landing page doesn’t work for me on iOS.

seconded; calling it "pee-ng" will limit adoption

we are open to suggestions

Re: Show HN: Peeng – like Pingdom, but the other way around and simpler

#35

How does Peeng differentiate between 'pings' from different services coming from the same IP? Payload? For example, if I wanted to use this for an appserver and db server and both have a NAT gw as the source, would I need to separate Peeng domains or can Peeng operate on the payload?

You can send query params when hitting your subdomain. We keep those query params and can then display them to differentiate between requests (coming from a NAT gw) —- does that help?

Re: Show HN: Peeng – like Pingdom, but the other way around and simpler

#39

So you are basically making a dead man's switch, it seems [0]. However, why should I send requests to you rather than you pinging me? It saves on your server costs, sure, but it can be more of a hassle for me as the developer when I just want to know if my service is up. And definitely change your name, the first thing I though of was pee or peeing, not a good connection to have in people's minds. [0] https://en.wiki…

Wouldn’t this allow for health checking services that don’t have public endpoints? My first thought was an alert to me that my home internet (or server) is down.

Granted I’d probably just set up a server to do that unless this was insanely cheap.

Post reply on HN