# Instatus — Uptime Monitoring & Status Pages

Instatus by Instatus, Inc. holds a panel rating of 2.5/5 from 6 AI judges (category median 3/5), as of 2026-11-02. Provenance: Rest of world; sovereignty: 1 of 6 dimensions proven.

- Vendor: Instatus, Inc. (https://instatus.com)
- Category: [Uptime Monitoring & Status Pages](https://whats-best.ai/software/uptime-monitoring.md)
- Provenance (editorial classification): Rest of world
- Canonical page: https://whats-best.ai/software/uptime-monitoring/instatus
- Alternatives: https://whats-best.ai/software/uptime-monitoring/instatus/alternatives ([markdown](https://whats-best.ai/software/uptime-monitoring/instatus/alternatives.md))
- Data as of: 2026-11-06 · evaluated 2026-11-02 · oldest source captured 2026-11-01

**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: Instatus, Inc.
- Headquarters: Incorporated in United States [S5]
- Data hosting: Not stated on the vendor’s pages as of 1 Nov 2026
- Free plan: Yes, per the vendor’s own page [S5]

## 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.

## 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 | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 |
| Alerting, escalation & on-call | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 |
| Status pages & incident communication | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 4/5 | 3.5/5 |
| API, monitoring as code & team administration | 3/5 | 2.5/5 | 3/5 | 3/5 | 3/5 | 3/5 |
| Uptime reports, data & the vendor's own reliability | 2/5 | 2.5/5 | 2.5/5 | 2.5/5 | 2.5/5 | 2.5/5 |
| European sovereignty | 1.5/5 | 1.5/5 | 1.5/5 | 1.5/5 | 1.5/5 | 1.5/5 |
| Pricing transparency | 2/5 | 2.5/5 | 2/5 | 2/5 | 2/5 | 2/5 |
| **Weighted verdict** | **2.5/5** | **2.5/5** | **2.5/5** | **2.5/5** | **2.5/5** | **2.5/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

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: 1 of 6 dimensions proven.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Incorporated in US | 0/2 | [S5] |
| Hosting location | Not determined | — | — |
| Hosting options | Not determined | — | — |
| Open source | Not determined | — | — |
| Data processing agreement | Not determined | — | — |
| Transfer impact assessment | Not determined | — | — |

## Key facts

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

**Compliance**
- Children: 16 [S6]
- Cookies consent eea: EEA · UK · Switzerland · yes [S6]
- DPA auto apply: processor · yes [S5]
- DPA reference: yes [S6]
- Google API policy: yes [S6]
- Gpc: yes [S6]
- International transfers: Standard Contractual Clauses + UK/Swiss equivalents [S6]
- Law enforcement: yes · yes [S6]
- No sale: no [S6]
- Rights response time: 30 [S6]
- Roles: customer data in Instatus · own business data [S6]
- Security measures: encryption in transit · encryption at rest · multi-factor authentication · access controls · monitoring [S6]
- Uptime SLA: 99.99 [S4]

**Data**
- Account collection: salted bcrypt hash [S6]
- Account deletion: 60 · 30 [S6]
- Billing retention: 7 [S6]
- Content deletion: 30 [S6]
- Cookie consent retention: 6 [S6]
- Deletion after cancellation: 60 · 30 [S5]
- Export: dashboard · api · yes [S5]
- Liability cap: 12 months of paid fees · 100 [S5]
- Sms subscribers CSV export: CSV · yes [S10]
- Subscriber unsubscribe: yes [S6]

**Hosting**
- Data location: United States [S6]
- Payment processor: reseller and Merchant of Record · Paddle · no [S6]

**Integrations**
- API: yes [S2]
- Bird credentials: API Key · Sender phone Number [S10]
- Create endpoint: /v3/integrations · POST [S14]
- Create parameters: pageId · integrationType · components[] [S14]
- Datadog: auto-create incidents on detected outage · yes [S2]
- Delete endpoint: /v3/integrations/:integration_id · DELETE [S14]
- Discord: yes [S2]
- Dynatrace: yes [S2]
- Enum support: Accepts any monitoring tool in MonitoringTool enum [S14]
- Esendex credentials: Username · API password · Account Reference [S10]
- Google chat: yes [S2]
- Google cloud monitoring: yes [S2]
- Intercom: show status in Intercom widget · yes [S2]
- Jira: yes [S2]
- Metrics display: yes · Pingdom · Datadog · New Relic · Prometheus [S2]
- Microsoft teams: yes [S2]
- Monitoring API: REST API to create third-party monitoring integrations [S14]
- Monitoring integration count: yes [S2]
- Monitoring providers: Pingdom · Prometheus · Freshping · Grafana · Better Uptime · HetrixTools · Runscope · Site24x7 · StatusCake · Uptime Robot · Updown.io [S2]
- New relic: yes [S2]
- On call create endpoint: create on-call schedule · POST /on-call-schedules [S9]
- On call delete endpoint: delete on-call schedule · DELETE /on-call-schedules/:id [S9]
- On call get members endpoint: list schedule members · GET /on-call-schedules/:id/members [S9]
- On call schedule API: yes · GET /on-call-schedules/:id/members · POST /on-call-schedules · PUT /on-call-schedules/:id · DELETE /on-call-schedules/:id [S9]
- On call update endpoint: update on-call schedule · PUT /on-call-schedules/:id [S9]
- Pagerduty: yes [S2]
- Sharing: yes · Slack · PagerDuty [S6]
- Slack: update status page from Slack · yes [S2]
- Sms import CSV columns: Name · Email · Phone [S10]
- Sms providers: Twilio · Esendex · Vonage · Bird · AWS SNS [S10]
- Sms subscribers CSV import: CSV · yes · Pro [S10]
- Sns credentials: region · AWS Access key Id · Secret access key [S10]
- Third party: Slack · Microsoft Teams · Discord · PagerDuty · Jira · custom SMTP · SMS · webhooks [S5]
- Twilio credentials: Account SID · Auth token · Sender phone number [S10]
- Update endpoint: /v3/integrations/:integration_id · PUT [S14]
- Update templates: Update supports create/createTemplate and resolveTemplate customization [S14]
- Vonage credentials: API Key · API secret · Sender phone number [S10]
- Webhook: yes [S2]
- X twitter: automatically tweet status updates · yes [S2]
- Zapier: yes [S2]
- Zendesk: yes [S2]

**Legal**
- Address: 9450 SW Gemini Dr PMB 30900, Beaverton, Oregon 97008-7105, USA [S5]
- Copyright holder: Instatus, Inc [S15]
- Custom contracts: yes [S4]
- Custom policies: yes [S4]
- Entity: Instatus, Inc. · Delaware, USA · privacy@instatus.com [S6]
- Entity: Instatus, Inc. · corporation · Delaware [S5]
- Entity: Instatus, Inc [S13]
- Governing law: Delaware · Delaware state and federal courts [S5]
- SLA adapted from: Adapted from Basecamp [S15]
- SLA change commitment: no [S15]
- SLA last updated: 2026-10-15 [S15]
- SLA part of tos: yes [S15]

**Pricing**
- Alerts: Email & SMS · Email · SMS & Calls [S4]
- Billing renewal: monthly · yearly · yes [S5]
- Business price: month [S4]
- Check interval: 30 · 2 min · 30 [S4]
- Credit claim window days: 30 [S15]
- Credits cash refundable: no [S15]
- Credits sole remedy: yes [S15]
- Currency: USD [S5]
- Free SLA coverage: no [S15]
- Free tier: no · yes · yes [S5]
- Invoice option: yes · Business · Enterprise · yes · yes · 30 [S5]
- Merchant of record: Paddle.com Market Limited · reseller and Merchant of Record [S5]
- Monitors: 50 · 15 · 1000 [S4]
- Nonprofit discount: free Pro account · free Pro account · three months free [S4]
- Oncall members: 20 · 2 · 50 [S4]
- Price change notice: 30 [S5]
- Pro price: month [S4]
- Refund yearly: yes [S5]
- Service credit formula: 10x hourly cost per day · amount paid that month · 5 [S15]
- Starter price: 0 [S4]
- Subscribers: 5000 · 200 · 25000 [S4]
- Taxes: no [S5]
- Team members: 50 · 5 [S4]
- Uptime commitment enterprise: 99.99 [S15]
- Uptime commitment paid plans: Pro · Select · Private Pro · Business · 99 [S15]
- Yearly discount: yearly · 25 [S4]

**Product**
- Advanced options: United States · Canada · Europe · Asia [S8]
- AI features: translate · summarize · draft content · detect abuse · no [S6]
- AI features: summarize incidents · translate content · draft updates · detect abuse [S5]
- AI no training on customer data: no · yes [S5]
- Beta SLA exclusion: yes [S5]
- Chat integrations subscribers: yes · slack · microsoft_teams · discord · google_chat [S12]
- Check frequency configurable: yes [S8]
- Component archiving: Archived components hidden unless affected or not operational [S11]
- Component fields: Component fields: name, group, show historical uptime [S11]
- Component groups: Component groups created from the component form [S11]
- Component ordering: Ordering via drag re-order handle [S11]
- Components definition: Components are parts of the service shown on the status page with own status and optional uptime history [S11]
- Custom domain: 1+ · 1+ · 3+ · not included [S4]
- Customer data ownership: yes [S5]
- Dns check locations: United States · Canada · Europe · Asia [S7]
- Dns failure actions: create incident · notify subscribers · publish to status page [S7]
- Dns friendly name: yes [S7]
- Dns interval configurable: yes [S7]
- Dns monitor check types: A · MX · record missing · wrong value · fails to resolve [S7]
- Dns monitoring logs record values: yes [S7]
- Dns recovery actions: yes · yes [S7]
- Dns status page integration: yes [S7]
- Downtime exclusions: 48 [S15]
- Failure actions: initiate incident · notify subscribers · publish to status page [S8]
- Group deletion: Group deletion implicit: remove all components; no explicit delete [S11]
- Incident escalations: yes [S4]
- Material feature removal: 30 · yes [S5]
- Minimum age: 18 [S5]
- Multiple SSO connections: yes [S4]
- On call delete response: 204 [S9]
- On call restriction types: NONE, TIMEOFDAY, TIMEINTERVALS [S9]
- On call rotation types: DAILY, WEEKLY, CUSTOM [S9]
- On call shift fields: shifts support rotationType, custom rotation value/unit, startDate, endDate, restrictionType, timeIntervals [S9]
- Orbitid: OrbitID is Instatus's identity platform [S13]
- Public pages default: public · yes [S5]
- Rate limits: yes [S5]
- Recovery actions: resolve incidents · auto-update status page [S8]
- Rss atom API follow: rss · atom · public_api · yes [S12]
- SAML SSO: yes [S4]
- SCIM directory sync: yes [S4]
- Scope: status pages · monitoring · on-call · incident response · APIs · mobile apps · integrations [S5]
- Service discontinuation: 90 · yes [S5]
- SLA reference: yes [S5]
- Sms notifications: yes [S10]
- Sms provider connection: sms_provider · yes [S12]
- Sms subscribe: yes [S10]
- Sms subscriber scope: yes [S10]
- Sms test: yes [S10]
- Sms unsubscribe: yes [S10]
- SSO applies to: Dashboard login, private status page login [S13]
- SSO idp providers: Okta, Google, Microsoft, OneLogin, Auth0 and more [S13]
- SSO protocol: SAML · OpenID · CAS [S13]
- SSO requirement: Business · OrbitID [S13]
- SSO setup steps: Upgrade to Business plan, open Single Sign-On, click Setup SSO, enter email domains, finish configuration in OrbitID [S13]
- SSO supported idps: Okta, Google SAML, Microsoft Azure, Microsoft ADFS, SAML, Duo, ADP, Jump Cloud, Keycloak, LastPass, miniOrange, NetIQ, OneLogin, Oracle Cloud, PingOne, PingFederate, Salesforce, VMware, OpenID, CAS, ClassLink, Cloudflare, CyberArk, SimpleS… [S13]
- Status banner: All systems operational [S9]
- Subscriber channels: email · sms · webhook · slack · teams · discord · x · rss · api [S12]
- Subscriber export: yes · add · search · export · unsubscribe [S12]
- Subscriber import: csv_email_import · yes [S12]
- Suspension late payment: 7 · yes [S5]
- Tcp checks: TCP monitors test host:port reachability from multiple global locations, detect offline/slow/dropped connections, measure connection time and latency, send alerts, display uptime on status page [S8]
- Tcp udp monitoring: yes [S8]

**Subprocessors**
- Page reference: subprocessors page [S6]

**Support**
- Channels: support@instatus.com · email · in-app chat [S5]
- Dns live chat: live chat · email [S7]
- Live chat: live chat · email [S8]
- Live chat: yes [S11]
- Live chat: yes [S12]
- Live chat: live chat · email [S13]
- On call page channels: live chat · email [S9]
- Priority support: yes [S4]
- Priority support: Business · Enterprise · yes [S5]
- Sms docs channels: live chat · email [S10]

8 more facts on the canonical page: https://whats-best.ai/software/uptime-monitoring/instatus

## Questions

### 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](https://whats-best.ai/evidence/15593).

### 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](https://whats-best.ai/evidence/15593).

### What are the best alternatives to Instatus?

As of 2 Nov 2026, the panel rates [Hyperping (3.5/5)](https://whats-best.ai/software/uptime-monitoring/hyperping), [Checkly (3.5/5)](https://whats-best.ai/software/uptime-monitoring/checkly) and [openstatus (3.5/5)](https://whats-best.ai/software/uptime-monitoring/openstatus) 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](https://whats-best.ai/software/uptime-monitoring/hyperping) (EU-Made). 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: [Instatus alternatives](https://whats-best.ai/software/uptime-monitoring/instatus/alternatives).

## Head-to-head

- [Instatus vs Atlassian Statuspage](https://whats-best.ai/compare/atlassian-statuspage-vs-instatus.md)

## What this page leaves out

- 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.
- 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.
- 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.
- 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.
- 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.
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown.

## Sources

- [S1] Vendor homepage: https://instatus.com/ (checked 2026-11-01)
- [S2] Integrations page: https://instatus.com/integrations (checked 2026-11-01)
- [S3] API documentation: https://instatus.com/help/api (checked 2026-11-01)
- [S4] Pricing page: https://instatus.com/pricing (checked 2026-11-01)
- [S5] Terms of service: https://instatus.com/policies/terms (checked 2026-11-01)
- [S6] Privacy policy: https://instatus.com/policies/privacy (checked 2026-11-01)
- [S7] Checks, locations & failure confirmation — found from sitemap: https://instatus.com/help/monitoring/dns (checked 2026-11-01)
- [S8] Checks, locations & failure confirmation — found from sitemap: https://instatus.com/help/monitoring/tcp-udp (checked 2026-11-01)
- [S9] Alerting, escalation & on-call — found from sitemap: https://instatus.com/help/api/on-call-schedules (checked 2026-11-01)
- [S10] Alerting, escalation & on-call — found from sitemap: https://instatus.com/help/status-page/notifications/sms (checked 2026-11-01)
- [S11] Status pages & incident communication — found from sitemap: https://instatus.com/help/status-page/components (checked 2026-11-01)
- [S12] Status pages & incident communication — found from sitemap: https://instatus.com/help/status-page/subscribers (checked 2026-11-01)
- [S13] API, monitoring as code & team administration — found from sitemap: https://instatus.com/help/team/sso (checked 2026-11-01)
- [S14] API, monitoring as code & team administration — found from sitemap: https://instatus.com/help/api/monitoring-integrations (checked 2026-11-01)
- [S15] Uptime reports, data & the vendor's own reliability — found from sitemap: https://instatus.com/policies/sla (checked 2026-11-01)

---

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

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