Switching from Pingdom to Uptimely
SolarWinds is replicating Pingdom accounts onto SolarWinds Observability Digital Experience, with a 30-to-60-day transition period after which the Pingdom account becomes read-only for viewing history. If you have decided not to go with it, this page is the practical version: which Pingdom concept becomes which Uptimely concept, what you pick up on the way, and what you give up. The last part is not a formality — there are three real losses and they are listed as plainly as the gains.
What SolarWinds' own documentation says
Three facts from SolarWinds' migration documentation shape every decision here. Your Pingdom account transitions to a read-only state at the end of the transition period. Historical monitoring data is not moved over as part of the migration — it stays in that read-only account. And text message or SMS alerts are not currently available in SolarWinds Observability. Whichever product you land on, the first job is the same: export the history you need while the account still lets you.
Deciding rather than moving?
This page assumes you have already chosen to leave. Uptimely vs Pingdom 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
| Pingdom | Uptimely | Notes |
|---|---|---|
| Uptime check | Website or API monitor | A URL and an interval. Uptimely's minimum interval is 1 minute on every plan, including Free. |
| Transaction check | Synthetic monitor | Uptimely runs scripted synthetic checks, but it has no recorder — you write the script rather than clicking through a browser to generate it. |
| Page speed check | — | No equivalent. Uptimely records response time per check and charts it, which is not the same thing as a page-speed audit. |
| Real user monitoring (RUM) | — | No equivalent, and none planned. If RUM is why you bought Pingdom, SolarWinds Observability carries it forward and staying is the better answer. |
| Alerting policy / contacts | On-call duty policy with escalation | A step up rather than a match: rotations, escalation rules with delays, and acknowledgement — included on every plan, not sold per seat. |
| SMS alerts | SMS alerts | Preserved. This is the channel SolarWinds' documentation says is not currently available in the replacement. |
| Public status page | Status page | One on Free, unlimited on Pro, each with its own custom domain, subscribers and scheduled-maintenance windows. |
| Integrations / webhooks | Channel integrations + outbound webhooks | Slack, Discord, email, SMS, voice and push, plus signed outbound webhooks (Standard Webhooks v1). |
| Pingdom API | Public /v1 REST API | Different shapes, same job. Uptimely publishes an OpenAPI 3.1 schema, an npm SDK and an MCP server; scripts do not port across, but they have something to be rewritten against. |
What you gain
- SMS alerts stay, alongside voice call, Slack, Discord, email and web push.
- On-call escalation with duty policies and acknowledgement, included on every plan — not a separate paging vendor and not priced per seat.
- Status pages included with the monitoring that drives them: 1 on Free, unlimited on Pro, custom domains, subscribers and maintenance windows.
- A free plan at $0 — Pingdom has none, only a 30-day trial — and a flat $29/month Pro plan with unlimited monitors rather than billing by check volume.
- A public /v1 REST API with a published OpenAPI 3.1 schema, an SDK and an MCP server, so agents and IaC can drive it.
- OpenTelemetry ingestion — OTLP logs, traces and metrics — plus a Prometheus /metrics endpoint, in the same product as the checks.
- Your check history stays in the account you are using rather than in a read-only one you have to remember to log into.
What Uptimely does not do
- Uptimely probes from ONE vantage point. Pingdom runs 100+ global locations, so this is the biggest single step down in the move, and a check that fails only from our network looks the same as a real outage. What Uptimely does about it: a monitor declares an incident only after consecutive failed checks, each of which is independently re-confirmed, and infrastructure-class failures are gated against a live egress health check. A second vantage is on the roadmap and is not shipped.
- There is no real-user monitoring, no page-speed scoring and no transaction recorder. Synthetic checks are scripts you write.
- The Pingdom importer moves monitors, not your account. Alert contacts, integrations, status pages and reports are set up again by hand. Pingdom also has no UI export of check configuration, so the file you import has to come from its API — and its list response alone cannot say whether a check is https or which path it hits, so those checks are reported as skips rather than imported as guesses.
- Historical data cannot be imported from Pingdom into Uptimely, or into anything else. Export it from Pingdom for your own records before the account goes read-only.
How to move
- Export your Pingdom history now, before the transition period ends and the account goes read-only. No destination product can import it, so this is for your records — but it is the only irreversible deadline in the whole move.
- Pull your checks out of the Pingdom API and save the JSON — what you want is GET /checks/{id}, one call per check, because that is the only response carrying the target, the interval and the failed-check threshold an import reads. GET /checks is the step before it, to list the ids; saving that list alone is what produces the skips described above, since it cannot say whether a check is https or which path it hits.
- Try it before you commit: Uptimely runs in guest mode without an account, so you can create a monitor, watch it probe and publish a status page before you sign up for anything.
- Import that JSON under Monitors → Import and export. It is converted to monitors and shown to you as a plan first — what will be created, what is skipped as something this project already has, and every check that could not come across in full, named. Nothing is written until you confirm. The wizard is still there for a handful.
- Run both in parallel until you have seen Uptimely catch something. Pingdom keeps working through the transition period, so there is no reason to cut over on faith.
- Rebuild alerting last: on-call duty policy, escalation rules, and the channels each person wants, including SMS.
The transition period, the read-only account, the statement that historical data is not moved over, and the unavailability of SMS alerts in SolarWinds Observability are all quoted from SolarWinds' own migration documentation: https://documentation.solarwinds.com/en/success_center/observability/content/intro/websites/migrate-pingdom.htm — read 2026-08-30 and re-checked 2026-09-02. 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 →Do I have to leave Pingdom?
No. SolarWinds describes SolarWinds Observability Digital Experience as the next generation of Pingdom rather than a discontinuation, and its synthetic network and real-user monitoring carry forward. If the wider SolarWinds suite is where your team is heading, staying is a reasonable answer. This page is for people who have already decided to look elsewhere.
Can I import my Pingdom monitors automatically?
Yes, the monitors. Save your checks from the Pingdom API as JSON and drop the file into Monitors → Import and export: Uptimely converts it and shows you the plan before it writes anything — what it will create, what it skips because this project already has a monitor of that name and type, and every check it could not carry across in full, by name. POST /v1/monitors/import?dry_run=true is the same preview for scripts, and the preview and the real run are the same decision. Two honest limits: an import that would take you past your plan's monitor limit is refused whole rather than applied halfway, and Pingdom publishes no UI export of check configuration, so the file has to come from its API. Alert contacts, integrations and status pages are still set up by hand.
Will my Pingdom history come across?
No, and it will not come across to any other product either. SolarWinds' own documentation states historical data is not moved as part of its migration, and Uptimely has no import path for another vendor's check history. Export what you need from Pingdom while the account is still writable, and treat the new account as starting fresh.
Does Uptimely check from as many locations as Pingdom?
No, and this is the honest weak point of the move. Pingdom runs synthetic checks from 100+ global locations; Uptimely probes from a single vantage point, with a second one on the roadmap rather than shipped. If multi-region agreement is a hard requirement, Uptimely is not the right shortlist today. If what you actually need is to be told reliably when your service is down, the confirmation re-check, the consecutive-failure threshold and the egress gate are how a single vantage is made trustworthy.
Do I keep SMS alerts?
Yes. SolarWinds' migration documentation states that text message or SMS alerts are not currently available in SolarWinds Observability; Uptimely sends SMS, and also voice calls, Slack, Discord, email and web push. For a team whose escalation path runs over SMS, this is usually the fact that decides the move.
How long does the move take?
The work is proportional to your check count, because re-creating monitors is the bulk of it: an hour or two for a handful, an afternoon for a few dozen through the API. Do not compress the overlap period, though — run both products in parallel until Uptimely has caught a real event, and cut over after that rather than before.