Atlassian Statuspage vs Instatus

Atlassian Statuspage

The captured pages show a communication endpoint, not a monitor: component status arrives from DataDog, New Relic, Librato or Pingdom, or from an email whose subject line contains UP or DOWN, and the product's own pitch is real-time status communication to users. I found no public information on any HTTP, ping, TCP or SSL check Statuspage runs itself, on probe locations or check intervals, so there is no second-location confirmation of a failure because no failure is detected here.

Instatus

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.

Atlassian Statuspage

Statuspage notifies subscribers — email, SMS and webhook on component changes and maintenance, an auto-tweet, and a reminder 60 minutes before a maintenance window — which is communication, not paging. The escalation rules, phone calls and on-call rotations in the captured pages belong to Opsgenie, a separate Atlassian product whose alerts update the page rather than being driven by it; I found no public information on escalation or acknowledgement workflows inside Statuspage, or on what an SMS to a subscriber costs.

Instatus

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.

Atlassian Statuspage

This is the core product: public, private and audience-specific pages on a custom domain with CSS/HTML/JS control, components and groups, incident templates, scheduled maintenance with four states and automated component changes, email/SMS/webhook subscribers with per-component subscriptions, SAML single sign-on on private pages, and embeddable status widgets. The 90-day uptime showcase publishes its formula — partial outages weighted at 30 percent — but the record is the customer's own declarations and stays editable by hand. I found no public information on RSS delivery, additional page languages, or how the page's hosting stays independent of the service it reports on when that service falls over.

Instatus

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.

Atlassian Statuspage

A documented REST API with a downloadable OpenAPI spec, per-page role-based access control, team members managed per plan through Atlassian admin groups, SAML single sign-on — via Atlassian Guard for team members, natively for private-page viewers — and IP allowlisting are all evidenced. The API is capped at one request per second unless you ask for an increase; I found no public information on a Terraform provider, CI/CD checks, SCIM provisioning, audit logs or two-factor authentication, and team members beyond a plan's allocation are handled by contacting support to increase the allocation.

Instatus

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.

Atlassian Statuspage

The uptime showcase keeps 90 days of per-component history on a dedicated /uptime page, with a published formula and links from each bad day to the incident that caused it — but the bars derive from incidents and maintenances the customer records and remain editable by hand, with partial outages counting only 30 percent as bad, so this is a curated record rather than a measurement. I found no public information on scheduled reports, bulk export, response-time data, an SLA with credits, or Atlassian's own status page and incident history; the customer agreement only says a service level agreement is specified where applicable.

Instatus

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.

Atlassian Statuspage

The contracting party is Atlassian Pty Ltd, incorporated in Australia and addressed care of San Francisco, the named EU representative Atlassian B.V. is also addressed care of San Francisco, and the privacy policy reserves transferring information to wherever Atlassian or its third-party service providers operate. A data processing agreement exists with a published sub-processor list, 30 days' notice of changes and termination as the customer's sole remedy on objection — real paperwork, but I found no public information on where account data, subscriber phone numbers or page history are stored, or on any EU hosting option.

Instatus

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.

Atlassian Statuspage

Five tiers are public with their subscriber, team member and metric limits — free, Hobby $29 /month, Startup $99 /month, Business $399 /month, Enterprise $1,499 /month — and the free tier states its 100 subscribers, 25 components and two team members. Computability stops there: team-member single sign-on rides on separately sold Atlassian Guard, overages are charged at Atlassian's then current rates, extra team members mean contacting support, and I found no public information on what an SMS to a subscriber costs or on VAT treatment.

Instatus

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.