TEKKNA PingPong · In production

[ PingPong · A product by TEKKNA ]

PingPong.

Uptime monitoring → incidents that close themselves

HTTP and TCP checks from Cloudflare’s edge, as often as every minute. A monitor that fails often enough opens an incident by itself, tells the people who need to know, and closes it again when the service recovers — with a status page that says what happened rather than a green tick that says nothing.

[ 01 ] — How it works

Checks that decide. Not a wall of graphs.

A monitor is one question — is this URL answering, is this port open — asked on a schedule you set. What matters is what happens when the answer changes, and that is the part PingPong does for you.

[ 01 ]

Checked from the edge.

HTTP(S) and TCP, run on Cloudflare’s network rather than from one box in one region — so an outage is your service being down, not our server being far away.

[ 02 ]

Down means down twice.

A monitor turns down only after several consecutive failures, which you choose. One dropped packet at three in the morning is not an incident and should not wake anybody.

[ 03 ]

Incidents that close themselves.

Going down opens one; recovering resolves it. Nobody has to remember to tidy up, so the incident list is a record of what happened rather than of who was diligent.

[ 04 ]

A status page that says something.

Public, plain, and showing the actual history — when it broke, how long for, and when it came back. A permanently green tick tells a customer nothing they can use.

[ 02 ] — Why we built it

We were the customer. Then we were the vendor.

PingPong replaced the monitoring we were paying for, on our own sites first. It watches this page, our clients’ sites, and the services behind them — which is a stronger claim than a testimonial, because you can check it.

[ 01 ]

EU-resident, end to end.

Checks, incidents and history stay on European infrastructure. If migrating away from non-EU providers is the point, the tool that watches the migration should not undo it.

[ 02 ]

No per-check meter.

Monitoring priced per check teaches you to monitor less, which is exactly backwards. Watch what you actually care about.

[ 03 ]

It tells the right people.

An incident reaches Slack where the team already is, rather than an inbox somebody reads on Monday.

[ 04 ]

Small on purpose.

Uptime monitoring is not a platform. It should answer one question well and stay out of the way the rest of the time.

[ 03 ] — Get in touch

Want it watching your services?

We run it for our own sites and for the clients we build for. If you would like it pointed at yours, say so and we will set it up with you.

stefan@tekkna.dev