Uptime Monitoring & Status Pages
StatusCake
UK / wider Europe Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by TrafficCake Limited · www.statuscake.com
Compare with Pingdom → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
StatusCake at a glance
- Vendor
- TrafficCake Limited
- Headquarters
- Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 1 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 1 Nov 2026
- Panel verdict
- The AI panel rates StatusCake 3/5, the mean of 6 judges. StatusCake is an uptime monitoring and status-page service from TrafficCake Limited in England and Wales. how scores are made
- As of
- Vendor pages captured 1 Nov 2026; evaluated by the panel 2 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
StatusCake is an uptime monitoring and status-page service from TrafficCake Limited in England and Wales. It is strongest on automation and teams and on checks and locations, at 6-7: a documented REST API with an OpenAPI specification, a Terraform provider with a claimed 8.5M+ installs, and checks over HTTP(S), TCP, DNS, SMTP, SSH, ping and push heartbeats from 43 locations in 30 countries at 30-second or constant rates, with downtime confirmed by additional servers before an alert. Sovereignty is the weakest criterion, at 4-5: a UK entity with personal data primarily stored and processed in the United Kingdom, subprocessors including Google Cloud, AWS, Twilio, and we found no public information on ISO 27001 or SOC 2 certification, an EU hosting option or a self-hosted edition. Status pages spread 4 to 6 — subscriber limits are published per plan, but we found no public information on custom domains, components or maintenance announcements. Alerting and on-call scores 5-6: fourteen platforms, but escalations and rotations are undocumented. Reports and reliability is flat at 6; pricing transparency 5-6, with different plan line-ups across the captured pages.
Speaks for it
- Checks cover HTTP(S), HEAD, TCP, DNS, SMTP, SSH, ping and push heartbeats from 43 locations in 30 countries, at rates down to 30 seconds or constant, with confirmation servers re-checking before an alert
- A documented REST API with a downloadable OpenAPI specification and a Terraform provider (claimed 8.5M+ installs) put checks under version control
- Fourteen alert platforms are listed, including phone call, SMS, PagerDuty, Opsgenie, Slack and Microsoft Teams, with contact groups and maintenance windows
- Data retention is published per plan and per data type, from 90 days of overview data on Bronze to six years on Gold
- Pricing tiers are public with monitor counts, intervals, logins and SMS credits — Superior at €19.99/mo with 100 uptime monitors, Business at €69.99/mo with 300 — plus a free tier and a 7-day trial without a credit card
Held against it
- We found no public information on browser or transaction checks, multi-step API checks with assertions, or private probes inside a customer's network
- We found no public information on escalation policies, on-call schedules or rotations, acknowledge-and-resolve flows, or alert grouping
- We found no public information on a custom domain for the status page, components fed by monitors, or scheduled maintenance announcements, and the public page shows the past seven days of uptime history
- The contracting entity is TrafficCake Limited in England and Wales with personal data primarily stored and processed in the United Kingdom, and we found no public information on ISO 27001 or SOC 2 certification, an EU hosting option or a self-hosted edition
- The captured pages give different figures for the free plan's monitor count and present two plan line-ups (Bronze, Silver and Gold against Free, Superior and Business), and we found no public information on per-message SMS or call costs, VAT treatment or overage handling
Best for
- You run an agency or managed-service shop monitoring many client sites and need sub-accounts, per-client tag reporting and white-label reports
- Your team manages infrastructure as code and wants checks defined through a documented API and Terraform provider before changes reach production
- You already run PagerDuty or Opsgenie for on-call and need a broad-protocol monitoring service feeding them
- You want a failure confirmed from multiple servers before anyone is paged, with checks from 43 locations in 30 countries
Avoid if
- You need transaction or browser checks that replay a checkout or login flow, since the documented check types are HTTP, HEAD, TCP, DNS, SMTP, SSH, ping and push heartbeats
- You require an EU contracting entity or EU data residency, since the vendor is registered in England and Wales and personal data is primarily stored and processed in the United Kingdom
- Your status page must show component-level service status or history beyond the past seven days
- You want full on-call machinery inside the monitoring product, since the documented alerting covers channels, contact groups, delays and maintenance windows
The scores
| Criterion | Panel median |
|---|---|
| Checks, locations & failure confirmation | 3.5 of 5 |
| Alerting, escalation & on-call | 3 of 5 |
| Status pages & incident communication | 2.5 of 5 |
| API, monitoring as code & team administration | 3.5 of 5 |
| Uptime reports, data & the vendor's own reliability | 3 of 5 |
| European sovereignty | 2.5 of 5 |
| Pricing transparency | 3 of 5 |
Checks, locations & failure confirmation
Show reasoningHide reasoning
How this is scored
What can be monitored and how reliably a failure is detected: HTTP(S) with status code and keyword checks, TCP and port, ping, DNS records, SSL certificate and domain expiry, cron jobs and heartbeats, multi-step API checks with assertions, browser or transaction checks of a login or checkout, the shortest check interval, the number and regions of probe locations, the re-check from a second location before an alert, timeouts and response time thresholds, and private locations inside the customer's own network.
0 — Runs no checks of its own; a status page or alerting tool that only receives signals from other monitors.
3 — HTTP checks of a URL at a fixed interval with an up or down result; keyword, SSL, cron and the probe locations are basic or not described.
5 — HTTP(S), keyword, TCP or port, ping and SSL expiry checks, cron or heartbeat monitoring, an interval of one minute or less, several named probe locations, a failure confirmed from a second location before alerting, and response times recorded per check.
8 — Multi-step API checks with assertions on headers and body, browser or transaction checks of a user flow, DNS and domain expiry checks, sub-minute intervals, probe locations listed by city with the confirmation logic documented, private locations or agents for internal services, and maintenance windows that pause checks.
10 — Coverage and accuracy a reliability team runs on: every check type above with code-based checks (for example Playwright or scripted tests) in version control, location-specific thresholds, false-positive handling and probe health published, and the detection method documented so a result can be reproduced.
The Agency Developer
Everything I would roll out for sixty client sites is documented: HTTP(S), HEAD, TCP, DNS, SMTP, SSH, PING and heartbeat checks, keyword matching, SSL expiry alerts at one, 14 and 30 days, domain expiry reminders down to 24 hours plus DNS record rules, 30-second and constant check rates, and 43 locations in 30 countries selectable at continent, country or city level. Downtime is confirmed by a configurable number of servers before an alert, with first-byte timeouts and an alert delay both set per check. We found no public information on multi-step API checks with assertions, browser or transaction checks, or private probes inside a client's own network. 1 7 3 4 14 8
The SaaS Platform Engineer
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. 1 7 8 14
The Customer Support Lead
The uptime checks cover the protocols I would expect — HTTP(S) with keyword matching, TCP, ping, DNS, SMTP, SSH and heartbeat push tests — run from 43 locations in 30 countries with selection at continent, country or city level, and downtime is confirmed by multiple confirmation servers (default two, up to four claimed) before an alert goes out, with check rates down to 30 seconds or constant and documented per-test timeouts. Maintenance windows that pause checks are documented in the API. We found no public information on browser or transaction checks of a login or checkout flow, multi-step API checks with assertions, or private probe agents inside a customer's own network beyond server metrics monitoring. 1 7 14 8
The E-Commerce Operations Manager
Coverage is broad: HTTP(S) with a keyword check that counts the page as down when the string is missing, TCP, ping, DNS, SSL expiry with alerts up to 30 days out, domain expiry reminders, heartbeats, checks as often as every 30 seconds (with a constant option) from 43 locations in 30 countries selectable by continent, country or city, and a failure re-checked from additional servers before alerting — the captured pages give different figures for how many (four on the homepage, up to three in the API settings). What I found no public information on is a browser or transaction check that replays my checkout and payment flow — exactly what broke for six hours while the homepage answered 200 — or multi-step API checks with assertions and private probes inside our own network. 1 7 8 13 14
The Information Security Officer
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. 1 2 7 8 14
The Skeptic
Test types run from HTTP(S) and keyword matching through TCP, ping, DNS, SMTP, SSH and heartbeat-style PUSH, at intervals down to 30 seconds or constant, from 43 locations in 30 countries selectable by continent, country or city — and a failure is confirmed by a configurable number of confirmation servers (default 2, up to 3) before any alert goes out, with timeouts and alert delays documented. We found no public information on multi-step API checks with assertions, browser or transaction checks of a user flow, or private probe locations inside a customer's network, which is what separates the solid from the comprehensive. 1 2 7 8 14
Alerting, escalation & on-call
Show reasoningHide reasoning
How this is scored
How the right person learns about a failure: alert channels (email, SMS, phone call, push app, Slack, Microsoft Teams, Telegram, webhooks), alerts to PagerDuty, Opsgenie or similar tools, escalation policies when an alert is not acknowledged, on-call schedules and rotations, acknowledge and resolve from the app, alert grouping and noise reduction, recovery notifications, maintenance windows that mute alerts, and whether SMS and calls are included or charged per message.
0 — No alerting at all; results can only be viewed in the dashboard.
3 — Email alerts and one or two chat integrations; escalation, phone calls and schedules are basic or not described.
5 — Email, SMS, a mobile push app, Slack, Microsoft Teams and webhooks, alerts forwarded to PagerDuty or Opsgenie, per-monitor alert contacts, recovery notifications, a delay or threshold before alerting, and maintenance windows that mute alerts.
8 — Phone call alerts, escalation policies with timeouts, on-call schedules and rotations with overrides, acknowledge and resolve from the app or chat, alert grouping, incident timelines with who did what, and the price of SMS and calls stated per country or included in the plan.
10 — On-call that replaces a separate incident tool: follow-the-sun schedules, escalation across teams, alert routing by service and severity, post-incident reviews generated from the timeline, and delivery of every alert channel monitored and reported.
The Agency Developer
The channel list is broad — email, SMS, phone calls, Slack, Microsoft Teams, Telegram, webhooks, PagerDuty and Opsgenie among 14 platforms — with contact groups carrying their own email addresses, mobile numbers and integrations, an alert delay of up to 60 minutes, and maintenance windows that mute alerts. Free accounts get one contact group while paid plans are unlimited, and paid tiers include SMS credits (75 on Superior, 400 on Business) rather than a stated per-message price. We found no public information on escalation policies, on-call schedules and rotations, or acknowledging and resolving incidents from the app or chat, so a missed first alert has no documented second ring. 6 7 8 5 16
The SaaS Platform Engineer
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. 6 7 8
The Customer Support Lead
Email, SMS, phone call, Slack, Microsoft Teams, Telegram and webhooks are all listed among fourteen alert platforms, with forwarding to PagerDuty and OpsGenie, contact groups that can hold email addresses and mobile numbers, a configurable delay in minutes before alerting, and maintenance windows that mute alerts. SMS arrives as plan credits (75 on Superior, 400 on Business) rather than a stated per-message price. We found no public information on escalation policies with timeouts, on-call schedules or rotations, acknowledging and resolving from the app, or alert grouping. 6 7 8 16
The E-Commerce Operations Manager
Phone call and SMS alerts sit among fourteen platforms including PagerDuty, Opsgenie, Slack, Microsoft Teams and Telegram, contact groups take international mobile numbers, there is a delay setting before alerting, maintenance windows mute alerts, and paid plans include SMS credits (75 or 400). But I found no public information on on-call schedules, rotations or an escalation policy that re-pages the next person when the night SMS is slept through, and no per-country price for calls or SMS beyond the included credits. 1 6 7 8 16
The Information Security Officer
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. 6 7 8 16
The Skeptic
Fourteen alert platforms are listed including phone call and SMS, PagerDuty, Opsgenie, Slack and Microsoft Teams, with per-monitor contact groups, an alert delay of up to 60 minutes, maintenance windows that pause alerts, and SMS credits bundled per plan (75 on Superior, 400 on Business) rather than an 'unlimited' promise. We found no public information on escalation policies, on-call schedules or rotations, acknowledge-and-resolve flows, or alert grouping — the machinery that decides who actually gets woken at 3am is undocumented. 6 7 8
Status pages & incident communication
Show reasoningHide reasoning
How this is scored
How customers and colleagues are told: public status pages on a custom domain with SSL, components and component groups fed automatically by monitors or set by hand, incident updates and scheduled maintenance announcements, subscribers notified by email, SMS, RSS or webhook, uptime history shown per component, private or password-protected pages for internal teams or single customers, branding and custom CSS, several languages, page templates, and how the status page itself stays online when the main product is down.
0 — No status page of any kind.
3 — A public status page listing monitors with their current state; custom domain, incident updates and subscribers are basic or not described.
5 — Public status pages on a custom domain, components linked to monitors, incident updates and scheduled maintenance, email subscribers, uptime history per component, the vendor's branding removable, and a password-protected or private page option.
8 — Component groups, SMS, RSS and webhook subscribers with per-component subscriptions, private pages with single sign-on or IP restriction, several languages, incident templates, embeddable status widgets, audience-specific pages for single customers, and the status page hosting kept separate from the main service and documented.
10 — Incident communication end to end: incidents drafted from monitor events and approved by a person, updates published to the page, subscribers, chat and social channels at once, a full incident archive with post-mortems, status page uptime published, and accessibility of the page stated.
The Agency Developer
StatusCake Pages covers the agency basics: a public status page with the vendor's branding removable, custom CSS, password or IP-restricted private pages, subscribers notified by email, SMS or RSS, pinned updates and a seven-day uptime history with past updates visible. We found no public information on custom domains for the status pages themselves, on components or component groups fed automatically by monitors, or on scheduled maintenance announcements, and the captured page lists one, five or ten pages depending on tier, which is tight across a portfolio of clients. 5 17 15 9
The SaaS Platform Engineer
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. 5 17 15
The Customer Support Lead
StatusCake Pages gives me a public status page with our own branding and custom CSS, subscribers notified by email, SMS or RSS, a visible history of past updates and resolutions, and password- or IP-protected private pages for our largest accounts — most of my list. What I could not find is a custom domain for the status page itself, components fed automatically by monitors, incident templates, or uptime history beyond the past seven days, which is thin to point at in a contract renewal; we also found no public information on how the page stays online when the monitored service is down. 5 17 9
The E-Commerce Operations Manager
A public status page with our own branding and custom CSS, password or IP-restricted private pages, subscribers notified by email, SMS and RSS, seven days of visible uptime history, an archive of past updates and a pinned updates section, with page and subscriber limits stated per plan. I found no public information on components or component groups (I would want checkout and payment shown as separate components), a custom domain for the page itself, several languages, or how the page stays hosted when the main service is down. 5 9 17
The Information Security Officer
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. 5 11 17
The Skeptic
StatusCake Pages, offered since 2015, supports custom branding and CSS with the vendor's branding removable, password- or IP-restricted pages, email, SMS and RSS subscribers, past updates visible to the audience, and uptime history on the public page for the past 7 days. We found no public information on a custom domain for the status page, on components or component groups fed by monitors, or on scheduled maintenance announcements published to subscribers. 5 9 17
API, monitoring as code & team administration
Show reasoningHide reasoning
How this is scored
How the tool fits a team and a deployment pipeline: a documented REST API to create and read monitors, status pages and incidents, a Terraform provider, CLI or monitoring-as-code workflow, checks run from CI/CD before a deploy, bulk import of monitors, integrations with ticketing and chat tools, team members with roles, single sign-on (SAML) and SCIM, audit logs, several teams or client accounts in one organisation, white-label or client reporting for agencies, and two-factor authentication.
0 — No API, no team accounts; one login per account and monitors are set up only by hand.
3 — A web dashboard with a few team members; the API, roles and multi-client set-up are basic or not described.
5 — A documented REST API covering monitors and status pages, webhooks, team members with roles, two-factor authentication, bulk import or a CSV upload of monitors, and several projects, teams or client groups in one account.
8 — A Terraform provider or monitoring-as-code CLI with checks kept in version control, checks triggered from CI/CD, single sign-on (SAML), SCIM provisioning, audit logs, sub-accounts for clients with their own logins, and white-label client reports.
10 — Administration that scales across many teams and clients: every setting reachable by API and code with parity stated, granular roles per resource, SSO enforced with SCIM, audit logs exportable to a SIEM, and agency or reseller accounts with separate billing.
The Agency Developer
This is the agency-friendly part: a documented API with downloadable OpenAPI spec and bearer authentication across uptime, SSL, page speed, heartbeat, contact group and maintenance window resources, a Terraform provider the vendor calls the most-downloaded in the industry at 8.5M+ installs, SDKs, sub-accounts for clients, view-only or full-access users, tags to group tests per client or team, white-label reports and branded email alerts, plus an audit log on higher tiers and automatic Pingdom migration for bulk moves. We found no public information on SAML single sign-on (only Google and Microsoft are described), SCIM provisioning, or checks triggered from a deployment pipeline. 7 9 15 8 1
The SaaS Platform Engineer
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. 7 8 9 15
The Customer Support Lead
A documented REST API with a downloadable OpenAPI specification covers uptime, SSL, page speed, heartbeat, contact group and maintenance window resources, and the Terraform provider — 8.5M+ installs, they claim — plus SDKs make monitoring as code realistic for our pipeline. Audit logs, sub-accounts, white-label client reports and View Only versus Full Access user roles are all evidenced. We found no public information on SAML single sign-on (only Google and Microsoft), SCIM provisioning, two-factor authentication, or checks triggered from CI/CD before a deploy. 7 9 15 8 1
The E-Commerce Operations Manager
A documented REST API with an OpenAPI specification covering uptime, page speed, SSL, heartbeat, maintenance windows and contact groups, plus a Terraform provider the vendor calls the most downloaded in its industry, SDKs, sub-accounts, white-label reports, per-client tag reporting, an audit log and two permission levels — the agency-facing reporting my shop would use is clearly there. Single sign-on is Google or Microsoft only, and I found no public information on SAML, SCIM provisioning, two-factor authentication or checks run from a CI/CD pipeline. 1 7 8 9 15
The Information Security Officer
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. 1 7 8 9 13 15
The Skeptic
A documented REST API with a downloadable OpenAPI specification covers uptime, SSL, page speed, heartbeats, contact groups and maintenance windows, and a Terraform provider — claimed 8.5M+ installs — puts checks in version control; audit logs, sub-accounts, view-only or full-access roles, and Google or Microsoft single sign-on round out the team side. We found no public information on SAML, SCIM provisioning, two-factor authentication, or checks triggered from CI/CD, and no public information on managing status pages or incidents through the API. 1 7 8 9 15
Uptime reports, data & the vendor's own reliability
Show reasoningHide reasoning
How this is scored
What the record is worth and whether the monitor itself can be trusted: uptime and SLA reports per monitor and period, response time charts and percentiles, scheduled reports by email, client-facing reports, how long check results and incident history are kept, export of results by CSV or API, the vendor's own public status page and incident history, its SLA, the probe IP addresses and user agent published for allow-listing, and an open-source or self-hosted edition.
0 — No history of any kind; only the current state is shown.
3 — An uptime percentage and a response time chart per monitor; retention, export and the vendor's own status are basic or not described.
5 — Uptime and response time reports per monitor and period, SLA reports, scheduled email reports, the retention period of check results stated, CSV or API export, the probe IPs published, and the vendor's own public status page.
8 — Response time percentiles and breakdowns (DNS, connect, TLS, first byte), client-ready branded reports, retention of a year or more stated per plan, a raw export of check results, the vendor's incident history and post-mortems public, and an SLA with credits published.
10 — A record that holds up in an audit: SLA calculations with their method stated, incident records suitable for ISO 27001, NIS2 or DORA evidence, full history exportable in an open format, a self-hosted or open-source edition with feature parity stated, and the vendor's own availability over several years published.
The Agency Developer
Monthly client reporting is genuinely covered: scheduled daily, weekly or monthly email reports across uptime, SSL, domain, page speed and other test types, tag-driven customisation sent to team and clients, white-label reports, and public report pages on a CNAME with per-day uptime percentages, load-time graphs and downtime history back to test creation. Retention is published per plan, from 90 days of overview data on Bronze to a year on Silver and six years on Gold, though detailed data is 30 to 60 days and server monitoring 7 to 14 days. We found no public information on response-time percentiles or breakdowns, published probe IPs, or the vendor's own SLA beyond service-creditable SLAs offered on custom plans. 8 18 19 7 1
The SaaS Platform Engineer
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. 8 18 19 2
The Customer Support Lead
Scheduled reports daily, weekly or monthly, unlimited email reports, white-label reports and public or private report pages with per-day uptime percentages and downtime history going back to the test's creation are all documented, and service credits under an SLA appear only as an option on custom plans. The captured pages give different figures for how long results are kept — one page says uptime results are kept for up to a month, another states a per-plan schedule reaching six years of overview data on Gold. We found no public information on SLA reports with a published calculation method, response time percentiles or breakdowns, or the probe IP addresses for allow-listing; the vendor's own status communications run through Atlassian Statuspage. 18 19 2 8
The E-Commerce Operations Manager
Scheduled reports daily, weekly or monthly plus on-demand and unlimited email reports, white-label client reports, public report pages showing per-day uptime percentages and downtime history back to test creation, and retention stated per plan from 90 days of overview data up to six years on the top plan — a solid basis for showing the agency what a March outage cost us. I found no public information on response-time percentiles, published probe IP addresses for allow-listing, or a standard SLA (service-creditable SLAs appear only as a custom-plan option), and the vendor's own status communications run through Atlassian Statuspage. 2 8 12 18 19
The Information Security Officer
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. 7 8 12 18 19
The Skeptic
Retention is stated per plan and per data type — Bronze keeps 30 days of detailed test data and 90 days of overview, Gold up to 6 years of overview — and history is retrievable through the uptime API, with scheduled daily, weekly or monthly reports, on-demand reports and white-label client reporting on top. The captured pages give different figures for how long uptime results are kept ('up to a month' on the features page), and we found no public information on probe IP addresses for allow-listing, response-time percentiles, or the vendor's own public status page and incident history; an SLA with credits appears only as a custom-plan option. 2 7 8 18 19
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where account data, alert contacts (names and phone numbers of the people on call), status page subscribers and check results are stored and processed, and who the subprocessors are (hosting, SMS and phone gateways, email delivery, support and payment tools). Independently sourced by the sovereignty pipeline. Probe locations outside Europe are part of what the product does and are not counted against it; where the data is stored and who processes it is. A self-hosted or open-source edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (SMS and call gateways, email, support, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every record on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, or a self-hosted open-source edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The Agency Developer
The contracting entity is TrafficCake Limited, registered in England and Wales at Grays, personal data is stated to be primarily stored and processed in the United Kingdom, and a data processing addendum covering UK and EU GDPR is published with breach notification, audit rights, deletion on termination and standard contractual clauses for transfers outside the UK. Subprocessors are published by name and purpose — DigitalOcean, Google Cloud and Amazon Web Services for hosting, Twilio for SMS, SparkPost and Mailchimp for email, Intercom for support, Stripe and PayPal for payments, Atlassian Statuspage for status communications. The processors' own locations are not stated, no ISO 27001 or SOC 2 certification is named, and we found no public information on a self-hosted edition. 11 12 9 5
The SaaS Platform Engineer
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. 9 11 12
The Customer Support Lead
The contracting entity is TrafficCake Limited, registered in England and Wales, personal data is stated to be primarily stored and processed in the United Kingdom, a data processing addendum covering UK and EU GDPR is published with standard contractual clauses for transfers, and a subprocessor list names the cloud (DigitalOcean, Google Cloud, AWS), email (SparkPost, Mailchimp), SMS (Twilio), payment (Stripe, PayPal), support and analytics providers. The subprocessor entries give purposes but not each provider's own location, and we found no public information on security certifications such as ISO 27001 or SOC 2, or on a self-hosted edition. 11 12 5 9
The E-Commerce Operations Manager
The contracting entity is TrafficCake Limited, registered in England and Wales, personal data is primarily stored and processed in the United Kingdom, a data processing addendum covering both UK and EU GDPR is published with standard contractual clauses for transfers, and subprocessors are listed by purpose — DigitalOcean, Google Cloud and AWS for hosting, Twilio for SMS, SparkPost and Mailchimp for email, Stripe and PayPal for payments, Intercom for support, and Google Analytics, Mixpanel and Hotjar for analytics. That is a well-documented UK chain rather than a European one, and I found no public information on an EU hosting option, security certifications, or a self-hosted edition, so the phone numbers of my on-call staff travel under UK safeguards with several US processors in the chain. 9 11 12
The Information Security Officer
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. 9 11 12
The Skeptic
The contracting entity is TrafficCake Limited, registered in England and Wales, with personal data 'primarily stored and processed in the United Kingdom'; a published data processing agreement under UK and EU GDPR adds standard contractual clauses, subprocessor notice and objection rights, and a named subprocessor list — DigitalOcean, Google Cloud and Amazon Web Services for hosting, Twilio for SMS, Stripe and PayPal for payments, Intercom for support. We found no public information on security certifications or on an EU contracting entity and EU hosting option, and per-subprocessor locations are not itemised. 9 11 12
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per tier by number of monitors, check interval and status pages, team seats and on-call responders, what SMS and phone alerts cost, which features (multi-step or browser checks, SSO, longer retention, private locations, white-label) cost extra, the free tier and its limits, overage handling, minimum term and VAT.
0 — No public prices at all; every customer is a sales call.
3 — A starting price or a free tier exists, but how cost scales with monitors, intervals, seats or alerts is unclear.
5 — Tiers are public with their monitor count, interval and main inclusions, but at least one commonly needed piece (SMS or call alerts, extra seats, extra status pages, SSO, longer retention) is unpriced or "on request".
8 — Every tier priced publicly with its scaling rule (monitors, interval, seats, responders, status pages), SMS and call costs stated, add-ons priced, overage handling stated, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given number of monitors, interval, team size and alert volume, with every add-on, overage and support fee and the cancellation and data-return terms published.
The Agency Developer
Public tiers carry monitor counts, intervals and team logins, so a two-hundred-monitor agency case is computable from the pricing page: Business at €69.99/mo or €699.96 billed yearly includes 300 uptime monitors, 30-second intervals, ten team logins and 400 SMS credits, with a free tier, a seven-day trial without credit card and cancellation any time. SMS is allocated as credits rather than priced per message, the Custom plan is POA, and VAT treatment and overage handling are not stated. The captured pages give different figures for the free plan's monitor count and different plan sets (Free, Superior, Business against Bronze, Silver, Gold), so I would confirm current tiers before committing sixty clients. 8 5 13
The SaaS Platform Engineer
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. 8 5 13
The Customer Support Lead
Tiers are priced publicly with their monitor counts per type, check intervals, status pages, subscriber limits and team logins (Superior €19.99/mo and Business €69.99/mo, with "Get 2 months free (save 16%)" on annual billing), a free tier and a seven-day trial without a credit card exist, and cancellation is stated as possible at any time. The captured pages give different figures for the free plan's uptime tests — three monitors at fifteen-minute intervals on the pricing page, ten tests at five-minute rates on the free-monitoring page — and the custom plan is priced on application. We found no public information on VAT treatment, overage handling, extra seats beyond the plan logins, or the price of SMS and phone alerts beyond the included credits. 5 8 13
The E-Commerce Operations Manager
Tiers are public with monitor counts, intervals, logins, page-speed and server monitors and SMS credits — for example €69.99/mo with 300 uptime monitors at 30-second intervals, 10 logins and 400 SMS credits — alongside a free tier, a seven-day trial with no credit card, monthly or annual billing with two months free on the year, and cancellation at any time. I found no public information on the cost of SMS or calls beyond the plan credits, overage handling, bolt-on prices (the custom plan is quoted "POA") or VAT treatment, and the captured pages give different figures for the free plan's monitor count and interval. 5 8 13
The Information Security Officer
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. 5 8
The Skeptic
The pricing page publishes tiers with monitor counts by type, intervals, logins and SMS credits (Superior at €19.99/mo with 100 uptime monitors and 75 SMS credits; Business at €69.99/mo with 300 monitors and 400 credits), plus a free tier, a 7-day trial without credit card and cancellation at any time. The captured pages give different figures for the free plan's uptime tests and present two different plan line-ups (Bronze, Silver and Gold against Superior and Business), and we found no public information on per-message SMS or phone call costs beyond the bundled credits, VAT treatment or overage handling. 5 8 13
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined ⚠ unverified | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about StatusCake
Is StatusCake European?
Yes, though not from the EU. whats-best.ai classifies StatusCake as UK / wider Europe.
Where does StatusCake store data?
Not stated on the vendor’s pages as of 1 Nov 2026.
Does StatusCake have a free plan?
Yes. StatusCake has a free plan, per the vendor’s page captured 1 Nov 2026.
What are the best alternatives to StatusCake?
As of 2 Nov 2026, the panel rates Hyperping (3.5/5), Checkly (3.5/5) and openstatus (3.5/5) highest among the other 14 Uptime Monitoring & Status Pages products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Hyperping (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: StatusCake alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement, Legal entity, Hosting location. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 5 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 product fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (20)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.statuscake.com Checked 1 Nov 2026 Details →
- 2 Features page (uptime monitoring) www.statuscake.com Checked 1 Nov 2026 Details →
- 3 Features page (SSL monitoring) www.statuscake.com Checked 1 Nov 2026 Details →
- 4 Features page (domain monitoring) www.statuscake.com Checked 1 Nov 2026 Details →
- 5 Features page (status pages) www.statuscake.com Checked 1 Nov 2026 Details →
- 6 Integrations page www.statuscake.com Checked 1 Nov 2026 Details →
- 7 API documentation developers.statuscake.com Checked 1 Nov 2026 Details →
- 8 Pricing page www.statuscake.com Checked 1 Nov 2026 Details →
- 9 About page (registered address) www.statuscake.com Checked 1 Nov 2026 Details →
- 10 Terms of service www.statuscake.com Checked 1 Nov 2026 Details →
- 11 Privacy policy www.statuscake.com Checked 1 Nov 2026 Details →
- 12 Data processing agreement (dpa) www.statuscake.com Checked 1 Nov 2026 Details →
- 13 Checks, locations & failure confirmation — found from sitemap www.statuscake.com Checked 1 Nov 2026 Details →
- 14 Checks, locations & failure confirmation — found from sitemap www.statuscake.com Checked 1 Nov 2026 Details →
- 15 Alerting, escalation & on-call — found from sitemap www.statuscake.com Checked 1 Nov 2026 Details →
- 16 Alerting, escalation & on-call — found from sitemap www.statuscake.com Checked 1 Nov 2026 Details →
- 17 Status pages & incident communication — found from sitemap www.statuscake.com Checked 1 Nov 2026 Details →
- 18 Uptime reports, data & the vendor's own reliability — found from sitemap www.statuscake.com Checked 1 Nov 2026 Details →
- 19 Uptime reports, data & the vendor's own reliability — found from sitemap www.statuscake.com Checked 1 Nov 2026 Details →
- 20 Code repository (open-source licence) — found from the homepage github.com Checked 1 Nov 2026 Details →