Freshping has shut down: moving your monitors

Updated 25 October 2026 · By the Upcertain team

What happened

Freshworks emailed Freshping users that it was retiring the product. Free plans could be used until 6 March 2026, and paid plans could not renew after that date. The Freshping website now redirects to Freshworks.

What to rebuild

• Checks: each URL with its interval and what counts as up.
• Alert contacts: who was emailed and which chat tools were connected.
• Status page: which checks it showed and the domain it used.

Rebuilding in Upcertain

1. Create an account. New accounts start on the Basic plan: 10 monitors checked as often as every 60 seconds and one status page.
2. Put your URLs in a file, one per line, or as a CSV with header columns such as name,url,type,interval. Choose New monitor, then Import from CSV; every row is previewed before anything is created, up to 200 at a time.
3. Add alert channels in Settings, Alert channels: email, Slack, Microsoft Teams, Discord, Google Chat or webhooks.
4. Create a status page from the same monitors. On Team and Business, put it on your own domain (steps).
5. Add heartbeat monitors for scheduled jobs if you had no way to watch them before.

What to rebuild, and where it goes

Choosing intervals and confirmation

Before copying your old intervals everywhere, sort your URLs by how much a short outage costs. Checkout, login and public APIs deserve the shortest interval your plan allows; documentation and marketing pages are fine every 5 minutes. Then decide how long a failure must last before anyone hears about it: one re-check after 15 seconds filters out dropped requests, while services with slow deploys may want three re-checks 30 seconds apart. How often to check has the numbers.

Alerts that reach the right people

In Upcertain each monitor picks alert channels, and each channel picks events: down, recovery and SSL expiry. Give each team its own channel, so the payments team does not hear about the blog. Add a delay on channels that only need to know about long outages. Set a repeat interval on critical monitors, so an unacknowledged incident keeps reminding people. People who only need to hear about outages can be notify-only contacts: they get email alerts and have no login.

Things worth setting up this time

• Confirmation checks, so one dropped request does not alert anyone.
• Certificate expiry warnings, which come with every HTTPS monitor.
• Separate channels per team, so alerts reach the people who own the service.