Pagerduty Incident Increases Incident Types from 2 to 3 in Professional Plan, Enhancing Incident Management Capabilities
What happened
Between the Apr 1, 2025 and Jul 6, 2025 captures of Pagerduty's pricing page, Pulse recorded 2 changes: Professional plan increased predefined Incident Types from 2 to 3; Intune Support for Mobile App added to Enterprise plan. Pulse files it as a packaging change (limit increase, feature added) with an upward direction. Pulse's latest capture (Oct 19, 2026) lists Professional at $21, Business at $41, PagerDuty Advance for Incident Management at $415, Status Pages at $89 and Stakeholder License at $150.
Pagerduty's previous recorded change was "Pagerduty Incident Enhances Enterprise Plan with Full Chat Experience and Post-Incident Reviews, Expanding Features for Advanced Incident Management" (Q1 2025). Pagerduty has been tracked since 2024-10-01.
In the same window Atlassian and Grafana also changed their Business Operations pricing pages. Those moves are listed further down, and the Pulse Agent can compare them side by side.
- Professional · Limit+50%23
- Enterprise · FeatureAdded
BeforeNo Intune Support for Mobile App
AfterIntune Support for Mobile App
| Plan | Field | Before | After | Change |
|---|---|---|---|---|
| Professional | Limit | 2 | 3 | +50% |
| Enterprise | Feature | No Intune Support for Mobile App | Intune Support for Mobile App | Added |
Values as written on Pagerduty's public pricing page in the two captures Pulse compared; where the page states no number, the cells give the wording before and after.
Evidence
The two captures Pulse comparedFull-page captures of Pagerduty's pricing page (pagerduty.com) from Apr 1, 2025 and Jul 6, 2025; the change is marked on the page, where professional limit reads 2 and then 3.
Sign in to see the evidence
The two full-page captures with this change marked up are free with an account.
Pagerduty, the last 90 days
Full history- Oct 19, 2026packagingPagerduty Incident: AI Actions quota revealed, 1,000-100,000/year by tier
- Apr 13, 2026improvedPagerduty Incident expands integrations catalog from 700 to 750 across all plans
- Q2 2025improvedPagerduty Incident Increases Incident Types from 2 to 3 in Professional Plan, Enhancing Incident Management Capabilities · this change
- Q1 2025improvedPagerduty Incident Enhances Enterprise Plan with Full Chat Experience and Post-Incident Reviews, Expanding Features for Advanced Incident Management
Across Business Operations in the same window
All Business Operations changes- AtlassianJan 11Atlassian Opsgenie Confirms Opsgenie Discontinuation for New Customers, Introduces API Rate Limits for Standard and Enterprise Plans
- GrafanaJan 10Grafana Transforms Pro Plan to Pure Pay-As-You-Go Model Starting at $0, Renames All Plans
- AtlassianJan 11Atlassian Opsgenie Removes Chat Support from Essentials, Standard, and Enterprise Plans
- AtlassianJan 11Atlassian Jira Democratizes AI Features by Moving Rovo Search, Chat, and Agents from Premium to Standard Tier
- AtlassianJan 11Atlassian Jira Implements Price Increases for Standard and Premium Plans Amid Major Feature Overhaul and User Limit Expansions
Questions about this change
Did Pagerduty raise prices in July 2025?
No list-price increase was recorded between Apr 1, 2025 and Jul 6, 2025. The change Pulse detected was a packaging change: limit increase, feature added.
What changed on Pagerduty's pricing page between Apr 1, 2025 and Jul 6, 2025?
Professional limit: 2 → 3 (+50%); Enterprise feature: No Intune Support for Mobile App → Intune Support for Mobile App, added. Pulse compared the captures it took on Apr 1, 2025 and Jul 6, 2025; the before/after table above lists each item as written on the page.
How often does Pagerduty change its pricing?
Pulse recorded 1 other pricing-page change for Pagerduty in the 90 days before this one; the previous change was "Pagerduty Incident Enhances Enterprise Plan with Full Chat Experience and Post-Incident Reviews, Expanding Features for Advanced Incident Management" in Q1 2025; Pagerduty has been tracked since 2024-10-01.
