# Better Stack Uptime — Uptime Monitoring & Status Pages

Better Stack Uptime by Better Stack, 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: Better Stack, Inc. (https://betterstack.com/uptime)
- 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/better-stack
- Alternatives: https://whats-best.ai/software/uptime-monitoring/better-stack/alternatives ([markdown](https://whats-best.ai/software/uptime-monitoring/better-stack/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: Better Stack, Inc.
- Headquarters: Incorporated in United States [S9]
- Data hosting: Not stated on the vendor’s pages as of 1 Nov 2026
- Free plan: Yes, per the vendor’s own page [S1]

## The panel's verdict

Better Stack Uptime is strongest on alerting and on-call, where scores reach 9, and on checks and locations, where they reach 8: ten monitor types at a fastest 30-second interval, an incident created only after a failure from at least 3 of at least 4 default locations, and escalation policies, follow-the-sun schedules and voice, SMS, e-mail, Slack, Teams and push alerts under all-you-can-alert pricing. Its weakest area is sovereignty, topping out at 4: the contracting entity is Better Stack, Inc., a Delaware corporation under New York law, the privacy policy states personal data is processed primarily in the European Union, and the data processing agreement permits transfers to the United States under the Data Privacy Framework and standard contractual clauses. The sharpest split: the skeptic and the e-commerce operations manager scored 0 across the board while remaining scores cluster between 4 and 9, though their write-ups cover the same features. Elsewhere the gaps are single points — status pages at 7-8, pricing transparency at 5-6 — over how far an itemised free tier offsets pages showing no paid uptime tier price.

**Speaks for it:**
- Alerting and on-call draws the highest scores, covering escalation policies with delays, repeats and fallback, follow-the-sun schedules, incident merging, and voice, SMS, e-mail, Slack, Teams and push alerts under all-you-can-alert pricing.
- Ten monitor types are documented, from uptime, keyword and ping to DNS, domain expiry, SSL certificate and TCP/UDP port, plus Playwright browser checks at a fastest 30-second interval.
- False-positive protection is explicit, with every monitor checked from at least 4 locations by default and an incident created only after a failure from at least 3.
- Status pages support a custom subdomain via a single CNAME record, per-component e-mail subscriptions, and private pages behind password, single sign-on or an IP allowlist.
- The free tier is fully specified at $0 per month with 10 monitors & heartbeats and 1 status page, and add-ons carry published unit prices such as single sign-on with Azure or Okta at $5 per user per month (Google single sign-on included) and 100 Playwright minutes $1.

**Held against it:**
- Sovereignty is the lowest-scored area: the contracting entity is Better Stack, Inc., a Delaware corporation under New York law and courts, and the data processing agreement permits transfers to the United States under the Data Privacy Framework and standard contractual clauses.
- We found no public information on an EU contracting entity or EU representative, on named hosting infrastructure, or on subprocessor names and locations.
- The captured pricing shows no paid uptime tier price or monitor-scaling rule and enterprise is a custom quote, so a cost beyond the free tier is not computable from the pages.
- The captured pages give different figures for refunds, with a 60-day money-back guarantee on the pricing page beside terms stating no refund is owed.
- We found no public information on retention of check results (logs at 30 days and error tracking at 90 days are the stated periods), on an SLA with credits, or on the vendor's own incident history.

**Best for:**
- You want on-call scheduling, escalation policies and incident management built into the monitoring tool rather than run as a separate product.
- You maintain many sites and need component-based status pages on custom subdomains, including private pages for internal teams or enterprise customers.
- You manage infrastructure as code and want a documented API, Terraform management, SAML single sign-on and Okta SCIM provisioning with group push.
- You can start on the free tier at $0 per month with 10 monitors & heartbeats and 1 status page, adding options at published unit prices.

**Avoid if:**
- You must contract with a European entity or document a European processing chain — the contracting party is a Delaware corporation under New York law and the data processing agreement permits transfers to the United States.
- You need a computable annual cost before committing — the pages show no paid uptime tier price and leave enterprise at a custom quote.
- You rely on a refund window when prepaying — the captured pages give different figures, a 60-day money-back guarantee on the pricing page beside terms stating no refund is owed.

## 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 | 4/5 | 4/5 | 4/5 | 0/5 | 4/5 | 0/5 |
| Alerting, escalation & on-call | 4.5/5 | 4.5/5 | 4.5/5 | 0/5 | 4.5/5 | 0/5 |
| Status pages & incident communication | 3.5/5 | 4/5 | 4/5 | 0/5 | 3.5/5 | 0/5 |
| API, monitoring as code & team administration | 3.5/5 | 3.5/5 | 3.5/5 | 0/5 | 3.5/5 | 0/5 |
| Uptime reports, data & the vendor's own reliability | 3/5 | 3/5 | 3/5 | 0/5 | 3/5 | 0/5 |
| European sovereignty | 2/5 | 2/5 | 2/5 | 0/5 | 2/5 | 0/5 |
| Pricing transparency | 2.5/5 | 3/5 | 3/5 | 0/5 | 2.5/5 | 0/5 |
| **Weighted verdict** | **3.5/5** | **3.5/5** | **3.5/5** | **0/5** | **3.5/5** | **0/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 | [S9] |
| 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**
- Audit cooperation: yes · yes [S11]
- CCPA notice: no · yes [S10]
- Custom telemetry residency: yes [S8]
- DPA reference: betterstack.com/dpa · yes [S9]
- Dpf certification: EU-U.S. DPF · Swiss-US DPF · UK-US DPF [S11]
- Dpia assistance: yes [S11]
- GDPR page: yes [S2]
- Right of access: yes [S10]
- Right to erasure: yes [S10]
- Right to restriction: yes [S10]
- Rights free of charge: letter or email · yes [S10]
- Scc fallback: yes [S11]
- Security measures: yes [S11]
- SOC 2 type2: yes [S12]
- System status page: yes [S22]

**Data**
- Breach notification: yes [S10]
- Breach notification: notify without undue delay [S11]
- Cookies third party: yes [S10]
- Min age: 18 [S10]
- Pii types: first and second names · email address · professional experience [S10]
- Recruitment processing: yes [S10]
- Return deletion: yes [S11]
- Security measures: encryption · firewalls · secure facilities · access rights systems [S10]
- Subject request forwarding: yes [S11]
- Technical types: referring URL · time and date of visits · IP address · browser name and type · device type · time spent on Service [S10]

**Hosting**
- Primary region: European Union [S10]
- Processing locations: United States of America · other locations where operations are maintained [S11]
- Transfer safeguards: adequacy decision · standard contractual clauses · binding internal company rules [S10]

**Integrations**
- API: yes [S18]
- API auth: Bearer token [S7]
- API docs sections: API token · Monitors · Heartbeats · On-call & incidents · Status pages · Metadata · Integrations · Team members · Organization roles · Usage · Reporting [S6]
- API documented: Incidents API · Monitors · Heartbeats · On-call & incidents · Status pages · Metadata · Integrations · Team members · Organization roles · Usage · Reporting [S15]
- API jsonapi: JSON:API [S7]
- API sections: Incidents API covers monitors, heartbeats, on-call & incidents, status pages, metadata, integrations, team members, organization roles, usage, reporting [S5]
- Calendars: yes · yes [S4]
- Global API token: all teams · yes [S7]
- Google sheets: Google Sheets IMPORTDATA integration with live CSV URL · yes [S21]
- Heartbeat URL: https://incidents.betterstack.com/api/v1/heartbeat/<HEARTBEAT_TOKEN> [S6]
- Interactive API docs: Interactive API docs available [S5]
- Mcp server: yes [S4]
- Monitoring tools: Datadog · New Relic · Grafana · Prometheus · Zabbix · Azure · AWS · Google Cloud [S3]
- Observability import: yes · yes · yes · yes · yes [S8]
- SCIM bearer token: bearer_token [S20]
- SCIM cross org user retention: yes [S20]
- SCIM group deprovision warning: yes [S20]
- SCIM group push teams: yes [S20]
- SCIM last admin removal blocked: 400 [S20]
- SCIM prerequisite SSO: yes [S20]
- SCIM provisioning: Okta · yes [S20]
- SCIM supported features: Create users · Update user attributes · Deactivate users · Sync password · Group push · Import users and groups [S20]
- SCIM user deactivation behavior: yes [S20]
- SCIM username format: Email [S20]
- Slack: Slack integration, tag on-call in Slack [S5]
- Slack: Create/acknowledge/resolve incidents from Slack, two-way event sync [S4]
- Team scoped API token: per team · yes [S7]
- Terraform: yes [S7]

**Legal**
- Copyright: Better Stack, Inc. [S14]
- Data processor role: processor or sub-processor [S10]
- DPA applicable laws: GDPR · UK GDPR · Swiss DPA · CCPA [S11]
- DPA term: while processing occurs or until contract termination [S11]
- Entity: Better Stack, Inc. [S2]
- Entity: Better Stack, Inc. [S7]
- Entity: Better Stack, Inc. [S6]
- Entity: Better Stack, Inc. [S5]
- Entity: Better Stack, Inc. [S3]
- Entity: Better Stack, Inc. [S4]
- Entity: Better Stack, Inc. · Delaware corporation [S9]
- Entity name: Better Stack, Inc. · Delaware [S10]
- Governing law: New York · New York courts [S9]
- Law enforcement notice: yes [S11]
- Liability cap: fees paid in prior 12 months [S9]
- Logo license: yes · yes [S9]
- Logo revoke email: hello@betterstack.com [S9]
- Marketing opt out: unsubscribe link · email withdrawal [S10]
- Minimum age: 13 [S9]
- No sale or sharing: yes · yes [S11]
- Payment terms: 15 · 1.5 [S9]
- Refund policy: yes [S9]
- Termination by vendor: yes [S9]
- Third party processors acknowledged: yes [S11]
- Warranty disclaimer: as-is, all warranties disclaimed [S9]

**Pricing**
- Enterprise quote: yes [S8]
- Error tracking included: 5.0E-5 · 100000 [S8]
- Free tier: yes · 10 · 10 · yes · 3 [S2]
- Free tier: Completely free status page on your subdomain [S3]
- Free tier: yes [S4]
- Free tier: 3 · 10 · 30 · 0 · 1 · 5000 · 100000 [S8]
- Logs aws direct connect: 0.04 [S8]
- Logs ingestion: 0.1 [S8]
- Logs query boost: 0.001 [S8]
- Logs retention: 0.05 [S8]
- Metrics included: 30 · 0.5 [S8]
- Money back guarantee: 60 [S8]
- Session replay: 0.0015 · 5000 [S8]
- Slack responder addon: 9 [S8]
- SSO azure okta: 5 [S8]
- SSO google: yes [S8]
- Taxes exclusive: yes [S9]
- Telemetry free access: 0 [S8]

**Product**
- Access protection: SSO · password · IP protection · yes [S3]
- Account data controller: yes [S11]
- AI human approval: yes [S4]
- AI postmortems: yes [S4]
- AI sre: AI SRE observability stack with agentic incident resolution [S1]
- AI sre: yes [S5]
- AI sre: AI SRE based on Claude Code with knowledge of your infrastructure [S4]
- AI sre: yes [S18]
- AI sre: Anthropic · OpenAI · DeepSeek · GLM · Gemini · Kimi · consumption-based [S8]
- AI sre root cause: Automated root cause analysis based on eBPF-based service map & log analysis [S4]
- Alert channels: voice call · SMS · email · Slack · Teams · push · yes [S2]
- Alerting targets: specific team members · current on-call team · Slack or Microsoft Teams integrations · Zapier and Webhook integrations · AI SRE [S15]
- API auth bearer token: Bearer token · yes [S22]
- API monitor response times endpoint: GET · last 24h · https://incidents.betterstack.com/api/v2/monitors/{monitor_id}/response-times [S22]
- API tokens location: Tokens obtained at Settings → API tokens [S22]
- Assignment scope: monitors · heartbeats · integrations [S15]
- Bulk assignment: yes [S15]
- Business hours filters: business hours filters · yes [S21]
- Check interval: 30 · yes [S3]
- Cname setup: single CNAME record [S3]
- Compound SLA report: Compound SLA report across selected monitors · yes [S21]
- Cron monitoring: cron and serverless worker monitoring with alerts on failure [S2]
- Cron monitoring: yes [S3]
- Css js customization: yes [S18]
- CSV filters applied: yes [S21]
- Custom css: custom CSS · yes [S3]
- Custom domain: custom subdomain via CNAME · yes [S3]
- Custom subdomain: *.betteruptime.com · yes [S17]
- Custom subdomain: yes [S18]
- Customer role controller: yes · yes [S11]
- Data ingestion included: 1 · 1 · 1 [S1]
- Default behavior without policy: current primary on-call by e-mail, then rest of team, then all integrations · yes [S15]
- Default locations per monitor: 4 [S14]
- Delay configuration: yes [S15]
- Displayed components: "monitors · "heartbeats · "third party services [S17]
- Embed announcements: yes [S17]
- Embed charts: response time charts · custom metrics · yes [S3]
- Embeddable status badge: yes [S18]
- Error tracking: yes [S4]
- Error tracking retention: 90 [S8]
- Error tracking sentry compatible: yes [S8]
- Escalation policy definition: Escalation policy defines who will be alerted and in what order, continuing until the incident is acknowledged [S15]
- Escalation policy reference: Reusable escalation policies can group multiple on-call schedules and be referenced inside other escalation policies [S16]
- Escalation re alert delay: Escalation steps can re-alert after a waiting period and escalate to the whole team if unacknowledged [S16]
- Explain with AI: yes [S4]
- External calendars: External calendar connection supported for on-call scheduling [S5]
- External calendars: yes [S18]
- Faq: yes [S5]
- Fastest check interval: second-by-second · yes · 30 [S2]
- Filter presets: saved filter presets · yes [S21]
- Follow the sun: When a step alerts multiple regional schedules, Better Stack notifies whoever is on-call in their local region [S16]
- Free tier: yes [S1]
- Global 30s checks: 30-second checks from multiple global locations [S2]
- Heartbeat definition: Heartbeat monitors track periodic tasks by expecting regular requests to a unique URL [S6]
- Heartbeat failure payload: yes · yes [S6]
- Heartbeat failure reporting: yes · /fail [S6]
- Heartbeat incident behavior: yes · yes [S6]
- Heartbeat pending state: yes [S6]
- Heartbeat setup fields: expect a heartbeat every (frequency) · grace period · on-call escalation settings [S6]
- Incident escalations: flexible escalation rules based on time, team availability, and incident origin [S2]
- Incident failure threshold: 3 [S14]
- Incident merging: smart incident merging with single-tap acknowledgment [S2]
- Incident merging: yes [S4]
- Incident templates: yes [S17]
- Incident types: critical incidents · scheduled maintenance · service announcements · automated or manual [S3]
- Incidents modules: Incident management docs cover AI SRE investigations, post mortems, Metadata & Catalog, screening alerts, reporting [S5]
- Incidents reports: Incidents overview · Incidents MTTA · Incidents MTTR [S21]
- Instructions todo list: yes [S15]
- Ip allowlist: one IP address or CIDR range per line · yes [S18]
- Keyword lookup case insensitive: yes [S13]
- Keyword monitor alert condition: Alert us when selection can be set to URL doesn't contain keyword [S13]
- Keyword monitor setup: Created via Monitors → Create monitor, entering URL or IP address and keyword [S13]

**Subprocessors**
- General authorization: yes [S11]
- List location: DPA [S10]

**Support**
- API endpoints: Monitors, Heartbeats, On-call & incidents, Status pages, Metadata, Integrations, Team members, Organization roles, Usage, Reporting [S7]
- Faq: yes [S7]

87 more facts on the canonical page: https://whats-best.ai/software/uptime-monitoring/better-stack

## Questions

### Is Better Stack Uptime European?

No. whats-best.ai classifies Better Stack Uptime as Rest of world. Its vendor, Better Stack, Inc., is incorporated in United States, per [the vendor’s page captured 1 Nov 2026](https://whats-best.ai/evidence/15388).

### Where does Better Stack Uptime store data?

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

### Does Better Stack Uptime have a free plan?

Yes. Better Stack Uptime has a free plan, per [the vendor’s page captured 1 Nov 2026](https://whats-best.ai/evidence/15380).

### What are the best alternatives to Better Stack Uptime?

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: [Better Stack Uptime alternatives](https://whats-best.ai/software/uptime-monitoring/better-stack/alternatives).

## Head-to-head

- [Better Stack Uptime vs UptimeRobot](https://whats-best.ai/compare/better-stack-vs-uptimerobot.md)

## What this page leaves out

- 16 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.
- 11 compliance 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.
- 10 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.
- 4 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 hosting 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 data 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 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.
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown.

## Sources

- [S1] Vendor homepage: https://betterstack.com/ (checked 2026-11-01)
- [S2] Features page (uptime monitoring): https://betterstack.com/uptime (checked 2026-11-01)
- [S3] Features page (status pages): https://betterstack.com/status-page (checked 2026-11-01)
- [S4] Features page (incident management and on-call): https://betterstack.com/incident-management (checked 2026-11-01)
- [S5] Documentation: https://betterstack.com/docs/uptime/start/ (checked 2026-11-01)
- [S6] Documentation (cron and heartbeat monitoring): https://betterstack.com/docs/uptime/cron-and-heartbeat-monitor/ (checked 2026-11-01)
- [S7] API documentation: https://betterstack.com/docs/uptime/api/getting-started-with-uptime-api/ (checked 2026-11-01)
- [S8] Pricing page: https://betterstack.com/pricing (checked 2026-11-01)
- [S9] Terms of service: https://betterstack.com/terms (checked 2026-11-01)
- [S10] Privacy policy: https://betterstack.com/privacy (checked 2026-11-01)
- [S11] Data processing agreement (dpa): https://betterstack.com/dpa (checked 2026-11-01)
- [S12] Security / trust page: https://betterstack.com/security (checked 2026-11-01)
- [S13] Checks, locations & failure confirmation — found from sitemap: https://betterstack.com/docs/uptime/keyword-monitor/ (checked 2026-11-01)
- [S14] Checks, locations & failure confirmation — found from sitemap: https://betterstack.com/docs/uptime/locations-and-regions/ (checked 2026-11-01)
- [S15] Alerting, escalation & on-call — found from sitemap: https://betterstack.com/docs/uptime/escalation-policies/ (checked 2026-11-01)
- [S16] Alerting, escalation & on-call — found from sitemap: https://betterstack.com/docs/uptime/complex-schedules/ (checked 2026-11-01)
- [S17] Status pages & incident communication — found from sitemap: https://betterstack.com/docs/uptime/getting-started-with-status-pages/ (checked 2026-11-01)
- [S18] Status pages & incident communication — found from sitemap: https://betterstack.com/docs/uptime/password-protected-status-page/ (checked 2026-11-01)
- [S19] API, monitoring as code & team administration — found from sitemap: https://betterstack.com/docs/uptime/okta-sso/saml-setup-instructions/ (checked 2026-11-01)
- [S20] API, monitoring as code & team administration — found from sitemap: https://betterstack.com/docs/uptime/okta-sso/scim-setup-instructions/ (checked 2026-11-01)
- [S21] Uptime reports, data & the vendor's own reliability — found from sitemap: https://betterstack.com/docs/getting-started/team-and-account-management/reporting/custom-reports/ (checked 2026-11-01)
- [S22] Uptime reports, data & the vendor's own reliability — found from sitemap: https://betterstack.com/docs/uptime/api/get-monitors-response-times/ (checked 2026-11-01)
- [S23] Code repository (open-source licence) — found from the homepage: https://github.com/BetterStackHQ (checked 2026-11-01)

---

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

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