# Uptrends — Uptime Monitoring & Status Pages

Uptrends by Uptrends B.V. holds a panel rating of 3/5 from 6 AI judges (category median 2.5/5), as of 2026-11-11. Provenance: provenance unknown; sovereignty: not determined.

- Vendor: Uptrends B.V. (https://www.uptrends.com)
- Category: [Uptime Monitoring & Status Pages](https://whats-best.ai/software/uptime-monitoring.md)
- Provenance (editorial classification): provenance unknown
- Canonical page: https://whats-best.ai/software/uptime-monitoring/uptrends
- Alternatives: https://whats-best.ai/software/uptime-monitoring/uptrends/alternatives ([markdown](https://whats-best.ai/software/uptime-monitoring/uptrends/alternatives.md))
- Data as of: 2026-11-22 · evaluated 2026-11-11 · oldest source captured 2026-11-10

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## At a glance

- Vendor: Uptrends B.V.
- Headquarters: Not stated on the vendor’s pages as of 10 Nov 2026
- Data hosting: Not stated on the vendor’s pages as of 10 Nov 2026
- Free plan: Not stated on the vendor’s pages as of 10 Nov 2026

## The panel's verdict

Uptrends B.V., an uptime monitoring and status page service, is strongest where the bench scored it highest — checks and locations at 7-8 — with multi-step checks in real browsers covering MFA and SSO journeys from 230+ ISP-based checkpoints worldwide or private locations, and an alert raised only after a second checkpoint duplicates the error. Alerting and on-call and automation and teams follow, backed by a documented Monitor API and a Terraform provider with Git-based version control, though Terraform is for Enterprise-level accounts. Status pages is the weakest area at 4, and we found no public information on custom domains, subscriber notifications or incident updates. The judges genuinely split on sovereignty, 0 to 3: the 3 credits the Dutch company form on record, while the 0s record no public information on data storage locations, subprocessors or a data processing agreement. Reports and reliability clusters at 6 with retention stated per plan; the captured pages give different figures — three and four — for the maximum number of escalation levels, and show no price figures.

**Speaks for it:**
- Checks and locations scored the highest cluster at 7-8 for multi-step, real-browser journey checks covering MFA and SSO from 230+ ISP-based checkpoints worldwide.
- An alert sounds only after a different checkpoint duplicates the error, and maintenance windows suppress checks.
- A documented Monitor API with create, update, clone and delete, plus a Terraform provider with Git-based version control, manage monitors as code.
- Retention is published per plan and data type — individual check data 14 to 90 days, statistical SLA data up to two years.
- Alerting spans email, SMS, phone/voice, mobile push, webhooks and forwarding to PagerDuty, Opsgenie and Splunk On-Call.

**Held against it:**
- Status pages drew the lowest scores at 4, with no public information found on custom domains, subscriber notifications or incident updates.
- Protected status pages and Terraform support sit on the Enterprise plan, and SLA monitoring on Business and Enterprise.
- Sovereignty scores split 0 to 3, with no public information on data storage locations, subprocessors or a data processing agreement.
- The captured pages give different figures for the maximum number of escalation levels — three and four.
- No price figures for the five named tiers appear on the captured pages, though a 30-day free trial without credit card is offered.

**Best for:**
- You watch checkout, payment or MFA/SSO login journeys end to end and want alerts confirmed from a second checkpoint before anyone is paged.
- You manage monitoring as code and want a documented Monitor API plus a Terraform provider with Git-based version control and an import workflow.
- You need SLA evidence to hand a customer or agency, with statistical uptime and calculated SLA data kept up to two years and individual check data up to 90 days.

**Avoid if:**
- Your procurement must see documented data residency, subprocessors or a data processing agreement before signature.
- Your security sign-off depends on account-level single sign-on, SCIM provisioning or audit logs being documented up front.
- Your customer communication during outages leans on status page subscriber notifications, custom domains or per-component uptime history.

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v1). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The Agency Developer | The SaaS Platform Engineer | The Customer Support Lead | The E-Commerce Operations Manager | The Information Security Officer | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| Checks, locations & failure confirmation | 3.5/5 | 4/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Alerting, escalation & on-call | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3/5 | 3.5/5 |
| Status pages & incident communication | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 |
| API, monitoring as code & team administration | 3.5/5 | 3.5/5 | 3/5 | 3/5 | 3/5 | 3.5/5 |
| Uptime reports, data & the vendor's own reliability | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 |
| European sovereignty | 1.5/5 | n/r | n/r | n/r | n/r | n/r |
| Pricing transparency | n/r | n/r | n/r | n/r | n/r | n/r |
| **Weighted verdict** | **3/5** | **3.5/5** | **3/5** | **3/5** | **3/5** | **3/5** |

### The judges

- **The Agency Developer** (v1.0): Runs hosting and maintenance at a fifteen-person web agency with sixty client sites on WordPress, TYPO3 and Shopware. Has learned about an expired certificate from a client's angry phone call once and does not want a second time. Wants HTTP, keyword, SSL and domain expiry checks set up in bulk, client groups with their own status pages and monthly uptime reports, and a price per monitor that still works at two hundred monitors.
- **The SaaS Platform Engineer** (v1.0): Platform engineer at a forty-person B2B SaaS in Berlin, one of four people on the on-call rotation. Wants multi-step API checks with assertions, kept in Terraform next to the services they test, failures confirmed from a second location before anyone is woken, phone calls and escalation when an alert is not acknowledged, and a status page that updates without someone logging in at 3 a.m.
- **The Customer Support Lead** (v1.0): Leads a support team of nine at a software company whose customers are tax advisers and payroll offices. During the last outage the team answered three hundred tickets that all asked the same question. Wants a status page on the company's own domain with components customers recognise, incident templates, subscribers notified by email, a private page for the largest accounts, and an uptime history they can point to in a contract renewal.
- **The E-Commerce Operations Manager** (v1.0): Runs operations for an online shop selling garden furniture in Germany, Austria and Switzerland, with half the year's revenue between March and June. The homepage once answered 200 while the checkout threw an error for six hours. Wants the checkout and the payment page checked, not only the homepage, an SMS or call to whoever is on duty that night, and a report that shows the agency what the downtime cost.
- **The Information Security Officer** (v1.0): Information security officer at a mid-sized logistics company that falls under NIS2 and is working towards ISO 27001. Needs every outage recorded with detection time, response and resolution, in a form an auditor accepts. Reads the subprocessor list before the feature page, because the on-call staff's mobile numbers and the status page subscribers are personal data, and wants single sign-on and an audit log before anyone gets a login.
- **The Skeptic** (v1.0): Has seen "30-second checks from 20 locations" that paged the whole team for a single probe's network glitch, a status page that went down with the product it reported on, and "unlimited SMS" with a fair-use clause on page nine. Asks how a failure is confirmed, how long the history is kept and whether it can be exported, where the monitor itself publishes its own outages — and what leaving would cost.

## European sovereignty — proven facts

No sovereignty finding yet.

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Data**
- Fpc plus retention: 21 · yes [S11]
- Infra individual measurements: device logs · screenshots from http sensors · individual sensor values · individual error information · 90 [S11]
- Infra individual per plan: 30 · 14 · 90 · 60 [S11]
- Infra statistical: average sensor values · day averages · total errors per day · total device uptime per day · last device statuses · last sensor values · alerts · 2 [S11]
- Infra statistical per plan: 1 · 2 [S11]
- Plan tiers: Starter · Premium · Professional · Business · Enterprise [S11]
- Retention paid plans: paid subscription plans · yes [S11]
- Rum five minute intervals: five minutes · 90 [S11]
- Rum hourly intervals: one hour · 2 [S11]
- Rum per plan: 1 · 2 · 30 · 14 · 90 · 60 [S11]
- Scheduled reports history: PDF reports · Excel reports · E-mail reports · 2 · History tab of scheduled report [S11]
- Scheduled reports per plan: 1 · 2 [S11]
- Synthetics individual measurements: individual monitor check data · monitor check screenshots · FPC waterfall data · transaction detail data · 90 [S11]
- Synthetics individual per plan: 30 · 14 · 90 · 60 [S11]
- Synthetics statistical: average uptime % · average load time · calculated SLA data · 2 [S11]
- Synthetics statistical per plan: 1 · 2 [S11]

**Integrations**
- API: yes [S1]
- API: yes [S5]
- API documentation interactive: yes [S8]
- Grafana: yes [S10]
- Monitor API auth prerequisite: Requires Uptrends API credentials and monitor management permissions [S8]
- Monitor API endpoints: GET /Monitor · POST /Monitor · GET /Monitor/{monitorGuid} · PATCH /Monitor/{monitorGuid} · PUT /Monitor/{monitorGuid} · DELETE /Monitor/{monitorGuid} · POST /Monitor/{monitorGuid}/Clone [S8]
- Monitor API group endpoints: GET /Monitor/{monitorGuid}/MonitorGroup/ · GET /Monitor/MonitorGroup/{monitorGroupGuid} · POST /Monitor/MonitorGroup/{monitorGroupGuid} [S8]
- Named services: Slack, PagerDuty, StatusHub, ServiceNow, Splunk On-Call, Microsoft Teams, Zapier, Opsgenie, Statuspage, custom webhook [S5]
- Opentelemetry: OpenTelemetry-compatible streaming · yes [S1]
- Status pages related: Knowledge base documents setup of public and protected status pages [S6]
- Terraform API key auth: Uptrends API key / API user credentials · yes [S9]
- Terraform config download: yes [S9]
- Terraform gitops: yes · Git [S9]
- Terraform hub purpose: operators · monitors · alert definitions · vault items [S9]
- Terraform import workflow: terraform plan -generate-config-out · yes [S9]
- Terraform provider: Terraform Provider · yes [S1]
- Terraform registry provider: 1.1.1 · ITRS-Group/itrs-uptrends · registry.terraform.io [S9]
- Terraform resource crud: yes [S9]

**Legal**
- Copyright: 2007-2026 [S1]
- Copyright notice: 2007-2026 [S10]

**Pricing**
- SLA plan requirement: Business · Enterprise · yes [S10]
- Trial: 30 · yes · no [S1]

**Product**
- Additional APIs: MonitorCheck API · MonitorGroup API · API changelog [S8]
- Agentic monitor setup: yes [S1]
- Alert channels: email, SMS/text, phone/voice, mobile apps, integrations, webhooks [S5]
- Alert testing: yes [S4]
- Alert triggers: Alerts can be generated when errors occur for a specific period of time or when a specific number of errors have occurred [S4]
- Alert triggers: performance, max/min page or element sizes, missing content [S5]
- Alerting integrations: yes [S1]
- API error status codes: 200 · 204 · 400 · 401 · 403 · 404 · 500 [S8]
- API field deprecation notice: /Monitor · /Monitor/{monitorGuid} · 2025-08-27 [S8]
- Auth retry: Requests with authentication information may be retried before declaring failure [S3]
- Checkpoint locations: yes · 230+ [S1]
- Checkpoint selection: Uptrends randomly picks one of the user's designated worldwide checkpoints for each HTTP/HTTPS check [S3]
- Checkpoints worldwide: checks run from designated checkpoints worldwide [S2]
- Clone monitor initially inactive: yes [S8]
- Cloud provider comparison: cloud-provider checks contrasted with ISP-based monitoring [S1]
- Components: Uptrends Synthetics · Uptrends Real User Monitoring · Uptrends Infra [S11]
- Custom integration message types: error · reminder · OK · no [S4]
- Custom message integrations: Slack · PagerDuty · email [S4]
- Dns resolution step: HTTP monitor first attempts DNS resolution of the specified domain name [S3]
- Double confirmation: yes [S5]
- Duty schedules: yes [S5]
- Error confirmation: retry from a different checkpoint; alert only if error is duplicated from that checkpoint [S3]
- Error snapshots: error snapshots for HTTPS availability and transaction monitors; screenshots addable to Web Application Monitoring steps [S5]
- Escalation config: escalation triggers by error duration or error count; reminders and method/recipient changes possible [S5]
- Escalation level contents: alert generation · number of reminders · notification method · recipients · alert definition [S4]
- Escalation levels: 4 [S5]
- Escalation levels max: 3 [S4]
- Extra email recipients: yes [S4]
- Free tools: uptime check · website speed test · traceroute · DNS Checker · CDN performance check · SLA & uptime calculator · ping test · IPv6 ping test · free website monitoring · find my website's IP address · response header check [S1]
- Http https checks scope: basic checks: response status codes, page load time, loading of content resources [S2]
- Http monitor deprecated for new users: HTTPS monitors extended to check HTTP websites · yes [S2]
- Http monitor full page check recommendation: Uptrends recommends Full Page check for in-depth checks [S2]
- Http version default: Negotiate · yes [S2]
- Https failure retries: On HTTPS request failure, Uptrends may retry several times with different security protocols before declaring failure [S3]
- Incident management: yes [S5]
- Ip address option: IP address can be specified instead of domain to skip DNS resolution, but no alert will be issued for resolve issues [S3]
- Low code setup: yes [S1]
- Maintenance windows: yes [S5]
- MFA SSO journeys: yes [S1]
- Mobile push: yes · iOS · Android [S5]
- Modules: Synthetics · RUM · Infra [S1]
- Monitor API bulk definitions: bulk view of monitor definitions [S8]
- Monitor API crud: create, update, clone, delete monitors via API [S8]
- Monitor API fields: MonitorGuid · MonitorType · GenerateAlert · IsActive [S8]
- Monitor API maintenance scheduling: yes [S8]
- Monitor API purpose: Monitor API provides endpoints to manage monitor settings and configuration [S8]
- Network error traceroute: On network errors, Uptrends performs a traceroute to the IP address using ICMP ping packets [S3]
- Observability recognition: 2025 · Gartner Magic Quadrant for Digital Experience Monitoring · Visionary [S1]
- Ok reminder alert control: yes [S4]
- Operator activity requirement: Alerts are sent only if the designated operator is active and on-duty [S4]
- Predefined integrations: email · SMS (uses message credits) · phone [S4]
- Private locations: private monitoring locations · yes [S1]
- Protected status page access methods: yes [S7]
- Protected status page admin access: yes [S7]
- Protected status page auth: yes [S7]
- Protected status page definition: A protected status page is a published dashboard accessible only to a well-defined public, secured by a login [S6]
- Protected status page enterprise only: Enterprise · yes [S7]
- Protected status page viewer permissions: yes [S7]
- Protected status page visibility: yes [S7]
- Public status page capability: Public status pages publish uptime information for monitors to the general public [S7]
- Public status page definition: A public status page is a special kind of dashboard published for a broad audience to keep customers up-to-date on website status [S6]
- Real browsers: yes [S1]
- Second tcp connection: A new TCP connection is opened to send the HTTP(S) request and the response is awaited [S3]
- SLA data recalculation: yes [S10]
- SLA definition: SLA monitoring lets users monitor SLAs with providers or SLAs they provide to customers [S10]
- SLA multiple definitions: yes [S10]
- SLA reporting export: yes [S10]
- SMS voice credit usage: yes [S4]
- Solutions: Website Monitoring · Synthetic Monitoring · Web Application Monitoring · Web Performance Monitoring · API Monitoring · Real User Monitoring · Mobile Website Monitoring · Server Monitoring · External Server Monitoring · Cloud Cost Management [S1]
- Status page content: yes [S7]
- Status page customization: yes [S7]
- Tcp ports: 80 · 443 · yes [S3]
- Terraform enterprise only: yes · Enterprise-level accounts [S9]
- Terraform hub admin default: administrators · yes [S9]
- Terraform iac management: monitors · alerting configurations · other resources · Infrastructure as Code management of Uptrends monitoring setup [S9]
- Third party integrations: PagerDuty · Microsoft Teams · Slack · StatusHub [S4]
- TLS default versions: TLS 1.2 · TLS 1.1 · yes [S2]
- Traceroute email option: yes [S4]
- Vendor: Uptrends (ITRS Uptrends), copyright 2007-2026 [S8]

**Support**
- Channels: support contact offered; Uptrends Basics docs referenced for setup help [S5]
- Monitor API support: yes [S8]
- Protected status page setup requires support: Enabling external access to protected status pages requires Support confirmation of granted permissions [S7]
- Terraform support team: Support team [S9]

## Questions

### Is Uptrends European?

Not determined: the vendor’s pages as captured do not say where Uptrends is based.

### Where does Uptrends store data?

Not stated on the vendor’s pages as of 10 Nov 2026.

### Does Uptrends have a free plan?

Not stated on the vendor’s pages as of 10 Nov 2026.

### What are the best alternatives to Uptrends?

As of 19 Nov 2026, the panel rates [Hyperping (3.5/5)](https://whats-best.ai/software/uptime-monitoring/hyperping), [Uptimia (3.5/5)](https://whats-best.ai/software/uptime-monitoring/uptimia) and [Checkly (3.5/5)](https://whats-best.ai/software/uptime-monitoring/checkly) highest among the other 23 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](https://whats-best.ai/software/uptime-monitoring/hyperping) (EU-Made, France). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [Uptrends alternatives](https://whats-best.ai/software/uptime-monitoring/uptrends/alternatives).

## What this page leaves out

- We found no public information on compliance on the pages we read (uptrends.com, uptrends.com/support/kb/synthetic-monitoring/uptime-monitoring/http-and-https/http-and-https-overview, uptrends.com/support/kb/synthetic-monitoring/uptime-monitoring/http-and-https/how-an-http-monitor-works, uptrends.com/support/kb/alerting/alert-escalation-levels, uptrends.com/features/alerting, uptrends.com/support/kb/dashboards-and-reporting/status-pages/status-pages-overview and 5 more). If the vendor publishes it somewhere else, send us the page.
- 13 product 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.
- 7 integrations 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.
- 1 legal 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.
- 1 pricing 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.

## Sources

- [S1] Vendor page: https://www.uptrends.com (checked 2026-11-10)
- [S2] Checks, locations & failure confirmation — found from sitemap: https://www.uptrends.com/support/kb/synthetic-monitoring/uptime-monitoring/http-and-https/http-and-https-overview/ (checked 2026-11-10)
- [S3] Checks, locations & failure confirmation — found from sitemap: https://www.uptrends.com/support/kb/synthetic-monitoring/uptime-monitoring/http-and-https/how-an-http-monitor-works/ (checked 2026-11-10)
- [S4] Alerting, escalation & on-call — found from sitemap: https://www.uptrends.com/support/kb/alerting/alert-escalation-levels/ (checked 2026-11-10)
- [S5] Alerting, escalation & on-call — found from sitemap: https://www.uptrends.com/features/alerting/ (checked 2026-11-10)
- [S6] Status pages & incident communication — found from sitemap: https://www.uptrends.com/support/kb/dashboards-and-reporting/status-pages/status-pages-overview/ (checked 2026-11-10)
- [S7] Status pages & incident communication — found from sitemap: https://www.uptrends.com/support/kb/dashboards-and-reporting/status-pages/public-and-protected-status-pages/ (checked 2026-11-10)
- [S8] API, monitoring as code & team administration — found from sitemap: https://www.uptrends.com/support/kb/api/monitor-api/ (checked 2026-11-10)
- [S9] API, monitoring as code & team administration — found from sitemap: https://www.uptrends.com/support/kb/terraform/terraform/ (checked 2026-11-10)
- [S10] Uptime reports, data & the vendor's own reliability — found from sitemap: https://www.uptrends.com/support/kb/dashboards-and-reporting/sla/ (checked 2026-11-10)
- [S11] Uptime reports, data & the vendor's own reliability — found from sitemap: https://www.uptrends.com/support/kb/dashboards-and-reporting/dashboards/data-retention/ (checked 2026-11-10)

---

Cite as: whats-best.ai, "Uptrends — Uptime Monitoring & Status Pages", AI panel analysis, as of 2026-11-22. https://whats-best.ai/software/uptime-monitoring/uptrends

Corrections: https://whats-best.ai/correct/1875?target=page
