Uptime Monitoring & Status Pages
Atlassian Statuspage
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Atlassian Pty Ltd · www.atlassian.com
Compare with Instatus → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Atlassian Statuspage at a glance
- Vendor
- Atlassian Pty Ltd
- Headquarters
- Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 1 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 1 Nov 2026
- Panel verdict
- The AI panel rates Atlassian Statuspage 2/5, the mean of 6 judges. Atlassian Statuspage is a status communication product, not a monitor: component status arrives from DataDog, New Relic, Librato or Pingdom, or from an email with UP or DOWN in the subject line, and checks and locations scores sit at 0. how scores are made
- As of
- Vendor pages captured 1 Nov 2026; evaluated by the panel 2 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Atlassian Statuspage is a status communication product, not a monitor: component status arrives from DataDog, New Relic, Librato or Pingdom, or from an email with UP or DOWN in the subject line, and checks and locations scores sit at 0. Status pages leads at 7 to 8: public, private and audience-specific pages on a custom domain with custom CSS, HTML and JavaScript, incident templates, embeddable widgets, and a 90-day per-component uptime history with the formula published. Automation and teams sits at 6 throughout on a documented REST API with an OpenAPI specification. Alerting and on-call splits the judges 3 to 6 — the higher marks credit subscriber channels from email and SMS to Slack and Teams; the lower ones weigh paging, since escalation, phone calls and on-call rotations are documented on the captured pages only for the separate Opsgenie product. Reports and reliability spread 3 to 5 over an uptime record derived from incidents a person records and editable by hand. Pricing transparency runs 5 to 7, with all five tiers public from a free plan to Enterprise $1,499 /month.
Speaks for it
- Status pages scored 7 to 8 for public, private and audience-specific pages on a custom domain with custom CSS, HTML and JavaScript, incident templates and embeddable widgets.
- A documented REST API with a downloadable OpenAPI specification covers incidents, components, metrics and per-page role permissions.
- All five tiers are public with subscriber, team-member and metric limits, from the free plan's 100 subscribers, 25 components and two team members to Enterprise $1,499 /month.
- A 90-day per-component uptime history displays with its calculation formula published, linking each day of downtime to the related incident.
- A published data processing agreement carries a public sub-processor list with thirty days' notice of changes, plus Irish governing law for EMEA customers.
Held against it
- Checks and locations scored 0: status arrives from DataDog, New Relic, Librato, Pingdom or email keywords, and we found no public information on any check, probe location or interval the product runs.
- Escalation rules, on-call schedules, phone calls and acknowledgement flows are documented on the captured pages only for the separate Opsgenie product.
- Uptime history derives from incidents a person records, counts partial outages at 30 percent, and remains editable by hand.
- The privacy policy states information may be transferred and stored outside your country of residence, and we found no public information on where account data or subscriber lists are hosted.
- Team-member single sign-on requires the separately sold Atlassian Guard, and we found no public information on per-message SMS costs or VAT treatment.
Best for
- You already run monitoring in DataDog, New Relic or Pingdom and want a public page that updates from it.
- You need to notify subscribers across email, SMS, webhook, Slack and Teams, and lock private pages behind SAML single sign-on.
- You drive incident and component updates through a documented REST API with per-page role permissions.
- You schedule maintenance and want automated notifications, tweets and component resets at the window's start and end.
Avoid if
- You need one tool that both detects failures and communicates them — the captured pages describe status arriving from external monitors rather than any check of its own.
- You need built-in on-call paging and escalation to wake engineers — the captured pages document those only for the separate Opsgenie product.
- Your compliance review requires a stated hosting location — the privacy policy states information may be transferred and stored outside your country of residence.
- You need an audit-proof uptime record for arguing downtime costs — the history is editable by hand and partial outages count 30 percent.
The scores
| Criterion | Panel median |
|---|---|
| Checks, locations & failure confirmation | 0 of 5 |
| Alerting, escalation & on-call | 2 of 5 |
| Status pages & incident communication | 4 of 5 |
| API, monitoring as code & team administration | 3 of 5 |
| Uptime reports, data & the vendor's own reliability | 2 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 3 of 5 |
Checks, locations & failure confirmation
Show reasoningHide reasoning
How this is scored
What can be monitored and how reliably a failure is detected: HTTP(S) with status code and keyword checks, TCP and port, ping, DNS records, SSL certificate and domain expiry, cron jobs and heartbeats, multi-step API checks with assertions, browser or transaction checks of a login or checkout, the shortest check interval, the number and regions of probe locations, the re-check from a second location before an alert, timeouts and response time thresholds, and private locations inside the customer's own network.
0 — Runs no checks of its own; a status page or alerting tool that only receives signals from other monitors.
3 — HTTP checks of a URL at a fixed interval with an up or down result; keyword, SSL, cron and the probe locations are basic or not described.
5 — HTTP(S), keyword, TCP or port, ping and SSL expiry checks, cron or heartbeat monitoring, an interval of one minute or less, several named probe locations, a failure confirmed from a second location before alerting, and response times recorded per check.
8 — Multi-step API checks with assertions on headers and body, browser or transaction checks of a user flow, DNS and domain expiry checks, sub-minute intervals, probe locations listed by city with the confirmation logic documented, private locations or agents for internal services, and maintenance windows that pause checks.
10 — Coverage and accuracy a reliability team runs on: every check type above with code-based checks (for example Playwright or scripted tests) in version control, location-specific thresholds, false-positive handling and probe health published, and the detection method documented so a result can be reproduced.
The Agency Developer
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. 1 3
The SaaS Platform Engineer
The captured pages show a status communication product rather than a monitor: component status is set by email keywords or by integrations with DataDog, New Relic, Librato or Pingdom, and the 90-day uptime display is computed from incidents and maintenance a person records — it can even be edited by hand afterwards. We found no public information on HTTP, keyword, DNS or multi-step checks of its own, on probe locations, or on a confirmation from a second location, so detection would still depend on a separate monitoring tool. 1 3 15
The Customer Support Lead
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. 1 3
The E-Commerce Operations Manager
The captured pages describe Statuspage as real-time status communication for users, and monitoring is described in the other direction — DataDog, New Relic or Pingdom update my page once they detect an issue, or an email with "UP" or "DOWN" in the subject line flips a component. I found no public information on Statuspage running HTTP, keyword or transaction checks against my checkout and payment pages itself, so detection would have to come from another tool. 1 3 11
The Information Security Officer
The product is documented as a status communication service that receives signals from external monitors such as DataDog, New Relic, Librato and Pingdom, or from an email whose subject contains "UP" or "DOWN"; the synthetic-check and escalation material captured concerns the vendor's separate Opsgenie product. We found no public information on any checks, probe locations, check intervals or failure confirmation run by the product itself. 1 3 11
The Skeptic
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. 1 3
Alerting, escalation & on-call
panel disagrees
Show reasoningHide reasoning
How this is scored
How the right person learns about a failure: alert channels (email, SMS, phone call, push app, Slack, Microsoft Teams, Telegram, webhooks), alerts to PagerDuty, Opsgenie or similar tools, escalation policies when an alert is not acknowledged, on-call schedules and rotations, acknowledge and resolve from the app, alert grouping and noise reduction, recovery notifications, maintenance windows that mute alerts, and whether SMS and calls are included or charged per message.
0 — No alerting at all; results can only be viewed in the dashboard.
3 — Email alerts and one or two chat integrations; escalation, phone calls and schedules are basic or not described.
5 — Email, SMS, a mobile push app, Slack, Microsoft Teams and webhooks, alerts forwarded to PagerDuty or Opsgenie, per-monitor alert contacts, recovery notifications, a delay or threshold before alerting, and maintenance windows that mute alerts.
8 — Phone call alerts, escalation policies with timeouts, on-call schedules and rotations with overrides, acknowledge and resolve from the app or chat, alert grouping, incident timelines with who did what, and the price of SMS and calls stated per country or included in the plan.
10 — On-call that replaces a separate incident tool: follow-the-sun schedules, escalation across teams, alert routing by service and severity, post-incident reviews generated from the timeline, and delivery of every alert channel monitored and reported.
The Agency Developer
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. 5 13 3 11
The SaaS Platform Engineer
Subscriber notifications are the strength: email, SMS, webhooks, Slack and Microsoft Teams by plan, with a reminder to email and SMS subscribers 60 minutes before scheduled maintenance and automatic completion notices. The captured pages on phone calls, on-call schedules and escalation describe Opsgenie rather than Statuspage itself — Statuspage's documented role is to be updated from alerting apps like Opsgenie, PagerDuty, VictorOps or xMatters, so for waking an engineer at night I would still pair it with our own paging stack. 1 3 5 11 13
The Customer Support Lead
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. 5 13 11 14
The E-Commerce Operations Manager
Notification channels are broad — subscribers can get email, text message, in-app messages, Slack, Microsoft Teams and automated Twitter updates, and scheduled maintenance notifies email, text and webhook subscribers with a reminder before the window starts. But that reaches my customers, not my night shift: I found no public information on escalation policies, on-call schedules, acknowledge-and-resolve or phone-call alerts for Statuspage itself — the escalation and on-call pages captured belong to the vendor's separate Opsgenie product. 1 3 5 13 14
The Information Security Officer
Documented alerting is subscriber-facing: email, SMS and webhook notifications, updates piped into Slack and Microsoft Teams channels, automated Twitter posts, and an email and SMS reminder sixty minutes before scheduled maintenance. Escalation rules, on-call schedules, phone-call alerts and acknowledge flows appear only in the vendor's separate Opsgenie product, which the page integrates with to update status from the alerting app. 1 3 13 11 14
The Skeptic
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. 3 11 13
Status pages & incident communication
Show reasoningHide reasoning
How this is scored
How customers and colleagues are told: public status pages on a custom domain with SSL, components and component groups fed automatically by monitors or set by hand, incident updates and scheduled maintenance announcements, subscribers notified by email, SMS, RSS or webhook, uptime history shown per component, private or password-protected pages for internal teams or single customers, branding and custom CSS, several languages, page templates, and how the status page itself stays online when the main product is down.
0 — No status page of any kind.
3 — A public status page listing monitors with their current state; custom domain, incident updates and subscribers are basic or not described.
5 — Public status pages on a custom domain, components linked to monitors, incident updates and scheduled maintenance, email subscribers, uptime history per component, the vendor's branding removable, and a password-protected or private page option.
8 — Component groups, SMS, RSS and webhook subscribers with per-component subscriptions, private pages with single sign-on or IP restriction, several languages, incident templates, embeddable status widgets, audience-specific pages for single customers, and the status page hosting kept separate from the main service and documented.
10 — Incident communication end to end: incidents drafted from monitor events and approved by a person, updates published to the page, subscribers, chat and social channels at once, a full incident archive with post-mortems, status page uptime published, and accessibility of the page stated.
The Agency Developer
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. 5 15 16 3 1
The SaaS Platform Engineer
This is the product's core and it is strong: public, private and audience-specific pages, custom domain with custom CSS/HTML/JS, component groups with rolled-up uptime, per-component subscriptions, incident templates, embeddable status widgets, automated tweets and SAML single sign-on locking private pages to employees. Uptime showcase adds 90 days of per-component history on a dedicated page with the calculation published. We found no public information on several languages or on how the status page hosting is kept separate from the main service. 1 3 5 13 15 16
The Customer Support Lead
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. 1 5 15 16 13 3
The E-Commerce Operations Manager
This is the product's core and it is thorough: public, private and audience-specific pages on a custom domain, custom styling up to CSS, HTML and JavaScript on the Business tier, components and component groups with per-component subscriptions, incident templates, embeddable status widgets, scheduled maintenance with automated notifications, and a 90-day uptime display per component with the calculation published. Private pages lock down with SAML 2.0 single sign-on or IP allowlisting. I found no public information on page languages, RSS subscribers, or how the page itself stays online when the vendor's service has trouble. 1 3 5 13 15 16
The Information Security Officer
This is the product's core: public, private and audience-specific pages on a custom domain with custom CSS, HTML and JS, components and component groups with per-component subscriptions, incident templates, scheduled maintenance in four states with automated subscriber notifications and tweets, embeddable widgets, SAML single sign-on for private pages, and a ninety-day per-component uptime history whose calculation formula is published. We found no public information on RSS subscriptions, additional page languages, or documentation of how the page hosting is kept separate from the vendor's main service. 1 3 5 13 15 16
The Skeptic
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. 1 3 5 13 15 16
API, monitoring as code & team administration
Show reasoningHide reasoning
How this is scored
How the tool fits a team and a deployment pipeline: a documented REST API to create and read monitors, status pages and incidents, a Terraform provider, CLI or monitoring-as-code workflow, checks run from CI/CD before a deploy, bulk import of monitors, integrations with ticketing and chat tools, team members with roles, single sign-on (SAML) and SCIM, audit logs, several teams or client accounts in one organisation, white-label or client reporting for agencies, and two-factor authentication.
0 — No API, no team accounts; one login per account and monitors are set up only by hand.
3 — A web dashboard with a few team members; the API, roles and multi-client set-up are basic or not described.
5 — A documented REST API covering monitors and status pages, webhooks, team members with roles, two-factor authentication, bulk import or a CSV upload of monitors, and several projects, teams or client groups in one account.
8 — A Terraform provider or monitoring-as-code CLI with checks kept in version control, checks triggered from CI/CD, single sign-on (SAML), SCIM provisioning, audit logs, sub-accounts for clients with their own logins, and white-label client reports.
10 — Administration that scales across many teams and clients: every setting reachable by API and code with parity stated, granular roles per resource, SSO enforced with SCIM, audit logs exportable to a SIEM, and agency or reseller accounts with separate billing.
The Agency Developer
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. 4 5 17 16
The SaaS Platform Engineer
A documented REST API with an OpenAPI download covers pages, incidents, postmortems, metrics and per-page role permissions, and team member management, group-based access through Atlassian admin and SAML single sign-on are all described. As someone who keeps checks in Terraform next to the services they test, we found no public information on a Terraform provider, a monitoring-as-code workflow, SCIM provisioning or audit logs for Statuspage itself. 4 5 16 17
The Customer Support Lead
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. 4 5 17 16
The E-Commerce Operations Manager
There is a documented REST API with an OpenAPI specification covering incidents, components, metrics, postmortems and per-page user roles, plus team member limits per plan and SAML 2.0 single sign-on — for team members via Atlassian Guard and for private-page viewers. I found no public information on Terraform or monitoring-as-code, checks triggered from CI/CD, SCIM provisioning, audit logs or bulk import of monitors. 1 4 5 16 17
The Information Security Officer
A documented REST API with an OpenAPI description covers incidents, components, metrics, status embeds and per-page role assignments for users, and SAML 2.0 single sign-on is documented for private pages and, with Atlassian Guard, for team members. We found no public information on audit logs, SCIM provisioning, two-factor authentication, monitoring-as-code or bulk import — the audit trail and provisioning controls I would need before rollout are not documented. 4 16 17 5 1
The Skeptic
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. 1 4 16 17
Uptime reports, data & the vendor's own reliability
Show reasoningHide reasoning
How this is scored
What the record is worth and whether the monitor itself can be trusted: uptime and SLA reports per monitor and period, response time charts and percentiles, scheduled reports by email, client-facing reports, how long check results and incident history are kept, export of results by CSV or API, the vendor's own public status page and incident history, its SLA, the probe IP addresses and user agent published for allow-listing, and an open-source or self-hosted edition.
0 — No history of any kind; only the current state is shown.
3 — An uptime percentage and a response time chart per monitor; retention, export and the vendor's own status are basic or not described.
5 — Uptime and response time reports per monitor and period, SLA reports, scheduled email reports, the retention period of check results stated, CSV or API export, the probe IPs published, and the vendor's own public status page.
8 — Response time percentiles and breakdowns (DNS, connect, TLS, first byte), client-ready branded reports, retention of a year or more stated per plan, a raw export of check results, the vendor's incident history and post-mortems public, and an SLA with credits published.
10 — A record that holds up in an audit: SLA calculations with their method stated, incident records suitable for ISO 27001, NIS2 or DORA evidence, full history exportable in an open format, a self-hosted or open-source edition with feature parity stated, and the vendor's own availability over several years published.
The Agency Developer
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. 15 4 7
The SaaS Platform Engineer
Uptime showcase shows 90 days of per-component history with its formula published — major outage minutes plus partial outage minutes weighted at 30 percent, divided by total minutes — and incident postmortems are reachable through the API. That history derives from incidents a person records and can be edited afterwards, and we found no public information on SLA reports, retention beyond the display window, export of results, or the vendor's own status page and incident history; the customer agreement only points to a service level agreement existing elsewhere. 4 7 15
The Customer Support Lead
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. 15 3 9 7
The E-Commerce Operations Manager
Uptime history runs 90 days per component with the formula published — partial outages count 30 percent as bad as major ones — and it can be edited by hand, so I read it as customer communication rather than an audit-proof record for arguing downtime costs with my agency. The customer agreement points to a service level agreement without publishing its terms here, and I found no public information on response-time data, scheduled reports, or the vendor's own status page and incident history. 4 7 15
The Information Security Officer
The record offered is a ninety-day per-component uptime history with a published formula that weights partial outages at thirty percent, rolled-up group averages and links to the related incidents, with incident postmortems reachable through the API and a service level agreement referenced in the customer agreement. Historical uptime can be edited by hand and degraded performance is excluded from the calculation, and we found no public information on response-time reporting, export of results, retention beyond the display window, or the vendor's own status page and incident history. 15 4 7 10
The Skeptic
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. 4 7 15
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where account data, alert contacts (names and phone numbers of the people on call), status page subscribers and check results are stored and processed, and who the subprocessors are (hosting, SMS and phone gateways, email delivery, support and payment tools). Independently sourced by the sovereignty pipeline. Probe locations outside Europe are part of what the product does and are not counted against it; where the data is stored and who processes it is. A self-hosted or open-source edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (SMS and call gateways, email, support, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every record on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, or a self-hosted open-source edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The Agency Developer
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. 6 8 9 7
The SaaS Platform Engineer
The contracting entity is Atlassian Pty Ltd, incorporated in Australia and addressed in San Francisco, the privacy policy permits collecting and transferring information globally to wherever Atlassian or its providers operate, and we found no public information on where account data, subscriber lists or check records are hosted. On the plus side a data processing agreement is published with a public sub-processor list and 30 days' notice of changes, an EU representative and Irish governing law for EMEA customers — but nothing in the captured pages evidences EU hosting. 6 7 8 9
The Customer Support Lead
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. 6 8 9 7
The E-Commerce Operations Manager
The contracting entity is Atlassian Pty Ltd, incorporated in Australia and addressed in San Francisco, the privacy policy states information may be transferred and stored wherever Atlassian and its service providers operate, and the captured pages state no hosting location for account data or subscriber lists. A published data processing agreement, a public sub-processor list with 30 days' notice, an EU representative and Irish law for EMEA customers are the European safeguards shown; for my German shop the unstated data location is the sticking point. 6 7 8 9
The Information Security Officer
The contracting entity is Atlassian Pty Ltd, incorporated in Australia with a San Francisco service address, and the privacy policy states information may be transferred and stored wherever Atlassian or its third-party providers operate; an EU representative and Irish law for EMEA customers exist. A data processing agreement is published with a publicly maintained subprocessor list and thirty-day change notice, but we found no public information on EU hosting options or where subprocessors are located, and audits and certifications are stated only in general terms. 6 8 9 7
The Skeptic
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. 6 7 8 9
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per tier by number of monitors, check interval and status pages, team seats and on-call responders, what SMS and phone alerts cost, which features (multi-step or browser checks, SSO, longer retention, private locations, white-label) cost extra, the free tier and its limits, overage handling, minimum term and VAT.
0 — No public prices at all; every customer is a sales call.
3 — A starting price or a free tier exists, but how cost scales with monitors, intervals, seats or alerts is unclear.
5 — Tiers are public with their monitor count, interval and main inclusions, but at least one commonly needed piece (SMS or call alerts, extra seats, extra status pages, SSO, longer retention) is unpriced or "on request".
8 — Every tier priced publicly with its scaling rule (monitors, interval, seats, responders, status pages), SMS and call costs stated, add-ons priced, overage handling stated, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given number of monitors, interval, team size and alert volume, with every add-on, overage and support fee and the cancellation and data-return terms published.
The Agency Developer
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. 5 1 7 17
The SaaS Platform Engineer
Four paid tiers and a free plan are public with their subscriber, team-member and metric limits and feature inclusions, alongside auto-renewal terms, overage charged at then-current rates that may be prorated, and a 30-day return policy. The gaps that matter to my budget: we found no public information on what SMS notifications cost per message, what Atlassian Guard adds for single sign-on, the pricing of private page plans, or the cost of extra team members beyond contacting support. 5 7 16 17
The Customer Support Lead
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. 1 5 7 17 16
The E-Commerce Operations Manager
All five tiers are public from a free plan up to Business $399 /month and Enterprise $1,499 /month, each with subscriber, team member and metric limits, and the customer agreement adds a 30-day return window and auto-renewal terms. Single sign-on requires Atlassian Guard at a price I found no public information on, extra team members are a support request rather than a listed price, and I found no public information on the cost of a text message to a subscriber or on VAT treatment. 1 5 7 17
The Information Security Officer
Five tiers from a free plan to Enterprise at $1,499 /month are public with subscriber, team-member, component and metric limits, and the agreement documents auto-renewal, overage at then-current rates and a thirty-day refund window. Team-member single sign-on requires the separately priced Atlassian Guard, additional team members beyond plan limits are handled by contacting support, and we found no public information on SMS message costs or VAT treatment. 1 5 7 17 16
The Skeptic
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. 1 5 7 17
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined ⚠ unverified | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Atlassian Statuspage
Is Atlassian Statuspage European?
No. whats-best.ai classifies Atlassian Statuspage as Rest of world.
Where does Atlassian Statuspage store data?
Not stated on the vendor’s pages as of 1 Nov 2026.
Does Atlassian Statuspage have a free plan?
Yes. Atlassian Statuspage has a free plan, per the vendor’s page captured 1 Nov 2026.
What are the best alternatives to Atlassian Statuspage?
As of 2 Nov 2026, the panel rates Hyperping (3.5/5), Checkly (3.5/5) and openstatus (3.5/5) 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 (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Atlassian Statuspage alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 13 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. Know more? Tell us
- 9 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. Know more? Tell us
- 4 support 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. Know more? Tell us
- 3 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. Know more? Tell us
- 3 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. Know more? Tell us
- 2 data 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. Know more? Tell us
- 2 integrations 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. Know more? Tell us
- 1 subprocessors 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. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (18)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage (product page) www.atlassian.com Checked 1 Nov 2026 Details →
- 2 Features page www.atlassian.com Checked 1 Nov 2026 Details →
- 3 Integrations page www.atlassian.com Checked 1 Nov 2026 Details →
- 4 API documentation developer.statuspage.io Checked 1 Nov 2026 Details →
- 5 Pricing page www.atlassian.com Checked 1 Nov 2026 Details →
- 6 Legal notice www.atlassian.com Checked 1 Nov 2026 Details →
- 7 Terms of service (customer agreement) www.atlassian.com Checked 1 Nov 2026 Details →
- 8 Privacy policy www.atlassian.com Checked 1 Nov 2026 Details →
- 9 Data processing agreement (dpa) www.atlassian.com Checked 1 Nov 2026 Details →
- 10 Security / trust page www.atlassian.com Checked 1 Nov 2026 Details →
- 11 Checks, locations & failure confirmation — found from sitemap support.atlassian.com Checked 1 Nov 2026 Details →
- 12 Checks, locations & failure confirmation — found from sitemap www.atlassian.com Checked 1 Nov 2026 Details →
- 13 Alerting, escalation & on-call — found from sitemap support.atlassian.com Checked 1 Nov 2026 Details →
- 14 Alerting, escalation & on-call — found from sitemap support.atlassian.com Checked 1 Nov 2026 Details →
- 15 Status pages & incident communication — found from sitemap support.atlassian.com Checked 1 Nov 2026 Details →
- 16 Status pages & incident communication — found from sitemap support.atlassian.com Checked 1 Nov 2026 Details →
- 17 API, monitoring as code & team administration — found from sitemap support.atlassian.com Checked 1 Nov 2026 Details →
- 18 API, monitoring as code & team administration — found from sitemap support.atlassian.com Checked 1 Nov 2026 Details →