← All guides

Freshping alternative — it shut down; free downtime alerts from one curl

If your Freshping dashboard stopped loading, your status page 404s, or the alerts just quietly stopped: Freshping was permanently retired by Freshworks on March 6, 2026. Monitoring stopped that day for free accounts, the data-export window closed roughly 90 days later, and freshping.io now just redirects to freshworks.com (we checked while writing this — September 2026). There is no Freshworks replacement product; their FAQ said "supporting Freshping is no longer part of our go forward plan" and recommended finding an alternative.

This page is two things: a quick, honest map of where ex-Freshping users can go — and a 60-second way to get the core loop back (URL checked from the edge → webhook when it goes down → webhook when it recovers → public status page + README badge) with one curl and no account, free.

1. What happened, briefly

The context: after a 2024 leadership change, Freshworks consolidated around Freshdesk and Freshservice, and a free monitoring tool with no revenue didn't survive the portfolio cleanup. If you're reading this after June 2026, your monitor configs and uptime history are unrecoverable — the rebuild below starts from the URL list in your head (or your old alert emails).

2. Honest first: nothing free matches what Freshping gave away

Freshping's free tier was reported at 50 monitors, 1-minute check intervals, 5 status pages with custom domains, and 10 global probe locations, plus ping/TCP/WebSocket-style check types. That combination doesn't exist for free anywhere today — including here. Part of why it doesn't exist is the lesson of this page: it cost real money to run and made none, and when priorities changed it vanished along with everyone's data. Calibrate accordingly: whatever you migrate to, prefer things that are either paid and sustainable, self-hosted and yours, or so simple that leaving takes a minute.

The replacement below is in the third category. It is deliberately small: HTTP GET checks every 30 minutes, webhook-only alerts, a minimal public status page. What it has that a dashboard product doesn't: no account, no migration, no lock-in — a monitor is one curl to create, one to inspect, one to delete.

3. The 60-second rebuild — one curl per URL

curl -X POST https://mockbird.mockbird.workers.dev/api/status/monitor \
  -H 'content-type: application/json' \
  -d '{"url":"https://api.example.com/health","notify":"https://hooks.slack.com/services/T000/B000/XXXX"}'

We GET your URL every 30 minutes from Cloudflare's network (8s timeout, redirects followed, 2xx/3xx = up). The response contains everything — your URL is probed immediately, and a confirmation delivery hits your webhook so you know the channel works before you rely on it:

{
  "id": "mon-XXXX",
  "secret": "…",
  "current": { "ok": true, "http_status": 200, "ms": 58 },
  "checked_every_minutes": 30,
  "status_page":  "https://mockbird.mockbird.workers.dev/status/mon-XXXX",
  "badge_svg":    "https://mockbird.mockbird.workers.dev/status/mon-XXXX/badge.svg",
  "feed_atom":    "https://mockbird.mockbird.workers.dev/status/mon-XXXX/feed.xml"
}

notify takes a Slack webhook, a Discord webhook, or any HTTPS endpoint — format sniffed from the host; everything that isn't Slack/Discord gets JSON signed with your monitor's secret (x-mockbird-signature: sha256=hex(hmac-sha256(secret, body)), verify it like a Stripe webhook). Alerting is deliberately quiet: one POST on down, one on recovery, debounced — two consecutive checks must agree, so a single blip never pages you.

4. Status pages and badges

Freshping's public status pages were a headline feature. Every monitor here gets a smaller version automatically: a public page at an unguessable URL showing the hostname, live state, 24h/7d OK-rate and recent down/recovered events — plus an embeddable SVG badge and an Atom feed of incidents. Drop the badge in a README:

[![api.example.com status](https://mockbird.mockbird.workers.dev/status/mon-XXXX/badge.svg)](https://mockbird.mockbird.workers.dev/status/mon-XXXX)

Honest gaps vs Freshping's pages: no custom domains, no multi-monitor roll-up page, no incident posts, hostname-only display. It's a live health page you can link, not a branded status site.

5. Something Freshping didn't have: cron heartbeats

The inverse monitor — your job pings us, and the alert fires when the pings stop (dead man's switch):

curl -X POST https://mockbird.mockbird.workers.dev/api/status/heartbeat \
  -H 'content-type: application/json' \
  -d '{"name":"nightly backup","period_minutes":1440,"notify":"https://hooks.slack.com/services/T000/B000/XXXX"}'

The response includes a secret ping URL; append && curl -fsS -m 10 <ping_url> to the cron job so it only checks in on success. Miss the period + grace → one service.down; resume → one service.up. Crontab/systemd/GitHub Actions recipes: cron-job monitoring with one curl.

6. Translation table

7. Where else ex-Freshping users land — honest directory

Fact-check note: Freshping numbers above are as widely reported at shutdown (its own pricing page no longer exists to cite); competitor numbers move — verify against their pricing pages before deciding.

8. Managing monitors

# info + 24h ok-rate + recent checks · then stop
curl "https://mockbird.mockbird.workers.dev/api/status/monitor/mon-XXXX?secret=YOUR_SECRET"
curl -X DELETE "https://mockbird.mockbird.workers.dev/api/status/monitor/mon-XXXX?secret=YOUR_SECRET"

Both endpoints self-document on a bare GET (GET /api/status/monitor, GET /api/status/heartbeat). Full feature walkthrough: the uptime monitor API guide.