Atlassian Statuspage in 2026: Features, Pricing, Limits & the Opsgenie Migration Cost
Quick answer: Atlassian Statuspage is a hosted status page product for telling customers and employees about incidents and scheduled maintenance. Public pages run from a free plan (100 subscribers) through Hobby at $29/month, Startup at $99, Business at $300 and Enterprise at $1,499, with prices rising by subscriber count (Atlassian's pricing page, checked 26 October 2026). For teams leaving Opsgenie, the catch is that Jira Service Management, Atlassian's recommended replacement, only includes native status pages on its Enterprise plan. Teams on Standard ($21.50/agent/month) or Premium ($55.28/agent/month) still need a separate Statuspage subscription, so the "one-vendor" migration path is usually two products and two bills.
Every incident has two jobs: fixing the problem and telling people about it. For years, many teams split those jobs across two Atlassian products, Opsgenie for alerting and on-call, and Statuspage for customer updates, and never thought about the boundary between them.
That boundary matters now. Atlassian stopped selling Opsgenie in June 2025 and shuts it down on 5 April 2027, and points customers to Jira Service Management (JSM). Many teams assume JSM covers the status page too. On most plans, it doesn't.
This guide covers what Atlassian Statuspage does, how its component statuses work, what each plan includes and costs today, and what Opsgenie customers actually end up buying when they follow Atlassian's migration path, with the math at four team sizes. Every price here was checked on Atlassian's own pages on 26 October 2026; Atlassian has changed several of them since September, so check again before you buy.
A note on where we stand. ITOC360 sells an incident management platform that includes status pages, so we compete with Atlassian here and have a stake in this comparison. We've tried to be useful anyway: every Atlassian price below comes from Atlassian's own pages, other vendors' figures are dated and attributed, and there's a section on when Statuspage is the better choice.
What is Atlassian Statuspage?
Atlassian Statuspage is a hosted service for publishing the status of your systems: which components are working, which are degraded, what incidents are open, and what maintenance is planned. Subscribers get notified by email, SMS, webhook, Slack or Microsoft Teams, depending on the plan. It started as the independent product Statuspage.io and became part of Atlassian in 2016.
Statuspage comes in three page types, each with its own pricing:
Page type | Audience | Typical use |
|---|---|---|
Public page | Anyone: customers, prospects, partners | The status page your customers bookmark, usually at |
Private page | Employees, behind login | Status of internal tools, VPN, HR systems, CI pipelines |
Audience-specific page | Different groups of logged-in users see different components | B2B platforms where each customer sees only the services they buy |
Every plan includes the same core feature set, according to Atlassian's pricing FAQ: incidents, components and component groups, scheduled maintenances, incident templates, page analytics, basic customization, REST API access, third-party components, automation and chat integrations, a status embed, an activity log and a Twitter integration. What the paid plans add is mainly capacity (subscribers, team members, metrics) and notification channels, plus access controls on the higher tiers.
Statuspage doesn't monitor anything itself. It shows what you, or a connected tool, tell it. That's why it's almost always paired with an alerting and on-call tool, and why the question of which tool feeds it matters so much in an Opsgenie migration.
Component statuses: what "partial outage" actually means
A Statuspage page is built from components: the parts of your service customers care about, such as API, dashboard, payments or EU region. Each component has one of five statuses. Picking the right one is the most common judgment call during an incident, because customers read the color before they read the words.
Status | Meaning | Example | Typical internal severity |
|---|---|---|---|
Operational | Working normally | — | — |
Degraded performance | Working, but slower than normal or impaired in a minor way | API latency doubled; pages load but slowly | SEV3, sometimes SEV2 |
Partial outage | Completely broken for a subset of customers, or one part of the component is down | Logins fail for EU users only; exports fail but the dashboard works | SEV2 |
Major outage | Completely unavailable for all, or nearly all, customers | The whole API returns errors | SEV1 |
Under maintenance | Planned work in progress | Database upgrade during a scheduled window | — (planned) |
The distinction customers notice most is degraded versus partial. Degraded means everyone can still use it, just badly. Partial means some people can't use it at all. If even one customer segment is fully blocked, it's a partial outage, even when your overall error rate looks small. A major outage on a core component is usually a major incident internally, with a fixed update cadence on the status page; incident communication best practices covers how often to post and what to say.
Incidents on the page move through their own states, separate from component status: Investigating, Identified, Monitoring and Resolved. Scheduled maintenance has its own lifecycle too. Mapping both to your internal incident severity levels in advance saves an argument during every incident; the incident communication templates guide has ready-made wording for each state.
Atlassian Statuspage features
Atlassian groups Statuspage's features into four areas on its features page: core features, notifications, uptime and performance, and customization. The first three are largely available on every plan; customization and some notification channels depend on the tier.
Core features
Every plan, including Free, comes with the same core set:
Incidents with updates, incident templates for common scenarios, and a public incident history.
Components and component groups, each with its own status, so customers see exactly which part of the service is affected.
Scheduled maintenance, announced in advance and shown on the page during the window. (Your monitoring still needs its own maintenance window and alert suppression; Statuspage doesn't silence alerts.)
Third-party components, which show the status of vendors you depend on, such as your cloud provider or payment processor.
Integrations and automation: a REST API, chat integrations, automation integrations with alerting tools, a status embed for your own site or app, and a Twitter integration.
Page analytics and an activity log of who changed what.
Notifications
Subscribers can be notified by email on every plan. Free also includes Slack and Microsoft Teams notifications. SMS and webhook notifications start at the Startup plan. Notifications are unlimited on all plans; what changes by tier is the channels and the number of subscribers.
Uptime and performance
Statuspage can display historical uptime for each component (the Uptime Showcase) and live system data as charts (Public Metrics), fed from monitoring tools such as Datadog or New Relic. The number of metrics you can show is capped by plan. Statuspage doesn't run uptime checks itself: what it shows comes from a person, the API or a connected monitoring tool.
Customization
Pages can be branded with your logo and colors, served from a custom domain, and on higher tiers customized with your own HTML, CSS and JavaScript.
What each plan unlocks
Capacity, notification and SSO figures below are from Atlassian's pricing page, checked 26 October 2026. Customization and component-subscription gates are as reported in Hyperping's Statuspage pricing breakdown (July 2026); confirm them with Atlassian before you buy.
Plan | Subscribers | Team members | Metrics | Notifications | Unlocks |
|---|---|---|---|---|---|
Free | 100 | 2 | 2 | Email, Slack, Microsoft Teams | 25 components, REST API |
Hobby | 250 | 5 | 5 | Custom domain, basic customization | |
Startup | 1,000 | 10 | 10 | Email, SMS, webhook | Custom CSS; SSO for team members through Atlassian Guard at no extra charge |
Business | 5,000 | 25 | 25 | Email, SMS, webhook | Full HTML, CSS and JavaScript customization; component subscriptions |
Enterprise | 25,000 | 50 | 50 | Email, SMS, webhook | Highest limits; purchase orders and invoicing |
Three gates drive most upgrades:
Team members. A team member is anyone who can log in and update the page. On Hobby, only five people can post an update, so a large on-call rotation can end up waiting for the one person with access.
SMS and webhooks start at Startup ($99). Hobby sends email only.
Full design control and component subscriptions start at Business. Component subscriptions let customers follow only the parts of your service they use, which matters for B2B products with many components.
Atlassian Statuspage pricing in 2026
Statuspage is priced per page type, then by plan. There's no per-user charge for the people reading the page; the main driver of cost is how many subscribers you notify.
Page type | Plans and monthly price | Source and date |
|---|---|---|
Public | Free $0 (100 subscribers) · Hobby $29 (250) · Startup $99 (1,000) · Business $300 (5,000) · Enterprise $1,499 (25,000) | Atlassian pricing page, checked 26 October 2026 |
Private (login-protected, for employees) | Starter $79 (50 users) · Growth $249 (300) · Corporate $599 (1,000) · Enterprise $1,499+ (5,000+) | As reported by Hyperping (July 2026) and All Quiet (September 2026); Atlassian's private tab didn't load for us, so confirm before you buy |
Audience-specific | From $300/month for 500 users, 10 groups and 25 team members; each further tier adds a fixed amount (Hyperping reports $200, then $100, then $50 per tier as volume grows) | Base price: Atlassian, 26 October 2026; tier steps: Hyperping, July 2026 |
Public and private pages are separate subscriptions. A company that wants a customer page and an internal page pays both: a Startup public page plus a Growth private page, for example, comes to $348 a month before any alerting or monitoring tool.
Prices have moved recently. The public Business plan is listed at $300 a month as of 26 October 2026. Several comparison articles and review sites published in September 2026 still show $399, so check the date on any Statuspage price you read, including this one.
What actually pushes the price up:
Subscriber count. The tiers step at 100, 250, 1,000, 5,000 and 25,000 subscribers. A B2B company whose customers subscribe their whole team can cross a tier quickly.
More than one audience. Public and private pages are separate subscriptions. A company that wants a customer page and an internal page pays for both.
Notification channels and SSO. Needing SMS, webhooks or SSO moves you off Hobby regardless of subscriber count.
Notifications themselves are unlimited on every plan, and SSL is included at no extra cost.
How to keep your Statuspage bill down
If you're staying on Statuspage, five choices make the biggest difference:
Clean the subscriber list every quarter. Tiers are set by subscriber count, so bounced addresses, former customers and duplicate team inboxes can push you up a tier for nothing.
Check why you're on your current tier. If you moved to Business only for custom CSS, compare that against the $201 a month difference from Startup. A custom domain is already available on Hobby.
Group components instead of buying audience-specific pages. Component groups on a standard public page often cover what teams first try to solve with the $300-a-month audience-specific product.
Don't run a private page you rarely update. If your internal page sees one incident a quarter, an internal channel or the status of your incident tool may be enough.
Ask about annual billing. It isn't self-serve; Atlassian sets it up through support with a signed order form, but it can simplify procurement.
What users say about Atlassian Statuspage
Review sites tell a consistent story: people trust the product and question the price. Summarized from reviews on G2, TrustRadius and GetApp, reviewed for this article in October 2026:
Theme | What reviewers say |
|---|---|
Reliability and ease of use | The most common praise. Reviewers describe it as dependable and simple to operate during an incident, which is exactly when it matters. |
Recognition | Customers already know how to read a Statuspage page, which some reviewers see as part of the value. |
Price that grows with subscribers | The most common complaint. Because tiers follow subscriber count, the bill rises as the customer base grows, while the product stays the same. |
Expensive for small teams | Smaller SaaS companies describe the free plan as too limited for production and the paid plans as hard to justify for a communication-only tool. |
Features behind higher tiers | Automation, deeper integrations and design control often require Startup or Business. |
Atlassian account management | Every team member needs an Atlassian account, which adds administration for teams that don't otherwise use Atlassian products. |
No built-in monitoring | Statuspage can't detect an outage on its own, so another tool has to tell it. |
On GetApp, Statuspage's features are rated 4.4 out of 5, and 80% of reviewers say they would recommend it (as shown in October 2026). The balanced reading: nobody calls it a bad product; the friction is paying a premium for a narrow job, at a price that rises with company size rather than with what you use.
The two-product problem for Opsgenie migrators
Atlassian's recommended home for Opsgenie customers is Jira Service Management, which is now sold as part of Atlassian's Service Collection together with Customer Service Management, Assets and Rovo. JSM includes alerts, on-call schedules and escalation, even on its Free plan for three agents. On paper, that covers what Opsgenie did.
The status page is where the paths split. On the Service Collection pricing page, checked 26 October 2026, status pages are listed only under the Enterprise plan: branded public and private status pages appear in Enterprise's feature list and nowhere in Standard or Premium. Atlassian announced native JSM status pages in February 2026 and expanded them in July 2026, and in the July post an Atlassian team member confirms the feature remains Enterprise-only. The plan gate hasn't moved since.
JSM plan (Service Collection) | Price per agent/month (checked 26 Oct 2026) | Alerts and on-call | Native status pages |
|---|---|---|---|
Free | $0, up to 3 agents | Yes | No |
Standard | $21.50 | Yes | No |
Premium | $55.28 | Yes, plus AIOps alert grouping and heartbeat monitoring | No |
Enterprise | Not published; annual only, contact sales | Yes | Yes |
The per-agent prices above are what Atlassian's calculator shows at its default team size. Smaller teams pay a higher per-agent rate: an independent analysis in September 2026 found $25 (Standard) and $57.30 (Premium) per agent at 15 agents.
So a team on Standard or Premium that wants a status page has two options:
Upgrade the whole organization to Enterprise, an annual plan with no public price, for every agent, to unlock one feature.
Keep Standard or Premium and buy Atlassian Statuspage separately. This is what most teams do. Atlassian's free Statuspage for Jira Service Management app connects the two, but its Marketplace listing makes clear it works with an existing, separately paid Statuspage subscription; it shows Statuspage data inside JSM rather than replacing the subscription.
Either way, "we moved off Opsgenie to Atlassian" usually means two subscriptions, two admin consoles and two places where incident updates have to be kept in sync. For teams that relied on Opsgenie's Statuspage integration, it's worth pricing this out before committing; see our Opsgenie end-of-life guide for the full migration timeline.
What the Opsgenie migration really costs at four team sizes
To compare like with like, we priced the same job at four team sizes: on-call scheduling, alerting and escalation, plus a public status page. Every responder is counted as a paid seat, because in JSM anyone who works on incidents needs an agent license.
The assumptions behind each bar:
JSM path: Premium at $55.28 per agent (the calculator's default rate; small teams pay more per agent), plus a Statuspage public plan sized to likely subscribers: Hobby up to 20 users, Startup at 50, Business at 100. Statuspage's tier depends on your subscriber count, not your headcount, so yours could sit one tier either side.
ITOC360 Advanced: $18 per user per month, with on-call, alerting, escalation and status pages in the same plan.
All Quiet Pro: $9.99 per user per month as published by All Quiet, also including status pages.
What none of the bars include: monitoring. Statuspage, JSM, ITOC360 and All Quiet all react to signals from monitoring tools; none of the three stacks above replaces Prometheus, Datadog, Zabbix or an uptime checker.If you don't already run monitoring, add its cost to every option, or consider a tool with built-in uptime checks. For a standalone status page, the realistic stack is therefore three tools: monitoring, alerting and on-call, and the status page itself.
Two honest readings of this chart. First, the JSM path costs roughly three times a single-platform plan at every size, and most of that gap is the JSM per-agent price, not Statuspage. Second, ITOC360 isn't the cheapest single-platform option; tools like All Quiet price lower. The decision between single-platform tools comes down to what else you need, such as alert correlation, integrations, ChatOps and role management, not the status page alone.
When Atlassian Statuspage is the right choice
The cost comparison above isn't the whole story. Statuspage is the most established product in its category, and for some teams it's the right tool to keep:
You need full ITSM, not just incident response. JSM Premium includes change management with approvals, asset and configuration management, and a service catalog. If your organization runs ITIL processes, JSM is doing a bigger job than an on-call tool, and paying for Statuspage alongside it can be reasonable.
You need audience-specific pages. Showing each B2B customer only the components they buy is a Statuspage strength that many single-platform tools don't match.
Your status page is owned by a separate team. If support or communications owns customer updates and engineering owns on-call, two products with clear ownership can work well.
You already pay for Statuspage and it works. Leaving Opsgenie doesn't force you to move your status page. Statuspage keeps working with or without JSM.
Your subscriber list is large and your brand matters. Statuspage is widely recognized, and customers know how to read it.
The question this guide answers is narrower: whether moving from Opsgenie to JSM removes the need for a second product. For JSM Standard and Premium customers, it doesn't. Whether that second product is worth its cost is a decision each team can make with the numbers above.
Atlassian Statuspage alternatives
Alternatives fall into two groups, and the right group depends on what you're replacing. If you only need a status page, a standalone tool is usually cheapest. If you're replacing Opsgenie too, a platform that includes on-call, alerting and status pages in one plan avoids the two-product problem entirely.
Platforms with on-call, alerting and status pages in one plan
Tool | What's included | Pricing model | Worth knowing |
|---|---|---|---|
ITOC360 | On-call, AI alert correlation, escalation, incident response, ChatOps and status pages | Per user; status pages from the Advanced plan ($18/user/month) | 50+ monitoring integrations; Opsgenie migration support on ITOC360 vs Opsgenie |
All Quiet | On-call, alerting, incident response, status pages | Per user; status pages included in Pro ($9.99/user/month, as published) | Europe-based; positions itself on price |
Better Stack | Uptime monitoring, on-call, status pages | Per responder plus monitoring usage | Strong if you also want built-in uptime checks |
incident.io, Rootly, FireHydrant | Incident response with status pages | Per user, plan-dependent | Incident-first tools; on-call depth varies |
PagerDuty | On-call, alerting, incident response; status pages as a separate product or add-on | Per user, plus status page pricing | Mature, but the two-product question applies here too |
Standalone status page tools
Tool | Pricing model | Worth knowing |
|---|---|---|
Instatus | Flat monthly plans | Simple and fast to set up |
openstatus | Flat pricing, unlimited subscribers; open source | Includes monitoring from many regions |
Hyperping | Flat plans with monitoring included | Aimed at small teams that want monitoring and a page together |
StatusPage.me, Pulsetic | Flat plans without per-subscriber billing | Budget options for smaller audiences |
Status.io | Tiered plans | Long-established; public and private pages |
If your requirement is a status page and nothing else, a standalone tool will almost always cost less than any platform. If you're also choosing what replaces Opsgenie, compare the platforms in the first table with the best incident management software in 2026, and read the Opsgenie alternatives guide for the migration checklist.
Frequently asked questions
What is Atlassian Statuspage?
Atlassian Statuspage is a hosted service for publishing the status of your systems, open incidents and scheduled maintenance to customers or employees, with notifications by email, SMS, webhook, Slack or Microsoft Teams depending on the plan.
What does "partial outage" mean on Statuspage?
A partial outage means a component is completely broken for a subset of customers, or one part of it is down, while others can still use it. It sits between degraded performance, where everyone can use the component but it's slow, and major outage, where it's unavailable for everyone.
Does Jira Service Management include status pages?
Only on the Enterprise plan. On Atlassian's Service Collection pricing page, checked 26 October 2026, status pages appear in the Enterprise feature list and not in Free, Standard or Premium. Teams on those plans need a separate Atlassian Statuspage subscription.
Do I need Statuspage if I migrate from Opsgenie to JSM?
If you want a status page and you're on JSM Standard or Premium, yes. JSM covers alerting and on-call, but native status pages are Enterprise-only. Atlassian's free connector app links JSM to an existing Statuspage subscription; it doesn't replace it.
When does Opsgenie shut down?
Atlassian stopped selling new Opsgenie subscriptions on 4 June 2025 and will shut the product down on 5 April 2027, according to its Opsgenie migration page. Our Opsgenie end-of-life guide covers the timeline and what to migrate first.
What are the best Atlassian Statuspage alternatives?
For a status page alone, flat-priced tools such as Instatus, openstatus and Hyperping. If you're also replacing Opsgenie, platforms that include on-call, alerting and status pages in one plan, such as ITOC360 and All Quiet, avoid paying for two products.
Sources checked for this article
Atlassian Statuspage pricing, checked 26 October 2026: public plan prices and limits, audience-specific base price, core features, SSO and notification FAQs.
Atlassian Statuspage features, checked 26 October 2026: the four feature areas.
Atlassian Service Collection (Jira Service Management) pricing, checked 26 October 2026: Standard $21.50 and Premium $55.28 per agent per month at the calculator's default team size; status pages listed under Enterprise only; agent definitions.
Atlassian: Migrate from Opsgenie: end of sale 4 June 2025, shutdown 5 April 2027.
Atlassian Community: Introducing status pages in JSM (16 February 2026) and What's new for status pages in JSM (2 July 2026).
Statuspage for Jira Service Management, Atlassian Marketplace.
Hyperping: Statuspage.io pricing (last updated 12 September 2026, figures as of July 2026): private and audience-specific tier detail, feature gates.
All Quiet's published pricing (25 September 2026): Pro plan price and private page tiers.
Reviews: G2, TrustRadius, GetApp.