Skip to content

Migrate · RealUptime Monitor

Migrate from Freshping

Freshping is not being sunset; it is already gone. Freshworks disabled free accounts and stopped paid renewals on March 6, 2026, and permanently deleted whatever data was left after a 90-day retention window, around June 4, 2026. There is no dashboard left to log into and nothing left to export live. This page covers what a former Freshping user can still recover, and what setting up from scratch on RealUptime Monitor actually involves.

Full Freshping comparison

There is nothing left to export from Freshping today

Freshworks' own deprecation FAQ states the free plan was disabled and paid renewals stopped on March 6, 2026, and that any data still on the service was permanently deleted after a 90-day retention window, around June 4, 2026. That window has now closed. If you exported your configuration through the Freshping Public API before the March 6 disable date, that export is the only source of truth left; if you did not, there is nothing left to pull, and the list of URLs you were checking is whatever you remember or can reconstruct from your own incident history, alerting logs, or a browser bookmark folder.

Freshworks named no replacement product in that FAQ. It pointed departing customers only at the Public API (while it still worked) and told them to explore other monitoring services on their own -- which is the situation this page addresses.

Add your checks to RealUptime

RealUptime's importer (the dashboard's "Import them instead" link) is a live, API-key-based flow supporting UptimeRobot and StatusCake today, with no Freshping adapter in either case. But the reason nothing can be pulled in automatically here is simpler than that: there is no live Freshping account left for any importer to call. Re-adding each URL by hand, through the same add-check form every RealUptime Monitor check goes through, is the actual first step any move to any provider requires once a vendor has shut down -- not a limitation specific to this product.

Map each check type

Freshping's own documentation went offline with the rest of the product, so its check-type list below is drawn from third-party comparison write-ups rather than Freshping's own docs -- flagged the same way the full Freshping comparison flags its own unverifiable claims, rather than presented as directly sourced.

Feature mapping

Freshping check types, mapped to RealUptime Monitor

HTTP / HTTPS

http · Have

Per third-party comparison sources; unverifiable against Freshping's own docs.

TCP

tcp · Have

Per third-party comparison sources; unverifiable against Freshping's own docs.

ICMP (ping)

ping · Have

Per third-party comparison sources; unverifiable against Freshping's own docs.

DNS

dns · Have

Per third-party comparison sources; unverifiable against Freshping's own docs.

WebSocket

No equivalent · Don’t have

RealUptime has no WebSocket check type today.

UDP

No equivalent · Don’t have

RealUptime has no UDP check type today.

(none: third-party sources report Freshping had no heartbeat checks)

heartbeat · Don’t have

RealUptime's heartbeat checks (for cron jobs and background workers pinging in) have no Freshping equivalent, per third-party comparison sources.

Not covered here: Freshping's hosted public status pages, which went offline with the rest of the product on March 6, 2026. RealUptime Status covers the status-page half, bundled with monitoring on every plan (see the full comparison linked below).

Verified August 29, 2026. Sources: Freshworks: Freshping deprecation frequently asked questions, Better Stack: Freshping check-type overview (third-party, Freshping's own docs are offline).

Ready to move your checks over?

For the full, sourced pricing and feature comparison against Freshping, see Full Freshping comparison. For why a check should run from more than one region at all, see why a status page can show all green during a real outage.