Atlassian Statuspage vs Instatus

Atlassian Statuspage

The captured pages describe a status communication product — "communicate real-time status to your users" — whose signals come from DataDog, New Relic, Librano or Pingdom integrations, or from an email whose subject line contains UP or DOWN. We found no public information on HTTP, keyword, SSL certificate or domain expiry checks run by the product itself; for my sixty client sites I would still need a separate tool doing the actual watching.

Instatus

The help pages document DNS, TCP and UDP checks run from the United States, Canada, Europe and Asia, a configurable interval that reaches 30 seconds on paid plans, and automatic incident creation plus auto-resolution on recovery. For my client sites I specifically need keyword and certificate-expiry checks, and we found no public information on HTTP keyword checks, SSL certificate or domain expiry checks, cron or heartbeat monitoring, or a re-check from a second location before an alert fires.

Atlassian Statuspage

Notifications go out by email, SMS, webhook, Slack and Microsoft Teams depending on the plan, and scheduled maintenance sends reminders to email and SMS subscribers sixty minutes before the window starts. Escalation, on-call schedules, phone calls and acknowledgement until closure are documented in the captured pages for Opsgenie, a separate Atlassian product Statuspage integrates with, and we found no public information on escalation policies, acknowledgement flows or per-message SMS and call pricing inside Statuspage itself.

Instatus

Alert channels scale from Email to Email & SMS to SMS & Calls across the plans, incident escalations are a listed feature, and the on-call API documents daily, weekly and custom rotations with time-of-day and time-interval restrictions — enough to run a real rota. We found no public information on acknowledging or resolving from the app, alert grouping or maintenance windows that mute alerts, and SMS runs through your own Twilio, Vonage, Esendex, Bird or AWS SNS account, so no per-message price appears.

Atlassian Statuspage

This is the product's core: public, private and audience-specific pages on a custom domain with custom CSS/HTML/JS, component groups with rolled-up uptime bars and per-component subscriptions, incident templates, embeddable widgets with custom positioning and colors, and single sign-on via SAML plus IP allowlisting to lock a page to employees or a single client. The uptime showcase adds a ninety-day history per component with a full account on a dedicated /uptime page. We found no public information on additional page languages, RSS subscribers, or how the page hosting is kept separate from the main service.

Instatus

This is clearly the core of the product: components with their own uptime history and groups, subscriber channels from email and SMS to Slack, Discord, X, RSS and the public API with CSV import, custom domains, and private or audience-specific pages whose login runs through the single sign-on setup — audience-specific pages are exactly what I want per client. We found no public information on multiple languages, incident templates, embeddable widgets or custom branding in the captured pages.

Atlassian Statuspage

There is a documented REST API with an OpenAPI specification covering pages, components, incidents, metrics and postmortems, role-based access control per page, team member add and remove flows with allocation cumulative across all activated pages, and SAML single sign-on for team members (with Atlassian Guard) and for private-page viewers. We found no public information on a Terraform provider or monitoring-as-code workflow, SCIM provisioning, audit logs, or client sub-accounts with their own logins — which is what I would need to hand sixty client pages to their owners.

Instatus

Single sign-on with SAML, OpenID and CAS plus SCIM directory sync and multiple SSO connections are documented for the Business plan, the API covers status page updates, on-call schedules and third-party monitoring integrations, and Zapier and Jira are listed. We found no public information on team roles, audit logs, client sub-accounts with their own logins, white-label reporting or a bulk import of monitors — which is how I would set up sixty client checks in one go.

Atlassian Statuspage

Components get a ninety-day uptime display plus a full historical account on the /uptime page, and the method is published — major outage minutes plus partial outage minutes weighted at thirty percent, over total minutes — with links from each bar to the related incident; custom metrics and postmortems are reachable through the API. We found no public information on scheduled email reports, SLA terms with credits, or Atlassian's own status history. Historical uptime is documented as editable by hand, which I would keep in mind before presenting the numbers to a client as proof.

Instatus

Uptime history per component and public response statistics are documented, the vendor publishes its own availability on instat.us measured from multiple locations with independent monitoring, and there is a real SLA with a stated credit formula and a 30-day claim window. We found no public information on scheduled or client-facing monthly uptime reports, retention periods for check results, response-time percentiles, or published probe IP addresses for 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 is collected globally and may be stored "outside of your country of residence, to wherever we or our third-party service providers operate"; we found no public information on EU hosting. A published data processing agreement with a public sub-processor list, thirty days' notice of changes, an EU representative and Irish governing law for EMEA customers lift it above the minimum, though no certification such as ISO 27001 or SOC 2 is named in the captured pages.

Instatus

Instatus, Inc. is a Delaware corporation that stores data primarily in the United States, payments run through Paddle as reseller and Merchant of Record, and a data processing addendum applies automatically with Standard Contractual Clauses for transfers from the EEA. A subprocessors page is referenced but the captured pages do not show the provider list, and we found no public information on an EU hosting option, a European contracting entity, or ISO 27001 or SOC 2 certifications.

Atlassian Statuspage

Every tier is public with exact prices — the free plan, Hobby $29 /month, Startup $99 /month, Business $399 /month and Enterprise $1,499 /month — each with its subscriber, team-member and metric limits, a thirty-day refund window on initial orders, and overages charged at then-current rates; the scaling unit is subscribers and metrics rather than monitors, since the product does not monitor. Team single sign-on requires Atlassian Guard, additional team members beyond a plan are a support request, and we found no public information on its price, on per-message SMS costs, or on VAT treatment of the listed prices.

Instatus

The tier table is unusually detailed — monitors, check interval, team and on-call members, subscribers, custom domains and alert channels per plan, "STARTER FREE", "YEARLY 25% OFF" and three months free on annual payment — and the terms add US-dollar fees, VAT excluded, invoicing for Business and Enterprise, and a 30-day price-change notice. The captured pricing page shows no amounts for Pro and Business, so at two hundred monitors the Business plan's annual cost cannot be computed from public pages, and per-message SMS prices are absent because texts run through your own provider.