Pingdom vs StatusCake

Pingdom

The captured documentation lists HTTP, custom HTTP, TCP, ping, DNS, UDP and mail checks with keyword content rules, certificate verification with days-before expiry, a one-minute minimum test resolution, and transaction checks built from a browser recording with page-state validations — close to what I need for testing a login flow. Probes are selectable only as regions (EU, NA, APAC, LATAM), not named cities. I found no public information on confirming a failure from a second location before alerting, heartbeat checks, private probes inside our network, or maintenance windows, and that confirmation step is what keeps my rotation from being woken by one flaky probe.

StatusCake

The protocol set is broad — HTTP(S), HEAD, TCP, DNS, SMTP, SSH, ping and push heartbeats, plus SSL expiry alerting, domain expiry with DNS record rules, keyword matching and configurable timeouts and trigger rates — and downtime is confirmed by additional servers before an alert goes out (four claimed on the homepage, up to three configurable via the API), which is exactly the false-positive guard I want before anyone is paged. Checks run from 43 locations in 30 countries, selectable by continent, country or city, at rates down to 30 seconds or constant, with maintenance windows that pause checks. We found no public information on multi-step API checks with assertions on headers and body, or on browser and transaction checks of a login or checkout flow, which is what keeps this short of top marks.

Pingdom

The documentation shows checks trigger down alerts, including when response time crosses a configured limit, and an API endpoint returns the alert actions generated for the account. Beyond that I found no public information on delivery channels, phone-call or SMS costs, escalation policies, on-call schedules, or maintenance windows that mute alerts. It tells me alerts fire, but not how they reach a human at 3 a.m.

StatusCake

Fourteen alert platforms including phone call and SMS, PagerDuty, Opsgenie, Slack, Microsoft Teams and webhooks, with per-monitor contact groups (email addresses, mobile numbers, integrations, a ping URL), a configurable delay before alerting, and maintenance windows that mute alerts — the channels my rotation needs exist, and SMS credits are shown per plan (75 on Superior, 400 on Business). We found no public information on escalation policies with timeouts, on-call schedules and rotations, acknowledge and resolve from the app, or alert grouping and incident timelines, so a team wanting full on-call inside the product would have to lean on PagerDuty or Opsgenie for that machinery.

Pingdom

We found no public information on status pages, incident updates, or subscriber notifications; the captured documentation covers the monitoring API only, and no facts about pages or incidents appear there.

StatusCake

StatusCake Pages offers a public status page showing past updates, issues and resolutions, uptime history for the last seven days, subscribers notified by email, SMS and RSS, custom CSS with the vendor's branding removable, and private pages behind a password or an IP access list, with subscriber caps published per plan (300, 1,500 and 7,000). We found no public information on a custom domain for the status page, on components and component groups fed by monitors, on scheduled maintenance announcements published to the page, or on per-component subscriptions, which is what separates this from the stronger tiers.

Pingdom

The REST API is genuinely well documented — version 3.1, a downloadable OpenAPI specification, bearer-token auth with read and read/write levels, and coverage of most control-panel functionality including bulk pause and resolution changes across checks, which is enough to script check lifecycle. I found no public information on a Terraform provider or other monitoring-as-code workflow, single sign-on, SCIM, audit logs, or team members with roles, and checks living in version control next to the service is a hard requirement for my team.

StatusCake

This is where the product fits my workflow: a documented v1 REST API with a downloadable OpenAPI spec covering uptime, SSL, page speed, heartbeats, maintenance windows and contact groups, plus SDKs and a Terraform provider the vendor describes as the most-downloaded in its industry at 8.5M+ installs — so checks can live in version control next to the services they test. Administration covers View Only and Full Access permission levels, sub-accounts, an audit log, Google or Microsoft single sign-on for all customers, and white-label reporting. We found no public information on SCIM provisioning, on checks triggered from CI/CD, and SAML specifically is not named among the sign-on options.

Pingdom

The API returns per-check root cause analysis results and the account's alert history, so some per-check record exists. I found no public information on uptime or SLA reports, response-time percentiles, retention periods, raw export, the vendor's own status page, or published probe IP addresses for allow-listing.

StatusCake

Reporting is well developed: scheduled daily, weekly or monthly email reports plus on-demand ones, tag-driven customisation, white-label reports, and public or private report pages shareable with customers on a CNAME, with the uptime API returning history and check periods. Retention is stated per plan in unusual detail — up to six years of overview data on Gold, one year on Silver, 90 days on Bronze — though the captured pages give different figures for uptime history retention, with the uptime feature page saying up to a month. We found no public information on response-time percentiles or breakdowns, published probe IP addresses for allow-listing, or the vendor's own SLA beyond a service-creditable SLA listed as a custom-plan option, and the vendor's own public status page is not evidenced on the pages we read.

Pingdom

The captured documentation says nothing about contracting entities, hosting locations, data residency, subprocessors, or a data processing agreement, and every sovereignty attribute is unknown rather than proven European or non-European. We found no public information on the data chain, so it stays unknown — something my Berlin company would have to resolve before contracting.

StatusCake

The contracting entity is TrafficCake Limited, registered in England and Wales with an address in Grays, United Kingdom; personal data is primarily stored and processed in the United Kingdom; and a published data processing addendum covers both UK and EU GDPR with standard contractual clauses for transfers outside the UK/EEA. A subprocessor list is published, but much of the chain runs through US providers — Google Cloud and AWS for hosting, Twilio for SMS, SparkPost and Mailchimp for email, Intercom for support, Stripe and PayPal for payments — albeit with safeguards stated. The entity and hosting are UK rather than EU, and we found no public information on ISO 27001 or SOC 2 certifications or a self-hosted edition, so this sits well below the top anchors.

Pingdom

The only pricing information captured is that response-time down alerting is "Not available for Starter and Free plans", which confirms a free tier and a Starter plan exist and that features are gated by plan. I found no public prices, scaling rules by monitor count or interval, or stated SMS and call costs.

StatusCake

The main tiers are public with real numbers: Superior at €19.99/mo (€16.66/mo billed yearly, €199.92 billed yearly) with 100 uptime monitors, one-minute intervals, two team members and 75 SMS credits, and Business at €69.99/mo (€58.33/mo billed yearly, €699.96 billed yearly) with 300 monitors, 30-second intervals, ten team members and 400 SMS credits, alongside a €0 free tier with a seven-day trial and no credit card; the captured pages give different figures for the plan line-up (the pricing page shows Free, Superior and Business while the status page feature page shows Bronze at €11.63, Silver at €36.63 and Gold at €183.29 with status page counts of 1, 5 and 10) and for the free plan's monitor count. What a buyer still cannot compute: the price per SMS or phone call beyond the included credits, add-on pricing (the custom tier is POA), overage handling, and VAT treatment. Annual billing gives two months free (save 16%) and cancellation is stated as possible at any time without a phone call.