PagerDuty Status Page Pricing: What 1,000 Subscribers Cost

A PagerDuty status page costs from $89 a month per 1,000 subscribers, and the Premium tier costs from $599 for the same 1,000. It is an add-on on both the Professional and Business plans rather than something included with your seats, so it lands on top of the $21 or $41 you already pay per user. The part worth knowing before you approve the quote: we read all fourteen rows of PagerDuty's own comparison between the two status page products, and they differ on exactly three. Every one of those three is a way of restricting who can see the page. The other eleven features are identical.

Status pages get bought late. Somebody asks why customers are emailing support during an outage instead of reading a page, a quote appears, and the number looks small next to the platform subscription it sits under. Then it renews at a subscriber count nobody predicted. This is what PagerDuty actually charges, checked against the vendor's own pricing document in September 2026, with the arithmetic shown so you can check it yourself.

How much does a PagerDuty status page cost?

From $89 a month per 1,000 subscribers for the standard product, and from $599 a month per 1,000 for Premium. Both prices are printed as "From" and "Starting at" on the vendor page, which means they are floors rather than fixed unit prices, so a real quote can come back higher. Status pages appear in the "Available Add-Ons" list on both Professional and Business, alongside AIOps, stakeholder licences, Live Call Routing and PagerDuty Advance.

That $1,068 a year figure is worth holding on to, because independent write-ups of PagerDuty's pricing quote the subscriber pack at exactly $1,068 annually. Twelve months at $89 is $1,068, so the two sources reconcile and the $89 can be treated as solid rather than as a marketing floor that nobody actually pays.

For scale against the thing it sits on: at $89 a month, a status page costs more than four Professional seats at $21 each, which come to $84. Most teams do not think of a status page as costing more than four engineers' access to the incident tool, but on this price list it does.

What is the difference between PagerDuty Status Pages and Premium Status Pages?

Three features, and they are all the same idea expressed three ways. We read the vendor's fourteen-row comparison table directly from the markup rather than from a summary, because most of its cells contain an icon rather than any text and are easy to misread. Standard carries eleven of the fourteen. Premium carries all fourteen.

So the $510 a month difference, $6,120 a year on a single thousand subscribers, buys access control. Private pages behind your SSO provider, pages that show different content to different audiences, and the ability to run public and private subscribers together. Nothing about the page itself gets better. The branding, the uptime metrics, the postmortems, the maintenance windows and the Slack subscriptions are all on the cheaper product.

That makes the buying decision unusually clean for once. If you need to show one public page to everyone, Premium is worth nothing to you at any subscriber count. If you have a contractual obligation to show enterprise customers a private view of their own services, Premium is the only product on this price list that does it, and $6,120 a year is what that obligation costs.

Is a status page included in a PagerDuty plan?

No, not on Professional or Business. Both plans list status pages under "Available Add-Ons", which is PagerDuty's own wording for things charged separately. Some third-party write-ups state that Professional includes 250 status page subscribers and Business 500. PagerDuty's own pricing page does not state any included subscriber count anywhere, so that claim is not something we will repeat as fact. If an included allowance matters to your budget, get it in writing from a sales rep rather than from a comparison blog, ours included.

How does that compare with other status page pricing?

Vendors meter status pages differently, which makes a straight comparison harder than it should be. Only some publish a per-subscriber rate at all. Where they do, the spread is wide.

Priced per subscriber, PagerDuty's standard page is 8.9 times Pulsetic's published rate and the Premium tier is 59.9 times it. That is not automatically damning, because you are buying a status page attached to a mature incident platform rather than a standalone product, and the integration has real value if your incidents already live in PagerDuty. It is worth knowing the multiple before you decide the integration is worth it, though, because 8.9x is a larger premium than most people would guess for the convenience.

Atlassian Statuspage is the other big name here, and it meters subscribers too, through plan tiers rather than a unit rate. Its public plans run $0, $29, $99, $399 and $1,499 a month, and its audience-specific plans start at $79. The pattern across all three vendors is the same: the thing that moves your status page bill is how many people subscribe to it, not how many services you display. We wrote up the whole market in our status page pricing breakdown.

Why do status pages charge per subscriber at all?

Because subscribers are the cost driver. A status page that nobody watches is a static web page. A status page with 40,000 subscribers is an email and SMS delivery system that has to fan out a message within seconds of an incident being declared, at exactly the moment your own infrastructure is having a bad day. Vendors meter the thing that costs them money to run.

The practical consequence for a buyer is that this line grows on a curve you do not control. Monitor counts and seat counts grow because somebody decides to add one. Status page subscribers grow because your product succeeded and customers opted in. A page that costs $89 a month at launch costs $445 at 5,000 subscribers on the same rate, and nobody filed a ticket to make that happen. If this is one line on a SaaS bill that has been quietly compounding for a couple of years, it is usually worth putting the whole subscription list through a read-only review of cloud and SaaS spend before renewal season rather than after it.

Do you need a status page at all?

More teams buy one than use one well. When we fetched and scored 40 live status pages from well known companies, only 12 of them published any uptime history at all, and the average page scored 2.3 out of 4 on basic measures like machine-readable status, an RSS feed and component detail. Five of the forty rendered nothing without JavaScript, which means they were invisible to a chunk of the tooling that tries to read them automatically. The full breakdown is in our census of 40 real status pages.

The reason that matters for a pricing decision is simple. If the industry norm is a page with a few coloured dots and no history, you are choosing between a $599 tier, an $89 tier and a page bundled into a monitoring plan for a job that most companies do to a fairly basic standard. Paying premium money for audience segmentation you will never configure is a common and avoidable mistake.

What this costs alongside the rest of PagerDuty

Status pages are one line on a bill that is mostly per-person. A ten person team on Professional pays $210 a month for seats at the annual rate, which is $2,520 a year, and the status page adds $1,068 on top of that for the first thousand subscribers. Stakeholder licences, if executives want read-only visibility, start at $150 a month per 50 people. None of that includes the monitoring that finds the outage in the first place, because PagerDuty routes alerts rather than generating them. We put every plan, every add-on rate and the arithmetic in one place in our PagerDuty pricing breakdown, including the sharpest edge on the price list: the free plan holds five users, so the sixth person costs $1,512 in year one rather than $252.

If what you need is a branded status page because customers ask where to look during an outage, and something that actually runs the checks, that is a different purchase from an incident response platform. Our own plans put a branded status page in every tier and price per monitor rather than per person, so the page does not arrive as a separate line item and subscribers are not a meter. If you also run a genuine on-call rota with escalation across squads, keep PagerDuty for that job and do not let a status page quote decide it.