Freshping shut down — where to move your checks

Freshping is gone. Freshworks disabled free accounts on 6 March 2026 as part of narrowing its portfolio to Freshdesk and Freshservice, and the stored data was deleted about 90 days after that. There is no replacement product from Freshworks and they did not name a successor — the advice was to find another monitoring tool.

If you are reading this because your checks stopped and nobody told you, that is the situation. This page is about where to go, and it is not only an argument for us.

What Freshping did well, and what to look for instead

Freshping's appeal was simple: 50 monitors at a 1-minute interval, free, with a status page, from a company large enough that it felt safe. That combination is hard to replace exactly. When you pick a successor, the thing worth checking is the one Freshping taught everybody the hard way: what happens to you when the vendor loses interest.

• A paid plan you are actually on is a commitment in both directions. A free tier is a favour that can

be withdrawn, as this shut down demonstrated.

• Open source cannot be sunset out from under you. If that is the lesson you took, Uptime Kuma is

free, self-hosts in one container, and nobody can take it away. It is a genuinely good answer and we compare ourselves to it honestly.

• If you want the closest free-tier shape to Freshping's, UptimeRobot gives 50 monitors at 5

minutes free, and Hyperping gives 20 at 5 minutes. Both are more generous than our 10.

We would rather say that plainly than pretend the only route out of a shutdown is towards us.

Where we fit

Uplance is a paid product with a free tier of 10 monitors at a 3-minute interval, 30 days of history and a status page. Smaller than what you had. What you get for the trade:

• Fifteen check types, including several Freshping never had: Minecraft server list ping,

Steam/Source A2S queries, FiveM, Discord bot presence through a real gateway connection, Postgres/MySQL/Redis with a real authenticated query, and mail blocklists.

• Proof the alert arrived. Every alert is written to an outbox before it is sent and retried for

about fifty minutes; once a week a real test event goes through every channel you configured and you are told which ones failed; the dashboard says "Alerts are at risk" when delivery is degraded; and /api/health returns 503 if our own checker stops, so an outside watchdog can page you.

• Alerts through your own Discord bot, under your name and avatar, with "I'm on it", "Mute 1 h" and

"Resolve" on the message.

• A status page with 90-day uptime bars, on your own domain from Pro (€19/month).

Moving over

There is no Freshping export to import from any more — the data was deleted in June 2026 — so this is a re-entry rather than a migration. Practical order:

1. List the URLs you were watching. If you no longer have them, your DNS zone and your load balancer

config between them usually reconstruct the list.

1. Add them. On the free plan, 10 monitors at 3 minutes; there is a bulk endpoint in the

API if you have many.

1. Configure your alert channels, then wait for the first weekly drill and read the result. That

report is the reason to pick a monitor, and it is the thing Freshping never showed you.

1. Put a heartbeat on anything scheduled — the checks that fail silently are the ones nobody notices

are missing.

One thing to do regardless of where you go

Whatever you move to, test the alerting before you need it. Break something on purpose, or mute a channel and see whether anyone notices. Freshping's shutdown was announced; the outage where your alert quietly fails to send will not be.