What each week held
Withheld: something was read in 1 week of the last 12. A series needs at least 2 to say anything a single reading does not.
What it declares
- Public status pages
- Private/authenticated status pages
- Audience-specific pages
- SSO via Atlassian Guard
- Custom CSS/HTML/JS branding
- Email/SMS/Webhook notifications
- Jira/JSM automation integration
- API access for incident management
As the company’s own pages describe it. Forge did not test any of these.
What users raised
- High cost for MSPs billing per client
- Expensive for a single status page
- Audience-specific add-on pricing ($300/mo) seen as costly
- Perceived slow feature development since Atlassian acquisition
- Not a monitoring tool, only a display layer
Themes people raised in public. A complaint is somebody’s opinion, not a measurement of the product.
Everything on record
6 observed claims. Newest first; the tag on each row is what kind of claim you are reading.
- PRODUCTFACTSep 30, 2026
Statuspage deprecated old API keys and discontinued support for sending api_key in query parameters as of May 15, 2026, requiring integrations to send the key in the request header instead.
Affects any customer with existing API integrations, requiring a required migration to header-based auth.
community.atlassian.com/forums/discussion/3226055/upcoming-changes-to-statuspage-api-keys-action-required-by-may-15-2026 - PRODUCTFACTSep 30, 2026
Atlassian shipped a new 'Send update to Statuspage' Jira Automation action allowing automatic posting of status updates (e.g., 'Investigating' on Sev1 trigger, 'Resolved' on close) without manual steps, rolling out to all instances.
Affects JSM/Statuspage joint customers by reducing manual incident-update work; a feature launch in the entity's own product area.
community.atlassian.com/forums/Jira-Service-Management-articles/No-More-Incident-Communication-Stress-Introducing-Status-Pages/ba-p/3192703 - COMPLAINTUSER OPINIONSep 30, 2026
One independent commentary argues Statuspage has shifted from a simple outage page to an enterprise incident platform with pricing floors from $29 to $399/month plus $300/month audience-specific add-ons, calling this a burden for MSPs billing per client.
Signals a complaint theme among MSP/agency users about per-client cost scaling; first sighting, not yet at third-sighting threshold.
provenstartups.substack.com/p/atlassian-statuspage-is-taxing-msps - PRICINGFACTSep 30, 2026
Audience-specific pages use volume-based pricing with a base tier at $300/month (500 users, 10 groups, 25 team members, 30 metrics), with incremental increases of $200 (tiers 2-10), $100 (tiers 11-30), and $50 (tier 31+).
Affects multi-tenant or MSP-style customers who need segmented audiences, a frequently cited cost pain point.
support.atlassian.com/statuspage/docs/audience-specific-page-pricing/ - PRICINGFACTSep 30, 2026
A separate Private Pages pricing track exists: Starter ($79/mo), Growth ($249/mo), Corporate ($599/mo), and Enterprise ($1499/mo), for authenticated/internal status communication.
Affects enterprises evaluating private stakeholder-facing incident comms costs.
frontdeskreview.com/software/status-pages/atlassian-statuspage/ - PRICINGFACTSep 30, 2026
Statuspage's public-page pricing track is tiered as Free, Hobby ($29/mo), Startup ($99/mo), Business ($399/mo), and Enterprise ($1499/mo), each with published subscriber/team-member/metrics caps.
Establishes the baseline public pricing ladder buyers compare against alternatives.
frontdeskreview.com/software/status-pages/atlassian-statuspage/
A record of what Forge read in public about Statuspage — its own pages and what people wrote about it. Nothing here is a test of the product, a ranking or a score, and Forge has no relationship with this company.