Freshping Alternative → Migration Guide

Moving from Freshping to InternetSecure

Freshping's data will be permanently deleted on June 4, 2026. This guide walks you through exporting what you need and setting up your monitors on InternetSecure.

Important dates

March 6, 2026

Freshping shut down

Free accounts disabled, no new checks

June 4, 2026

Data permanently deleted

Export your history before this date

Today

Migrate to InternetSecure

Set up monitors in under 5 minutes

1

Export your Freshping data

If you still have access to your Freshping account, export your data before June 4. Freshping offers two export methods:

Option 1: Dashboard Export

Account admins can request a data export from the Freshping dashboard. You'll receive a secure download link within 48 hours containing XML files with your monitor configurations, status page settings, and integration configs. The link stays active for 60 days.

Option 2: REST API

If you prefer a programmatic approach, use Freshping's REST API to extract your monitor configurations and historical data. Useful if you're scripting the migration.

From the export, the key things you'll need for each monitor are the URL, check path, check interval, and alert recipients.

Free plan users have until ~June 4, 2026 (90 days after shutdown). Paid plan users have 90 days after their subscription end date.

2

Create your InternetSecure account

Sign up at internetsecure.org/register/free. No credit card required.

Choose the plan that matches your monitoring needs:

Had 1-5 Freshping monitors?

Free (1 monitor) or Plus ($5/mo, 10 monitors) will cover you.

Had 10-50 Freshping monitors?

Pro ($20/mo, 100 monitors) gives you room to grow.

All plans include 1-minute checks from multiple global nodes with multi-node consensus. See the full comparison.

3

Add your domains

From your Domains dashboard, add each domain you were monitoring in Freshping:

  1. Add domain — enter the domain name (e.g., example.com)
  2. Enable uptime monitoring — toggle uptime on for the domain
  3. Configure check path — set the path to monitor (default is /)
  4. Choose HTTP method — HEAD (fastest), GET, or POST
  5. Set alerts — configure which channels to notify (email, Slack, JIRA, Linear, Teams)

Each monitor takes about 30 seconds to set up. Checks begin immediately.

Migrating a large number of monitors? Open a support ticket and we'll help you bulk-add your domains.

4

Set up your alerts

Freshping supported email and Slack alerts. InternetSecure supports those plus JIRA, Linear, and Microsoft Teams.

Email

Enabled by default on all plans

Slack

Webhook URL in profile settings

JIRA

Auto-creates issues with incident details

Linear

Creates issues in your Linear workspace

Configure integrations from your Profile page, then enable per-monitor alerts from the domain settings.

5

Things Freshping didn't have

Now that you're set up, consider enabling features that weren't available on Freshping:

Cloudflare Offline Page

If your domains use Cloudflare, you can enable automatic offline pages that deploy to your domain when downtime is detected. Visitors see a branded page on your URL instead of an error. Works on Cloudflare's free plan. Configure per-monitor from the domain settings.

Security Scanning

InternetSecure automatically scans your domains for SSL/TLS issues, missing security headers, DNSSEC, DMARC, DKIM, and more. Scheduled scans detect changes and alert you when your security posture changes. This runs alongside uptime monitoring.

Maintenance Windows

If you have scheduled maintenance, set up maintenance windows per monitor to suppress alerts during planned downtime. Configure day-of-week and time ranges.

Compliance Framework Mapping

On paid plans, security scan results are automatically mapped to compliance frameworks including GDPR, HIPAA, SOC 2, ISO 27001, and PCI DSS. Useful if you need to demonstrate security posture for audits.

Concept mapping

If you're familiar with Freshping's terminology, here's how things map:

Freshping InternetSecure
Check Monitor (domain + check path)
Status Page Cloudflare Offline Page (auto-deployed on your domain)
Incident Incident (with timeline, affected nodes, duration)
Integration Alert channel (per-monitor, configured in domain settings)
Probe location Node (all nodes check every monitor, consensus required)
Downtime alert Down alert (consensus-verified, ~5s delivery)

Ready to migrate?

Your first monitor will be live in under 60 seconds.