Pingdom vs StatusCake

Pingdom

The API documents HTTP, keyword, TCP, ping, DNS, UDP and mail-protocol checks with certificate validation and days-before-expiry down alerts, a one-minute check interval, four probe regions, and scripted or recorded transaction checks with page-state validations. We found no public information on heartbeat or cron monitoring, confirmation from a second location before alerting, private probes inside our own network, or maintenance windows.

StatusCake

Eight check protocols including HTTP(S), DNS, PING, TCP, SMTP, SSH and PUSH heartbeats are documented with check rates down to 30 seconds (marketed as constant or 5-second on higher plans), and downtime is confirmed by additional servers before an alert — the confirmation count is settable through the API with a documented default, which is the kind of detection method I can explain to an auditor. Maintenance windows that pause checks by test or tag, and location selection at continent, country or city level across 43 locations in 30 countries, are also published. We found no public information on multi-step API checks with assertions, browser or transaction checks, or private locations inside our own network.

Pingdom

The documentation shows alerts generated when a response time exceeds a set value in ms or a certificate fails verification, plus an endpoint listing past alerts, but we found no public information on delivery channels, escalation policies, on-call schedules, acknowledgement, or the cost of SMS and phone alerts. For my on-call staff I need far more than proof that an alert fires.

StatusCake

Alerts go out on fourteen platforms including PagerDuty, OpsGenie, phone call and SMS, with contact groups holding email addresses and international-format mobile numbers configurable through the API, an alert delay setting, maintenance windows that pause alerting, and a mute option in Slack. We found no public information on escalation policies with timeouts, on-call schedules and rotations, acknowledging or resolving from the app, or alert grouping. SMS is bundled as credits per plan (75 on Superior, 400 on Business), but we found no public per-message or per-country pricing for SMS or calls.

Pingdom

We found no public information on status pages, custom domains, components, incident updates or subscriber notifications; the captured API documentation is silent on the subject.

StatusCake

Public status pages with custom branding and custom CSS, password or IP-access protection for private audiences, subscribers notified by email, SMS and RSS with per-plan subscriber limits, a visible history of past updates and seven days of uptime history are all published, and the privacy policy confirms the vendor acts as processor for status page subscriber data — the point I check before collecting those numbers. We found no public information on custom domains, components linked to monitors, per-component subscriptions, incident templates or widgets, or on how the status page itself stays online when the main service is down. That is a workable public page but not yet the audience-specific communication set I would want for a single-customer view.

Pingdom

A well-documented REST API with a downloadable OpenAPI specification covers most control-panel functionality, including bulk pausing and modification of checks, with tokens carrying read or read/write permission. We found no public information on single sign-on, SCIM provisioning, audit logs, team roles, two-factor authentication, or monitoring-as-code workflows — the controls I require before anyone gets a login.

StatusCake

A documented REST API with a downloadable OpenAPI specification and an Apache-2.0 licence covers uptime, SSL, page speed, heartbeat, contact groups and maintenance windows, and a Terraform provider the vendor describes as the most downloaded in its industry keeps checks in version control — what I want before a change reaches production. Team logins are tiered, permissions split View Only and Full Access, sub-accounts and white-label reports are documented, and an audit log is listed on the pricing page, which I need before anyone gets a login. Single sign-on is offered through Google and Microsoft for all customers, but we found no public information on SAML-based federation, SCIM provisioning or two-factor authentication.

Pingdom

The API returns root cause analysis results per check and the alerts generated for the account, which gives a partial incident trail, but we found no public information on uptime or SLA reports, retention periods, export formats, probe IP addresses for allow-listing, or the vendor's own availability record and SLA.

StatusCake

Retention is published per plan and per data type — for example Silver keeps a year of overview and 60 days of detailed test data, Gold six years of overview — which is the retention statement an ISO 27001 auditor asks for, and check periods, uptime history and alert history are retrievable through the API alongside daily, weekly and monthly white-label reports. An SLA with service credits appears only as a custom-plan option, and the subprocessor list shows the vendor's own status communications run through Atlassian Statuspage. We found no public information on response time percentiles, published probe IP addresses for allow-listing, the SLA calculation method, or the vendor's own published availability history.

Pingdom

The captured vendor details identify SolarWinds Worldwide, LLC in the USA with an Irish affiliate mentioned in the privacy policy, but we found no public information on where account data, alert contacts and status subscribers are stored, on the subprocessor list, on a data processing agreement, or on security certifications. Until the on-call phone numbers and subscriber data have a documented chain, I cannot put them in the system.

StatusCake

The subprocessor list is published with purposes and data categories — cloud on DigitalOcean, Google Cloud and AWS, email via SparkPost and Mailchimp, SMS via Twilio, support via Intercom, payments via Stripe and PayPal, status via Atlassian Statuspage — and a data processing addendum covering UK and EU GDPR grants audit rights once per twelve months, breach notification without undue delay, fourteen days' subprocessor change notice with an objection right, and deletion on termination. Personal data is stored primarily in the United Kingdom under an England-and-Wales entity, with transfers outside the UK and EEA possible under standard contractual clauses, and the audit terms place the audit costs on the customer. We found no public information on ISO 27001 or SOC 2 certification, on the locations of the named subprocessors, or on a self-hosted edition.

Pingdom

The only pricing fact on the captured pages is that response-time alerts are not available for Starter and Free plans, which confirms a free tier and a starter tier exist. We found no public information on prices, monitor limits, seat costs, SMS and call charges, overage handling, contract terms or VAT.

StatusCake

The pricing page publishes plans with monitor counts, check intervals, page speed, domain, SSL and server monitors, team logins and SMS credits — Superior at €19.99/mo with 100 uptime monitors, 1-minute intervals, 2 logins and 75 SMS credits; Business at €69.99/mo with 300 monitors, 30-second intervals, 10 logins and 400 credits — plus a free plan, a 7-day trial without a credit card, and annual billing marketed as two months free (save 16%). The custom tier is priced only on application, per-message costs for SMS and phone calls are not published, and we found no public information on overage handling, minimum term or VAT treatment. The captured pages also give different plan names and figures on the status page (Bronze €11.63 per month, Silver €36.63 per month, Gold €183.29 per month) and a different free-plan monitor count than the pricing page.