Status pages

The ledger

Newest first. A fact, a company’s own claim about itself and a user’s opinion are all here, and the tag on each row is which one you are reading.

• Small SaaS teams communicating incidentsDISCOURSECOMPANY CLAIMSep 30, 2026

  Recent 2026 postmortem-writing guidance converges on a consistent structure — summary, timeline, root cause (often via 5 Whys), what went well/poorly, and action items with owner and due date — with several guides recommending publishing the postmortem or its summary on the status page itself.

  Establishes the baseline 'best practice' template small teams are being pointed toward; useful for tracking future drift in postmortem norms.

  dev.to/jensonhirst/how-to-write-an-incident-postmortem-in-2026-with-template-2p27
• Small SaaS teams communicating incidentsDISCOURSECOMPANY CLAIMSep 30, 2026

  A 2026 automation-focused vendor piece argues most teams update status pages 20–40 minutes after incident detection using tools like Statuspage or Instatus, because those tools require a human to log in and post, by which point customers are already filing support tickets.

  A vendor-argued complaint theme (manual posting lag) framed as the problem automation tooling should solve for small/mid SaaS teams.

  ustechautomations.com/resources/blog/saas-incident-communication-automation-2026
• Small SaaS teams communicating incidentsPRODUCTCOMPANY CLAIMSep 30, 2026

  Vendor comparison content for 2026 describes incident.io as tying status communication directly into the incident-response workflow, letting responders publish manual updates, automate steps, or use pre-approved templates, with a status page included in its free Basic plan and per-user pricing for advanced on-call/response features.

  Establishes current packaging reference point: free status page + paid per-user incident response tier, relevant to small teams comparing cost structures.

  editorialge.com/best-saas-status-page-tools/
• Small SaaS teams communicating incidentsPOSITIONINGCOMPANY CLAIMSep 30, 2026

  Buyer guidance content frames small SaaS status-page adoption as conditional rather than default: a status page is needed only when contracts/SLAs require recorded incident communication, outage scale overwhelms manual updates, customers need self-service history, or multiple independently-failing components require component-level status.

  Sets the buyer-language bar small SaaS teams are being told to use before purchasing any status-page tool.

  axonbuild.com/blog/status-page-small-saas
• Status page honestyPRICINGCOMPANY CLAIMSep 30, 2026

  Atlassian Statuspage pricing is commonly cited as starting around $29/month (Hobby) with private pages starting at $79/month and top plans reaching $399/month, while numerous alternatives (Hyperping from ~$19-24/mo flat with monitoring/on-call bundled, OpenStatus at $30/mo flat, UptimeRobot from $7-9/mo, Instatus from $15-20/mo) position themselves as cheaper and more automated than Statuspage's largely manual, page-only model.

  establishes the baseline packaging/pricing contrast driving the 'honesty via automation' argument — that manual status pages are the ones prone to the operational-during-outage problem, while automated/monitoring-linked pages claim to avoid it

  hyperping.com/blog/statuspage-pricing
• Status page honestyDISCOURSEUSER OPINIONSep 30, 2026

  A recent industry post frames the core complaint explicitly: status pages are described as failing during outages when they run on the same infrastructure they report on, show 'All systems operational' during a real outage, or post updates too late, leading users to stop trusting the page and fall back to support tickets and social media.

  confirms 'operational-during-outage' is a named, recognized failure mode in current discourse, not a one-off complaint

  statuspage.me/blog/monitoring/why-status-pages-fail-during-outages
• Status page honestyDISCOURSEUSER OPINIONSep 30, 2026

  A live example surfaced showing the pattern this discourse describes: on Sept 29, 2026 users reported Claude problems on Downdetector starting 10:19am ET while Anthropic's own status page and most third-party monitors continued to show the service operational, with one aggregator logging 150 user reports in 24 hours despite an official 'operating normally' status.

  illustrates the 'official green, crowd yellow' trust gap that fuels the status-page-honesty discourse, directly relevant to any vendor relying on self-reported status pages

  www.ibtimes.com.au/claude-users-report-problems-downdetector-anthropic-status-1876063
• OpenstatusPRODUCTFACTSep 30, 2026

  Openstatus ships a built-in AI chat assistant in the dashboard (launched May 16, 2026) that lets users query their workspace, draft status reports, and inspect monitors in natural language, with every tool call and mutation logged to an audit trail.

  BASELINE — establishes AI-agent feature set as part of the product's differentiation.

  www.openstatus.dev/changelog/chat-assistant
• OpenstatusPRODUCTFACTSep 30, 2026

  Openstatus rebuilt the dashboard's monitor Logs tab (Sep 4, 2026) on a new data-table-filters component to let users search, filter and slice every check a monitor has run.

  BASELINE — minor UX improvement, noted for completeness of recent activity.

  www.openstatus.dev/changelog/dashboard-response-logs
• OpenstatusPRODUCTFACTSep 30, 2026

  Openstatus recently added OAuth 2.1 sign-in for its MCP server (Sep 8, 2026), letting clients like Claude, ChatGPT, Cursor, Claude Code, or opencode connect via a consent screen instead of an API key, with per-connection workspace/permission scoping and revocation under Settings > Integrations.

  BASELINE — most recent product update, deepens AI-agent integration story.

  www.openstatus.dev/changelog/mcp-oauth
• OpenstatusPOSITIONINGCOMPANY CLAIMSep 30, 2026

  Openstatus positions itself as combining built-in uptime monitoring and a status page in one open-source, self-hostable product with flat pricing that doesn't scale with subscriber count, contrasting itself against Atlassian Statuspage, BetterStack, Status.io, UptimeRobot, Checkly, and Datadog Synthetics, each of which it claims lacks monitoring, charges per subscriber, or is closed-source.

  BASELINE — core competitive positioning against the category's major vendors.

  www.openstatus.dev/compare
• OpenstatusPRICINGFACTSep 30, 2026

  The free Hobby plan includes one monitor, one status page (with three page components), and a minimum check interval of 10 minutes.

  BASELINE — free tier scope for evaluating future packaging changes.

  www.openstatus.dev/
• OpenstatusPRICINGFACTSep 30, 2026

  Openstatus's current paid tiers are Starter ($30/mo), Pro ($100/mo), and Scale ($500/mo), differentiated by number of status pages, components, monitors, and check interval (1m on Starter, 30s on Pro/Scale), with all tiers including monitoring from 28 regions.

  BASELINE — establishes the pricing structure to compare future changes against.

  www.openstatus.dev/pricing
• Better StackPOSITIONINGCOMPANY CLAIMSep 30, 2026

  Better Stack positions itself as a unified alternative to fragmented observability stacks, citing an example of roughly $687/month for 1TB each of logs, traces, and metrics versus approximately $55,574/month for equivalent Datadog usage.

  Cost-disruption versus Datadog is the core buyer-facing pitch; establishes baseline positioning language to watch for shifts.

  www.modern-datatools.com/tools/better-stack/pricing
• Better StackPRODUCTCOMPANY CLAIMSep 30, 2026

  Better Stack made its Error tracking product generally available, describing it as Sentry-compatible, AI-native, and priced at roughly one-sixth the cost of alternatives.

  Marks error tracking as a fully-launched, actively marketed product line rather than beta, relevant to competitive positioning against Sentry.

  betterstack.com/community/blog/
• Better StackPRODUCTFACTSep 30, 2026

  Better Stack's official changelog shows recent feature releases including 'Changelog #15: Prompt a dashboard in 60 seconds' (AI-generated dashboards from connected databases/cloud providers) and 'Changelog #14: Incident filtering' for finding incidents by status, duration, and affected resource.

  Establishes the current product surface (AI-assisted dashboarding, incident filtering) as the baseline for detecting future feature changes.

  betterstack.com/tag/changelog
• Better StackPRICINGCOMPANY CLAIMSep 30, 2026

  Better Stack has no single price: it offers a free tier (10 monitors, 1 status page, basic log access), then a per-responder incident/on-call license priced around $29/month annual ($34 monthly), with separate add-on packs for extra monitors, telemetry volume (logs/metrics/traces), and status page features layered on top.

  Buyers comparing flat-rate competitors need to budget for modular add-ons; a solo project can run $29-60/mo while teams with heavier telemetry or white-labeled status pages can exceed $500-700/mo.

  betterstack.com/pricing
• InstatusCOMPLAINTUSER OPINIONSep 30, 2026

  Monitoring on Instatus's Pro tier is basic, limited to 50 monitors across 4 regions with no synthetic checks.

  Relevant to buyers comparing monitoring depth against dedicated observability competitors.

  hyperping.com/blog/best-statuspage-alternatives
• InstatusCOMPLAINTUSER OPINIONSep 30, 2026

  There is no tier between Pro and Business, which is described as the main pricing complaint, and this pricing cliff is consistently flagged by community reviews as the number-one complaint.

  Signals a recurring friction point for growing teams needing private pages or SSO without the full Business price.

  hyperping.com/blog/instatus-pricing
• InstatusPOSITIONINGCOMPANY CLAIMSep 30, 2026

  Instatus positions itself as 'the fast, flat-priced alternative' to Atlassian Statuspage, with Jamstack pages loading quickly in 30+ languages and bundled monitoring/on-call starting at $15/month with no per-seat fees.

  Establishes Instatus's core market positioning against the dominant incumbent.

  betterstack.com/community/comparisons/statuspage-vs-instatus/
• InstatusPRODUCTFACTSep 30, 2026

  Instatus's public changelog lists recent product additions including better DNS monitors, cron monitors that can open incidents automatically, multiple maintenance reminders, time zone support on status pages, support for 750+ third-party components, 50 languages (up from 30) with RTL support, recurring maintenance periods, inclusion of incidents from third-party components (starting with Statuspage), and General Notices for pinning persistent announcements.

  Establishes the current baseline feature set for monitoring buyers comparing against competitors.

  instatus.com/changes
• InstatusPRICINGCOMPANY CLAIMSep 30, 2026

  The Business plan unlocks private (authenticated) status pages, SAML SSO, higher subscriber limits, and more monitors, while these are gated behind a 15x price jump from Pro.

  Affects buyers needing SSO or private pages who must pay a large premium.

  hyperping.com/blog/instatus-pricing
• InstatusPRICINGCOMPANY CLAIMSep 30, 2026

  Instatus has a free Starter plan, a Pro plan at $20/month ($15/month billed annually), and a Business plan at $300/month ($225/month billed annually).

  Establishes baseline pricing structure and the tier gap between Pro and Business.

  hyperping.com/blog/instatus-pricing
• StatuspagePRODUCTFACTSep 30, 2026

  Statuspage deprecated old API keys and discontinued support for sending api_key in query parameters as of May 15, 2026, requiring integrations to send the key in the request header instead.

  Affects any customer with existing API integrations, requiring a required migration to header-based auth.

  community.atlassian.com/forums/discussion/3226055/upcoming-changes-to-statuspage-api-keys-action-required-by-may-15-2026
• StatuspagePRODUCTFACTSep 30, 2026

  Atlassian shipped a new 'Send update to Statuspage' Jira Automation action allowing automatic posting of status updates (e.g., 'Investigating' on Sev1 trigger, 'Resolved' on close) without manual steps, rolling out to all instances.

  Affects JSM/Statuspage joint customers by reducing manual incident-update work; a feature launch in the entity's own product area.

  community.atlassian.com/forums/Jira-Service-Management-articles/No-More-Incident-Communication-Stress-Introducing-Status-Pages/ba-p/3192703
• StatuspageCOMPLAINTUSER OPINIONSep 30, 2026

  One independent commentary argues Statuspage has shifted from a simple outage page to an enterprise incident platform with pricing floors from $29 to $399/month plus $300/month audience-specific add-ons, calling this a burden for MSPs billing per client.

  Signals a complaint theme among MSP/agency users about per-client cost scaling; first sighting, not yet at third-sighting threshold.

  provenstartups.substack.com/p/atlassian-statuspage-is-taxing-msps
• StatuspagePRICINGFACTSep 30, 2026

  Audience-specific pages use volume-based pricing with a base tier at $300/month (500 users, 10 groups, 25 team members, 30 metrics), with incremental increases of $200 (tiers 2-10), $100 (tiers 11-30), and $50 (tier 31+).

  Affects multi-tenant or MSP-style customers who need segmented audiences, a frequently cited cost pain point.

  support.atlassian.com/statuspage/docs/audience-specific-page-pricing/
• StatuspagePRICINGFACTSep 30, 2026

  A separate Private Pages pricing track exists: Starter ($79/mo), Growth ($249/mo), Corporate ($599/mo), and Enterprise ($1499/mo), for authenticated/internal status communication.

  Affects enterprises evaluating private stakeholder-facing incident comms costs.

  frontdeskreview.com/software/status-pages/atlassian-statuspage/
• StatuspagePRICINGFACTSep 30, 2026

  Statuspage's public-page pricing track is tiered as Free, Hobby ($29/mo), Startup ($99/mo), Business ($399/mo), and Enterprise ($1499/mo), each with published subscriber/team-member/metrics caps.

  Establishes the baseline public pricing ladder buyers compare against alternatives.

  frontdeskreview.com/software/status-pages/atlassian-statuspage/