Uptime Monitoring & Status Pages
Instatus
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Instatus, Inc. · instatus.com
Compare with Atlassian Statuspage → 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.
Instatus at a glance
- Vendor
- Instatus, Inc.
- Headquarters
- Incorporated in United States source, captured 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 Instatus 2.5/5, the mean of 6 judges. Instatus is a status-page service with built-in uptime monitoring, and the bench scored it in that shape: status pages led at 7-8, alerting and on-call scored 6, automation and teams 5-6, reports and reliability 4-5, pricing transparency 4-5, while checks and locations sat at 4 and sovereignty at 3 with no spread on either. 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
Instatus is a status-page service with built-in uptime monitoring, and the bench scored it in that shape: status pages led at 7-8, alerting and on-call scored 6, automation and teams 5-6, reports and reliability 4-5, pricing transparency 4-5, while checks and locations sat at 4 and sovereignty at 3 with no spread on either. The documented checks are TCP, UDP and DNS record monitors run from the United States, Canada, Europe or Asia at intervals down to 30 seconds on paid plans; we found no public information on HTTP keyword or SSL certificate checks, or on confirming a failure from a second location before an alert fires. The single-point spreads reflect emphasis rather than conflict — the flagged splits found none to report — and the Information Security Officer's 8 on status pages cites single sign-on for private pages. Pricing publishes detailed tier limits but no amounts for Pro or Business; sovereignty rests on a Delaware entity, primary United States storage, an automatically applied data processing addendum and Standard Contractual Clauses.
Speaks for it
- Status pages scored 7-8, the bench's highest, with components, groups, per-component uptime history and subscriber channels across email, SMS, webhook, Slack, Teams, Discord, X and RSS.
- Private or audience-specific status pages can be signed into with single sign-on — SAML, plus OpenID and CAS — on the Business plan.
- On-call schedules support daily, weekly and custom rotations with time-of-day restrictions, managed through a documented API.
- The SLA is public — 99% on paid self-serve plans and 99.99% on Enterprise — with a service-credit formula of ten times the hourly plan cost per day of more than five minutes' downtime, capped at that month's payment, and a 30-day claim window.
- Monitoring tools such as Pingdom, Datadog, New Relic and Prometheus can create status-page incidents automatically through the REST API.
Held against it
- Monitoring is documented as TCP, UDP and DNS record checks, and we found no public information on HTTP keyword, SSL certificate expiry or heartbeat checks.
- We found no public information on confirming a failure from a second location before an alert fires.
- Sovereignty scored 3 with no spread: the vendor is a Delaware corporation whose privacy policy states data is stored primarily in the United States, and we found no public information on an EU hosting option or security certifications.
- The captured pricing page shows no amounts for the Pro and Business tiers, and per-message SMS and call costs are not stated because messaging runs through the customer's own gateway account.
- We found no public information on audit logs, retention of check results, scheduled reports or response-time percentiles.
Best for
- You need a customer-facing status page at the centre of your incident communication, with components and per-component uptime history on a custom domain.
- You serve enterprise accounts that need private or audience-specific status pages behind single sign-on.
- You already run Pingdom, Datadog, New Relic, Prometheus or similar and want detected outages published to your status page automatically.
- You run an on-call rota that needs daily, weekly or custom rotations with time-of-day restrictions.
Avoid if
- You require EU data residency or a European contracting entity — the vendor is a Delaware corporation storing data primarily in the United States, with EEA transfers relying on Standard Contractual Clauses.
- Your monitoring must catch application-level failures such as a broken checkout behind a responding homepage — the documented checks cover network ports and DNS records.
- You want alerting costs billed by the vendor — SMS and calls run through your own Twilio, Vonage, Esendex, Bird or AWS SNS account.
- You need published prices to budget against — the captured pricing page gives no figures for the Pro and Business tiers.
The scores
| Criterion | Panel median |
|---|---|
| Checks, locations & failure confirmation | 2 of 5 |
| Alerting, escalation & on-call | 3 of 5 |
| Status pages & incident communication | 3.5 of 5 |
| API, monitoring as code & team administration | 3 of 5 |
| Uptime reports, data & the vendor's own reliability | 2.5 of 5 |
| European sovereignty | 1.5 of 5 |
| Pricing transparency | 2 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
The help pages document DNS, TCP and UDP checks run from the United States, Canada, Europe and Asia, a configurable interval that reaches 30 seconds on paid plans, and automatic incident creation plus auto-resolution on recovery. For my client sites I specifically need keyword and certificate-expiry checks, and we found no public information on HTTP keyword checks, SSL certificate or domain expiry checks, cron or heartbeat monitoring, or a re-check from a second location before an alert fires. 4 7 8 15
The SaaS Platform Engineer
TCP, UDP and DNS monitors run from named regions at intervals down to thirty seconds, with connection time, latency and packet loss measured, down and degraded states, and recovery that resolves incidents and republishes the status page automatically. We found no public information on HTTP keyword, SSL expiry, cron or heartbeat checks, on multi-step API or browser checks of a user flow, on private locations inside our network, or on a re-check from a second location before anyone is alerted. 4 7 8
The Customer Support Lead
The help pages document TCP, UDP and DNS record checks run from the United States, Canada, Europe and Asia, with a configurable interval down to 30 seconds on paid plans, connection time and latency measured, and automatic incident creation on failure and on recovery. We found no public information on HTTP or keyword checks, SSL certificate and domain expiry, cron or heartbeat monitoring, re-checking from a second location before an alert, or private locations inside a customer network, so the detection story rests on network-layer and DNS checks. 4 7 8
The E-Commerce Operations Manager
TCP, UDP and DNS monitors run from the United States, Canada, Europe and Asia, with configurable frequency down to 30 seconds on the paid tiers and latency or response statistics recorded per check. But we found no public information on HTTP keyword checks or browser and transaction checks of a checkout flow, and nothing on confirming a failure from a second location before alerting — so these pages only prove the domain, its records and its ports are watched, not that a broken checkout would be caught while the homepage still answers fine. 4 7 8
The Information Security Officer
The captured help pages document DNS A and MX record checks, TCP and UDP reachability checks with connection time, latency and packet-loss measurement, a configurable interval down to 30 seconds on paid plans, and a choice of running from the United States, Canada, Europe or Asia. Failure and recovery actions are specified (create an incident, notify subscribers, auto-resolve and update the status page). We found no public information on HTTP keyword checks, ping, SSL certificate expiry, cron or heartbeat monitoring, or on any confirmation from a second location before an alert fires — which is the false-positive control an auditor would ask me to evidence. 4 7 8 15
The Skeptic
TCP, UDP and DNS checks run from the United States, Canada, Europe or Asia at intervals down to 30 seconds on paid plans, with latency, packet loss and record values logged and failures turned into incidents automatically. Regions are named only at continent level, though, and we found no public information on HTTP, keyword, SSL, ping or heartbeat checks, on maintenance windows that pause checks, or on how a failure is confirmed before an alert fires. 4 7 8
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
Alert channels scale from Email to Email & SMS to SMS & Calls across the plans, incident escalations are a listed feature, and the on-call API documents daily, weekly and custom rotations with time-of-day and time-interval restrictions — enough to run a real rota. We found no public information on acknowledging or resolving from the app, alert grouping or maintenance windows that mute alerts, and SMS runs through your own Twilio, Vonage, Esendex, Bird or AWS SNS account, so no per-message price appears. 2 4 9 10
The SaaS Platform Engineer
The Business tier adds SMS and phone call alerts plus incident escalations, and on-call schedules with daily, weekly or custom rotations and time restrictions are managed through a documented API; SMS runs through a provider we connect ourselves, such as Twilio or Vonage. We found no public information on acknowledging alerts from the app, escalation timeout detail, alert grouping or maintenance windows that mute alerts, and the PagerDuty integration flows inbound, creating status-page incidents from PagerDuty rather than forwarding our alerts out. 4 9 10 12
The Customer Support Lead
Email alerts start on the free tier, SMS arrives on Pro and SMS with calls on Business, and on-call schedules with daily, weekly and custom rotations plus time-of-day restrictions are documented through the schedules API, with incident escalations listed on the pricing page. SMS runs through a provider the customer connects themselves — Twilio, Esendex, Vonage, Bird or AWS SNS — and subscribers can be reached by email, webhook, chat channels and RSS. We found no public information on escalation timeouts, acknowledging or resolving from the app or chat, alert grouping, or maintenance windows that mute alerts. 4 9 10 12
The E-Commerce Operations Manager
The Business tier lists SMS and call alerts, on-call schedules support daily, weekly and custom rotations with time-of-day restrictions, and email, Slack, Microsoft Teams, Discord and signed webhooks are all documented — that is the night-call setup I need. We found no public information on acknowledging and resolving from the app, alert grouping, escalation timeout rules, or per-country prices for SMS and calls, since SMS runs through your own Twilio, Vonage, Esendex, Bird or AWS account. 4 9 10 12
The Information Security Officer
Alerting spans email, SMS and phone calls by tier, chat channels including Slack, Microsoft Teams, Discord and Google Chat, signed webhooks, and bring-your-own SMS gateways such as Twilio, Esendex, Vonage, Bird and AWS SNS. On-call schedules with daily, weekly and custom rotations and time-of-day restrictions are documented through a full create, read, update and delete API, and incident escalations are listed as a paid feature. We found no public information on escalation timeouts, acknowledging or resolving from the app, alert grouping, or incident timelines showing who did what — the records I would need for detection, response and resolution evidence. 2 4 5 9 10
The Skeptic
On-call schedules with daily, weekly and custom rotations and time-of-day restrictions, incident escalations, phone-call alerts on the Business plan, and Slack, Teams, Discord, Google Chat and webhook channels are documented; SMS runs through your own gateway credentials (Twilio, Vonage, Esendex, Bird or AWS SNS), so per-message prices never appear on the vendor's pages. We found no public information on escalation timeouts, acknowledging or resolving from the app, alert grouping, or incident timelines. 2 4 9 10
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
This is clearly the core of the product: components with their own uptime history and groups, subscriber channels from email and SMS to Slack, Discord, X, RSS and the public API with CSV import, custom domains, and private or audience-specific pages whose login runs through the single sign-on setup — audience-specific pages are exactly what I want per client. We found no public information on multiple languages, incident templates, embeddable widgets or custom branding in the captured pages. 4 5 10 11 12 13
The SaaS Platform Engineer
This is the centre of the product: custom domains, components and component groups with per-component historical uptime, subscriber channels across email, SMS, webhook, RSS, X and chat with per-component SMS subscriptions, private and audience-specific pages, and single sign-on covering private status page login. We found no public information on removable branding or custom CSS, page languages, embeddable widgets beyond the Intercom one, or how the page hosting is kept separate from the main service. 4 5 10 11 12 13
The Customer Support Lead
This is what my team needs after our last outage: components with groups and per-component uptime history on a custom domain, subscribers notified by email, SMS, webhook, Slack, Teams, Discord, X and RSS with per-component notification choices, and pages that can instead be private or audience-specific, with single sign-on covering private status page login for our largest accounts. We found no public information on incident templates, pages in several languages, embeddable status widgets, or how the status page hosting is kept separate from the main service. 4 5 11 12 13
The E-Commerce Operations Manager
Components and component groups with per-component uptime history, subscribers reachable by email, SMS, webhook, Slack, Teams, Discord, X and RSS, per-component notification choices, and private or audience-specific pages with single sign-on covering private status page logins. We found no public information on incident templates, embeddable widgets, several page languages, or how the status page hosting is kept separate from the main service. 4 5 10 11 12 13
The Information Security Officer
This is the product's core: components with groups, per-component uptime history and third-party dependencies such as AWS and Stripe; custom domains on paid tiers; subscribers notified by email, SMS, webhook, Slack, Teams, Discord, X, RSS and API with per-component subscription choice and signed webhook payloads. Pages can be private or audience-specific, and a private status page can be signed into with SAML single sign-on, which is exactly what I need before pointing customers at one. We found no public information on page languages, incident templates, embeddable widgets or separation of the status page hosting from the main service; the vendor does publish its own availability at instat.us with maintenance announced 48 hours in advance. 4 5 10 11 12 13 15
The Skeptic
Components and component groups with per-component uptime history, subscribers over email, SMS, webhook, chat, X and RSS with per-component notification choices, custom domains on paid plans, and private or audience-specific pages whose login can use single sign-on on the Business plan are all documented. We found no public information on page languages, embeddable status widgets, or how the page itself stays online when the main service is down. 4 5 11 12 13
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
Single sign-on with SAML, OpenID and CAS plus SCIM directory sync and multiple SSO connections are documented for the Business plan, the API covers status page updates, on-call schedules and third-party monitoring integrations, and Zapier and Jira are listed. We found no public information on team roles, audit logs, client sub-accounts with their own logins, white-label reporting or a bulk import of monitors — which is how I would set up sixty client checks in one go. 2 4 9 13 14
The SaaS Platform Engineer
There is a documented REST API for status-page integrations and on-call schedules with signed webhook payloads, Zapier and Jira, SAML single sign-on with many identity providers, SCIM directory sync, and team-member counts per tier. We found no public information on a Terraform provider or any monitoring-as-code workflow, on creating monitors by API, on role-based permissions, audit logs, client sub-accounts or two-factor authentication for accounts. 2 4 9 12 13 14
The Customer Support Lead
A documented REST API covers status pages, incidents, monitoring integrations and on-call schedules, email subscribers import from CSV, and SAML single sign-on plus SCIM directory sync are sold and documented with setup through the OrbitID identity platform supporting Okta, Google, Microsoft and more. We found no public information on a Terraform provider or monitoring-as-code workflow, checks triggered from CI/CD, audit logs, team member roles, or client sub-accounts with their own logins. 2 4 9 12 13 14
The E-Commerce Operations Manager
A documented REST API covers status page updates, on-call schedules and monitoring integrations, SAML single sign-on with SCIM provisioning is available on the Business plan through their identity platform, and subscribers can be bulk-imported from CSV. We found no public information on a Terraform provider or any monitoring-as-code workflow, audit logs, client sub-accounts, or white-label reports for agencies. 2 4 9 13 14
The Information Security Officer
A documented REST API covers status page updates, monitoring-tool integrations and on-call schedules, with signed webhooks, CSV subscriber import and export, and Zapier and Jira integrations; SAML single sign-on (Business plan, plus OpenID and CAS through the OrbitID identity platform, with many identity providers named), SCIM directory sync and multi-factor authentication are all stated. We found no public information on a Terraform provider or monitoring-as-code workflow, checks triggered from CI/CD, client sub-accounts or white-label reports. Most importantly for my ISO 27001 programme, we found no public information on audit logs — single sign-on without an audit trail still fails my access review. 2 3 4 6 9 13 14
The Skeptic
A REST API covering status page updates, monitoring integrations and on-call schedules, signed webhooks, and SAML single sign-on with SCIM directory sync on the Business plan are documented, with team member limits per tier. We found no public information on a Terraform provider or command-line workflow, checks run from CI/CD, audit logs, or per-client sub-accounts with their own logins. 3 4 9 13 14
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
Uptime history per component and public response statistics are documented, the vendor publishes its own availability on instat.us measured from multiple locations with independent monitoring, and there is a real SLA with a stated credit formula and a 30-day claim window. We found no public information on scheduled or client-facing monthly uptime reports, retention periods for check results, response-time percentiles, or published probe IP addresses for allow-listing. 5 7 8 11 15
The SaaS Platform Engineer
The vendor publishes its own availability at instat.us measured with independent monitoring from multiple locations, and the SLA is unusually explicit: 99% on paid self-serve plans and 99.99% on Enterprise, with a stated service-credit formula, a 30-day claim window and sole-remedy terms. Status pages show per-component uptime history and response statistics, but we found no public information on response-time percentiles, retention of check results, scheduled or client-facing reports, published probe addresses, or a self-hosted edition. 4 7 8 11 15
The Customer Support Lead
Per-component uptime history and response statistics can be published on the status page, data exports through the dashboard and API while the account is active, and the SLA is public with a concrete credit formula — ten times the hourly cost of the plan for each day with more than five minutes of downtime — alongside the vendor's own status page at instat.us. We found no public information on scheduled email reports, how long check results are kept, response time percentiles, or the probe IP addresses my customers' firewalls would need allow-listing. 5 7 11 15
The E-Commerce Operations Manager
The service-level agreement is genuinely published with a concrete credit formula — ten times the hourly plan cost for each day with more than five minutes of downtime, capped at the month's payment — and the vendor measures its own availability from independent locations and publishes it at instat.us. But we found no public information on scheduled email reports, branded client-ready reports, how long check results are kept, or response-time percentiles, so I could not hand my agency a downtime-cost report built from these pages. 4 5 10 11 15
The Information Security Officer
The SLA publishes a 99% commitment for paid self-serve plans and 99.99% for Enterprise, a service-credit formula of ten times the hourly plan cost for each day with more than five minutes of downtime, a 30-day claim window, and availability measured from multiple locations with independent monitoring published on the vendor's own page. Per-monitor uptime and response statistics can be displayed publicly, per-component uptime history is supported, and data is exportable through the dashboard and API while the account is active. We found no public information on the retention period of check results, scheduled or client-facing reports, response-time percentiles, published probe IP addresses for allow-listing, or public post-mortems — so the record as documented would not yet stand on its own in one of my audits. 5 7 8 10 11 15
The Skeptic
The vendor publishes its own availability on its own status page and an SLA with a spelled-out credit formula — ten times the hourly plan cost for each day with more than five minutes of downtime, capped at that month's payment — and uptime history is shown per component. But the retention period for check results is not stated on any captured page, and we found no public information on scheduled reports, response time percentiles, or the probe IP addresses a customer would allow-list. 5 11 15
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
Instatus, Inc. is a Delaware corporation that stores data primarily in the United States, payments run through Paddle as reseller and Merchant of Record, and a data processing addendum applies automatically with Standard Contractual Clauses for transfers from the EEA. A subprocessors page is referenced but the captured pages do not show the provider list, and we found no public information on an EU hosting option, a European contracting entity, or ISO 27001 or SOC 2 certifications. 5 6
The SaaS Platform Engineer
Contracting is with Instatus, Inc., a Delaware corporation at a Beaverton, Oregon address, data is stored primarily in the United States, and a data processing addendum applies automatically, with Standard Contractual Clauses covering transfers out of the EEA, UK and Switzerland. The captured pages point to a subprocessors page without naming providers beyond Paddle for payments, and we found no public information on an EU hosting option, security certifications, or a self-hosted edition. 5 6
The Customer Support Lead
A privacy policy and a data processing agreement that applies automatically are published, but the contracting entity is a Delaware corporation that stores data primarily in the United States, and the privacy policy points to a separate subprocessors page whose contents the captured pages do not show; transfers out of the EEA rely on Standard Contractual Clauses. We found no public information on EU hosting options or a self-hosted edition. 5 6
The E-Commerce Operations Manager
The captured pages state that data is stored primarily in the United States, the contracting entity is a Delaware corporation under Delaware courts, and transfers out of the EEA rely on Standard Contractual Clauses; a data processing addendum does exist and applies automatically. The privacy policy points to a subprocessors page whose contents the captured pages do not show, no ISO 27001 or SOC 2 certification is stated, and we found no public information on EU hosting or a self-hosted edition. 5 6
The Information Security Officer
Instatus, Inc. is a Delaware corporation with Delaware governing law, and the privacy policy states data is stored primarily in the United States — including the on-call contacts and status page subscribers that are personal data under my NIS2 obligations. A data processing addendum applies automatically with the vendor as processor, EEA transfers rely on Standard Contractual Clauses, payments run through Paddle as merchant of record, and a subprocessors page is referenced though its contents were not captured. We found no public information on security certifications such as ISO 27001 or SOC 2, or on a self-hosted or open-source edition, so the chain cannot be closed on European terms from what is published. 5 6
The Skeptic
The contracting entity is Instatus, Inc., a Delaware corporation under Delaware law that stores data primarily in the United States, and a data processing addendum applies automatically as part of the terms, with Standard Contractual Clauses for transfers from the EEA. A subprocessors page is referenced but we captured no list of subprocessors with their locations, and we found no public information on a European hosting option or a self-hosted edition. 5 6
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
The tier table is unusually detailed — monitors, check interval, team and on-call members, subscribers, custom domains and alert channels per plan, "STARTER FREE", "YEARLY 25% OFF" and three months free on annual payment — and the terms add US-dollar fees, VAT excluded, invoicing for Business and Enterprise, and a 30-day price-change notice. The captured pricing page shows no amounts for Pro and Business, so at two hundred monitors the Business plan's annual cost cannot be computed from public pages, and per-message SMS prices are absent because texts run through your own provider. 4 5 10
The SaaS Platform Engineer
Tier inclusions are specific and public — fifteen to a thousand monitors, intervals from two minutes down to thirty seconds, subscriber, team-member, on-call and custom-domain counts, and alert channels per tier — alongside twenty-five percent off yearly payment, VAT excluded and stated as the buyer's responsibility, and clear renewal, refund, suspension and invoicing terms. The captured pages give no figures for the Pro and Business monthly prices themselves, no per-message cost for SMS or calls, and no overage rules, and SMS delivery runs through a provider the customer connects and pays separately. 4 5 10 15
The Customer Support Lead
The pricing page is public with per-tier limits for monitors, check interval, subscribers, on-call members, team members, alert types and custom domains, a free tier, 25% off yearly payment, VAT treatment, invoicing terms for Business and Enterprise, and per-plan uptime commitments. The captured pages do not show the monthly price figures for the Pro and Business plans themselves, and we found no public information on overage handling or the price of extra seats, so a real annual cost cannot be computed from what we read. 4 5 15
The E-Commerce Operations Manager
Tier limits are public in detail — monitors, check interval, subscribers, on-call members, team members, custom domains, and which tiers get SMS or calls — alongside a free Starter tier, 25 percent off yearly payment, USD pricing with VAT excluded, and invoicing for Business and Enterprise. But the captured pricing page gives no price figure for the Pro and Business tiers themselves, and we found no public information on per-message costs for SMS and call alerts beyond routing them through your own provider account. 4 5
The Information Security Officer
The pricing page lays out tiers with monitor counts of 15, 50 and 1,000, check intervals from 2 minutes to 30 seconds, subscriber, on-call member and team member limits, custom domains and alert channels per tier, a free starter tier, 25% off yearly with three months free on annual prepayment, and the terms state fees in US dollars excluding taxes with Paddle as merchant of record. However, the captured pages show no amounts for the Pro and Business tiers, and SMS and call alerts run through the customer's own Twilio, Vonage or similar account, so their cost is not stated by the vendor. An annual cost for a given team size is therefore not computable from what was captured. 4 5 10 15
The Skeptic
Tier inclusions are public — monitor counts, check intervals, subscriber, on-call and team member limits per plan — alongside the free Starter plan, a 25% yearly discount, three months free on annual payment, tax treatment and refund terms. The captured pricing page gives the Pro and Business headings without numeric amounts, and SMS and call costs are not stated because messaging runs through the customer's own gateway account. 4 5 10
European sovereignty — proven facts
1 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 | Incorporated in US | 0/2 pts | 5 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 Instatus
Is Instatus European?
No. whats-best.ai classifies Instatus as Rest of world. Its vendor, Instatus, Inc., is incorporated in United States, per the vendor’s page captured 1 Nov 2026.
Where does Instatus store data?
Not stated on the vendor’s pages as of 1 Nov 2026.
Does Instatus have a free plan?
Yes. Instatus has a free plan, per the vendor’s page captured 1 Nov 2026.
What are the best alternatives to Instatus?
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: Instatus 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, 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.
- 26 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. Know more? Tell us
- 12 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. Know more? Tell us
- 7 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
- 4 support 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
- 3 legal 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
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage instatus.com Checked 1 Nov 2026 Details →
- 2 Integrations page instatus.com Checked 1 Nov 2026 Details →
- 3 API documentation instatus.com Checked 1 Nov 2026 Details →
- 4 Pricing page instatus.com Checked 1 Nov 2026 Details →
- 5 Terms of service instatus.com Checked 1 Nov 2026 Details →
- 6 Privacy policy instatus.com Checked 1 Nov 2026 Details →
- 7 Checks, locations & failure confirmation — found from sitemap instatus.com Checked 1 Nov 2026 Details →
- 8 Checks, locations & failure confirmation — found from sitemap instatus.com Checked 1 Nov 2026 Details →
- 9 Alerting, escalation & on-call — found from sitemap instatus.com Checked 1 Nov 2026 Details →
- 10 Alerting, escalation & on-call — found from sitemap instatus.com Checked 1 Nov 2026 Details →
- 11 Status pages & incident communication — found from sitemap instatus.com Checked 1 Nov 2026 Details →
- 12 Status pages & incident communication — found from sitemap instatus.com Checked 1 Nov 2026 Details →
- 13 API, monitoring as code & team administration — found from sitemap instatus.com Checked 1 Nov 2026 Details →
- 14 API, monitoring as code & team administration — found from sitemap instatus.com Checked 1 Nov 2026 Details →
- 15 Uptime reports, data & the vendor's own reliability — found from sitemap instatus.com Checked 1 Nov 2026 Details →