Switching from Freshping to Uptimely
Freshworks retired Freshping: its deprecation FAQ states free plan accounts were disabled on 6 March 2026, paid subscriptions were not renewed past that date, and account data is deleted 90 days after shutdown. It advises customers to migrate to an alternative monitoring tool. This page is the practical version of doing that — what each Freshping concept becomes here, what you gain, and the one place where Uptimely's free plan is plainly smaller than the one you lost.
Where things stand
Freshworks published a proper deprecation notice rather than going quiet, which is worth crediting, but the dates have passed. Free accounts were disabled on 6 March 2026 and the free-tier export window closed on 4 June 2026, with paid accounts' data deleted 90 days after the end of their term. Freshworks has offered no replacement product. If you can still sign in, export first; if you cannot, you are rebuilding from your own notes, and the good news is that a monitor is a URL and an interval.
Deciding rather than moving?
This page assumes you have already chosen to leave. Uptimely vs Freshping is the page that argues the choice itself, with every competitor figure sourced and dated, and all Uptimely comparisons lists the rest.
What maps to what
| Freshping | Uptimely | Notes |
|---|---|---|
| Check | Website or API monitor | A URL, an interval and an expected status code. 1-minute intervals on every plan, Free included — the same frequency Freshping's free plan gave you. |
| Check group | Project | Uptimely scopes monitors, status pages, incidents and on-call to a project, so a group becomes a project with its own members and alerting. |
| Public status page | Status page | One on Free, unlimited on Pro. Uptimely's adds subscribers, scheduled-maintenance windows, a custom domain and per-component response-time charts. |
| Email / Slack / Teams alerts | Alert channels | Slack, Discord, email, SMS, voice call and web push. Microsoft Teams is the one that does not carry over — its backend is dormant and the UI is hidden. |
| Alert recipients | On-call duty policy | A step up: rotations, escalation with delays and acknowledgement, on every plan. Freshping had no on-call concept at all. |
| Uptime reports | Uptime history and response-time charts | Per-monitor uptime over selectable windows, plus the heartbeat strip on the status page itself. |
| — | Incidents, maintenance, telemetry and the /v1 API | No Freshping equivalent. The incident lifecycle, scheduled maintenance, OTLP logs/traces/metrics and the public REST API are all new ground on the free plan. |
What you gain
- 1-minute checks on the free plan — the same frequency Freshping gave away, which most free tiers in this market do not.
- On-call duty policies with escalation and acknowledgement, included on every plan, including Free.
- The full incident lifecycle and scheduled maintenance windows, with subscriber notifications, rather than a page that only shows a colour.
- A status page with subscribers and a custom domain on the $0 plan, and unlimited status pages on Pro at $29/month.
- A public /v1 REST API with an OpenAPI 3.1 schema, an npm SDK and an MCP server — Freshping had no monitor-management API.
- OpenTelemetry ingestion (OTLP logs, traces and metrics) and a Prometheus /metrics endpoint.
- A product with an active roadmap. The reason you are reading this page is that the last one did not have one.
What Uptimely does not do
- Uptimely's free plan is 10 monitors. Freshping's was 50, and no free plan in this market replaces that one-for-one. If raw free monitor count is what you need, UptimeRobot's free plan is 50 monitors at 5-minute checks and is the fairer place to look — we would rather point you there than pretend the numbers match.
- Uptimely probes from ONE vantage point, where Freshping checked from several regions. A second vantage is on the roadmap and is not shipped. The compensation is temporal rather than spatial: a monitor declares an incident only after consecutive failed checks, each independently re-confirmed, with infrastructure-class failures gated against a live egress health check.
- The Freshping importer only helps if you already have a file. It reads the JSON Freshping's v1 API served, and that API is no longer served — so it converts an export you saved while the service was up, not one you can go and fetch now. Freshping's XML export is deliberately not parsed: its element names are documented nowhere, and a parser written against a guessed schema would half-succeed in silence. Without a file, monitors are re-created through the wizard.
- Microsoft Teams is not a live alert channel here. Slack and Discord are.
How to move
- If you can still sign in to Freshping, export your check list first. If you cannot, write down the URLs and intervals from memory or from your own monitoring notes — that list is the whole migration.
- Try it without signing up: Uptimely runs in guest mode, so you can create a monitor, watch it probe and publish a status page before you make an account.
- Bring your checks over, most-important first. A saved Freshping API export goes into Monitors → Import and export, which converts it and shows you the plan before writing; otherwise the wizard takes a URL and an interval. The free plan holds 10, and an import that would exceed that is refused whole rather than half-applied, so start with the ones whose failure you would want to be woken for.
- Publish the status page and point your existing status subdomain at it — custom domains are on the free plan.
- Set up an on-call duty policy. This is the part Freshping had no answer for, and it is the reason a 10-monitor plan can be worth more than a 50-monitor one.
The deprecation dates, the deletion window and the recommendation to migrate are quoted from Freshworks' own deprecation FAQ: https://support.freshping.io/support/solutions/articles/50000011808-freshping-deprecation-frequently-asked-questions — read 2026-09-02. Freshping's plan figures (50 checks, 1-minute intervals, alert channels) are third-party sourced, because Freshping's own pricing and feature pages are no longer served. Uptimely figures reflect its current plans.
Uptimely's Free plan has 10 monitors, 1 status page and 1-minute checks, with no credit card. Pro comes with a 14-day free trial.
Start free →Is Freshping really gone?
Freshworks' deprecation FAQ states that free plan accounts were disabled on 6 March 2026 and that paid subscriptions were not renewed from that date, running only to the end of their term, with no new features or major updates in the meantime. It recommends migrating to an alternative monitoring tool. Freshworks has not offered a replacement product.
Can I still export my Freshping data?
Probably not. The FAQ set the free-tier export deadline at 4 June 2026 and states that data is deleted 90 days after account shutdown, with the equivalent window for paid accounts running 90 days past the end of the subscription. If you still have access, export before you do anything else.
Does Uptimely's free plan match Freshping's?
Not on monitor count. Freshping's free plan was 50 checks and Uptimely's is 10, with 1 status page and 3 team members — that is a real reduction and we are not going to bury it. On everything else the free plan is larger: 1-minute checks, a status page with subscribers and a custom domain, the full incident lifecycle, on-call escalation, scheduled maintenance, a public REST API and OpenTelemetry ingestion, none of which Freshping's free plan included.
What if I just want 50 free checks again?
Then UptimeRobot's free plan is the honest recommendation — 50 monitors, no card, at 5-minute intervals rather than 1-minute. Uptimely's own comparison page with UptimeRobot lays out where each one wins. Come back when you need on-call, status pages or an API alongside the checks, because that is the trade the free plans are actually making.
How do I move my checks over?
If you saved a Freshping API check export while the service was still up, drop the JSON into Monitors → Import and export. It is converted to monitors and previewed entry by entry — created, skipped as a duplicate, or named as something that could not come across in full — and nothing is written until you confirm. Freshping's XML export is not read: its element names are documented nowhere, so a parser for it would be a guess that fails quietly. Without a file it is the wizard for a handful, or the public /v1 REST API and the @uptimely/sdk package for more.
Does Uptimely check from multiple regions like Freshping did?
No. Uptimely probes from a single vantage point today, and a second network is on the roadmap rather than shipped, so for a Freshping user this is a step down. What it does instead is make one vantage trustworthy: a monitor declares an incident only after consecutive failed checks, each of which is independently re-confirmed, and failures that look like our own network rather than yours are gated against a live egress health check before anything pages you.