Atlassian Statuspage vs Instatus

Atlassian Statuspage

This is a status communication product, not a checker: component status is driven from outside monitors such as DataDog, New Relic, Librato and Pingdom, or by an email with "UP" or "DOWN" in the subject line, and the pages we read describe no checks, intervals or probe locations of the product's own. That suits my team since our monitoring already exists, but nothing here evidences failure detection.

Instatus

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.

Atlassian Statuspage

The product itself notifies subscribers rather than an on-call rotation: email, text message and in-app, with Slack, Microsoft Teams, SMS and webhook notifications by plan, per-component subscriptions, and a reminder to email and SMS subscribers sixty minutes before scheduled maintenance. The vendor's Opsgenie pages document on-call dispatch with phone calls, mobile push and escalation until the alert is acknowledged or closed, but the Statuspage pages show no escalation policy or on-call schedule around page incidents.

Instatus

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.

Atlassian Statuspage

This is the tool I have been asking for: public pages on a custom domain with custom CSS, HTML and JavaScript, components including 150-plus ready-made third-party components like Stripe and PagerDuty, component groups, incident templates, subscribers reached by email, SMS, webhook, Slack or Teams, scheduled maintenance that tweets and resets components automatically, and an embeddable status widget. Audience-specific and private pages locked down with SAML single sign-on cover our largest accounts, and each component can show ninety days of uptime history with the calculation formula published. We found no public information on multiple languages or on keeping the status page hosting separate from the main service.

Instatus

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.

Atlassian Statuspage

There is a documented REST API with a downloadable OpenAPI specification covering pages, incidents, components, metrics, users and per-page role permissions, plus team member limits per plan with add and remove flows, and single sign-on via SAML 2.0 for team members (with Atlassian Guard) and for private-page viewers. We found no public information on a Terraform provider or command-line workflow, SCIM provisioning, audit logs or bulk import.

Instatus

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.

Atlassian Statuspage

Components can display ninety days of uptime history with the calculation formula published — partial outages weighted at thirty percent of major ones — and a day with downtime links to the related incident, while metrics are exposed through the API and customer data is retrievable through the product during the term. We found no public information on scheduled reports, an SLA with credits, or the vendor's own status page and incident history; historical uptime can also be edited by hand, which I would hesitate to put in front of a client at renewal.

Instatus

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.

Atlassian Statuspage

The contracting entity is Atlassian Pty Ltd, incorporated in Australia and addressed in San Francisco, and the privacy policy states information may be transferred, processed and stored outside the customer's country, with no hosting location stated anywhere we read. On the credit side there is a published data processing agreement, a public subprocessor list with thirty days' notice of changes and a termination remedy, EU and UK representatives, Irish law for EMEA customers, and independent third-party audits and certifications described. For our payroll and tax clients the data-residency question is left open rather than answered.

Instatus

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.

Atlassian Statuspage

All five tiers are public with their subscriber, team member and metric limits — the free plan, Hobby $29 /month, Startup $99 /month, Business $399 /month and Enterprise $1,499 /month — and the customer agreement states a thirty-day return window, auto-renewal at then-current rates and overage at then-current rates. What we could not compute: extra team members beyond a plan go through support, private-page single sign-on viewer numbers are said to depend on the plan without being listed, and VAT treatment is not stated on the pricing page.

Instatus

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.