2. 1. Market Size & Growth
| Market Segment | 2024–2025 Size | Projected | CAGR |
|---|---|---|---|
| Status Page as a Service | $1.26B (2024) | $4.12B by 2033 | 14.1% |
| Incident Management Software | $2.5–4.5B | $5.93–12.3B by 2031–2033 | 10.7–12.5% |
| IT Alerting Software | ~$2.69B (2025) | $5.2–6.0B by 2033–2035 | ~15% |
| Server Uptime Monitoring | $6.2B (2024) | $15.1B by 2033 | 10.7% |
| Website Monitoring Software | $1.675B (2025) | $3.15B by 2032 | 9.6% |
Cloud-based solutions hold 60% of status page market revenue. Asia-Pacific is the fastest-growing region at 15.2% CAGR. Growth drivers: cloud-native architectures, microservices expansion, and AI-powered analytics.
3. 2. Status Page Platforms
| Platform | Revenue / Funding | Pricing | Key Facts |
|---|---|---|---|
| Atlassian Statuspage | Acquired 2016 (undisclosed); part of $4.4B Atlassian | Free (100 subs) / $29–$1,499/mo | ~7.68% ITSM market share; Venmo, Reddit, Dropbox; 21-day outage Feb 2025 |
| Instatus | ~$480K ARR; Calm Company Fund backed | Lower than Atlassian | ~1,000 customers; Cairo-based founder; fast & simple |
| Oh Dear | $126.5K (2024, +26% YoY); bootstrapped | 15 EUR/mo for 5 pages | 1-person company (Belgium); all-in-one monitoring + status |
| SorryApp | Undisclosed | $99/mo (1K subs, 5 team members) | Multi-page collections; Slack/Teams integration |
| Hyperping | Undisclosed | Free / $24–$164/mo flat rate | No per-user fees; 30-sec checks from 18 locations |
| Hund | Undisclosed | $29/mo (20 components) | Full HTML/CSS customization; Terraform provider; 99.9% SLA |
| StatusCake | ~$580K/year (est.) | $20–$67/mo | Founded 2012 (UK); uptime + page speed + SSL + domain |
| IsDown | Undisclosed | Undisclosed | Status page aggregator — monitors 4,522+ vendor pages; internal focus |
The status page space is remarkably fragmented. Most players are small bootstrapped teams. The biggest story is Atlassian Statuspage’s 21-day critical outage in February 2025 — the irony of a status page going down for three weeks is not lost on the market, and it created an opening for alternatives.
4. 3. Incident Management Platforms
| Platform | Revenue | Funding / Valuation | Status |
|---|---|---|---|
| PagerDuty | $467.5M (FY2025) | Public (NYSE: PD); ~$1.13B market cap | Growth slowing (8.5% YoY); stock -84% from ATH |
| incident.io | $9M (2025) | $96.2M raised; $400M valuation | Slack-native; Netflix, OpenAI, Airbnb customers |
| Opsgenie (Atlassian) | Part of $4.4B Atlassian | Acquired for $295M (2018) | Sunsetting: no new sales June 2025, shutdown April 2027 |
| Squadcast | $10.9M (Oct 2024) | $10–19.5M raised | Acquired by SolarWinds (March 2025) |
| FireHydrant | Undisclosed | $32.5M+ raised | Acquired Blameless (Aug 2024); SRE-focused |
| Rootly | 400% revenue growth (2023) | $15.3M raised (Google Gradient, 8VC) | Canva, Nvidia, TripAdvisor; free tier |
| Blameless | $3.7M (2023, pre-acquisition) | $50.1M raised | Acquired by FireHydrant (August 2024) |
| StatusHero | $4M (2025) | $1.1M raised | Async check-ins + project status aggregation |
The incident management space is consolidating: FireHydrant acquired Blameless, SolarWinds acquired Squadcast, Atlassian is sunsetting Opsgenie. The survivors are the modern Slack-native tools (incident.io, Rootly) and the incumbent (PagerDuty) trying to defend with AI.
5. 4. Uptime Monitoring
| Platform | Revenue / Funding | Key Metrics |
|---|---|---|
| UptimeRobot | ~$21M/year (est.); acquired by Pale Fire Capital (2019) | 2.7M+ users, 7.57M+ monitors; 50 free monitors |
| Pingdom (SolarWinds) | Acquired for $103M (2014) | 500K customers at acquisition; 60+ global locations; $15+/mo |
| Better Stack | $3.4M (Sept 2025); $28.6M raised | 200K+ developers, 4K+ paying; Forbes Startup of the Year 2022 |
| Checkly | $561K (June 2024); $32.25M raised (Series B $20M) | 1K+ companies (Autodesk, 1Password); Playwright-based synthetic monitoring |
| Datadog Synthetics | Part of $3.21B trailing revenue | 51.82% DCM market share; Gartner Leader |
| New Relic Synthetics | $925.6M (FY2023); taken private for $6.5B | ~24% system admin market share; Gartner Leader |
| Freshping (Freshworks) | Part of $600M+ Freshworks | Free forever: 50 monitors, 1-min intervals, 5 status pages, 10 users |
| Updown.io | ~$192K; bootstrapped, ~6 people | Pay-as-you-go credits; ~0.6 EUR/mo per site |
UptimeRobot dominates the free/freemium space with 2.7 million users monitoring 7.57 million endpoints. Its massive free tier (50 monitors) creates an enormous adoption funnel. Meanwhile, the premium end is dominated by Datadog and New Relic bundling synthetics into broader observability platforms.
6. 5. Open Source Alternatives
| Project | GitHub Stars | Language | Key Features |
|---|---|---|---|
| Uptime Kuma | ~83,200 | Node.js | Self-hosted monitoring, 95+ notification channels, 20-sec intervals, Docker, MariaDB (v2.0) |
| Upptime | ~16,000+ | TypeScript | GitHub Actions-powered, zero-server, static status page generator |
| Cachet | ~14,000 | PHP/Laravel | Status page system, incident tracking, metrics, 10+ languages; being rebuilt with Vue.js/Tailwind |
| Gatus | ~9,500 | Go | Single binary, 10–30MB RAM, HTTP/TCP/ICMP/DNS/WS/SSH monitoring, 20+ alert providers |
| Statping-ng | ~7,000 | Go | Status page + monitoring, graphs, analytics, plugins |
| OneUptime | ~6,000+ | TypeScript | Full observability platform (replaces Datadog + PagerDuty + Statuspage); Apache 2.0 |
| cState | ~2,500 | Hugo/Go | Static status page, no database, Git-based |
| Vigil | ~1,800 | Rust | Microservices-focused, lightweight; created by Crisp.chat |
Uptime Kuma’s 83,200 stars make it one of the most popular self-hosted tools on all of GitHub. For context, that’s more stars than Grafana (66K) and approaching Prometheus (56K). There is no official hosted version — a massive market opportunity.
OneUptime is the most ambitious OSS project, aiming to replace the entire paid stack (monitoring + status + alerting + incident management + post-mortems) with a single Apache 2.0 platform. Gatus is gaining momentum with its single-binary Go approach — 10–30MB RAM makes it ideal for resource-constrained environments. Upptime’s zero-infrastructure approach (runs entirely on GitHub Actions) is uniquely clever.
7. 6. PagerDuty Deep Dive: The Incumbent Under Siege
Revenue History
| Fiscal Year | Revenue | YoY Growth |
|---|---|---|
| FY2021 | $213.6M | +28.4% |
| FY2022 | $281.4M | +31.8% |
| FY2023 | $370.8M | +31.8% |
| FY2024 | $430.7M | +16.2% |
| FY2025 | $467.5M | +8.5% |
Stock Performance
- IPO: April 2019 at $24/share; opened at $38.25 (~$2.82B market cap)
- All-time high: $57.37 (June 2019)
- Current: ~$6.25 (February 2026)
- Current market cap: ~$1.13B
- Decline from ATH: -84% stock price; -60% from IPO market cap
Customer Metrics
- ~34,000 total customers
- 804 customers at $100K+ ARR
- 58 customers at $1M+ ARR
- ~50% Fortune 500 penetration; ~70% Fortune 100
Acquisitions
- Rundeck (2020): $100M — DevOps automation
- Catalytic (2022): Undisclosed — no-code workflow automation
- Jeli (2023): Undisclosed — incident analysis/post-mortems
AI Bet (Operations Cloud, 2025)
- Shift Agent: Automates on-call PTO/vacation conflicts
- Insights Agent: Answers questions about past incidents, recommends improvements
- AI Orchestrations: ML-trained on historical events
- Claims AI saves an average of 4.87 hours per incident
Competition Pressure
PagerDuty faces pressure from every direction:
- From below: incident.io, Rootly (modern UX, Slack-native, faster deployment)
- From above: Atlassian bundling incident management into JSM
- From adjacent: Datadog, Grafana expanding into alerting and incident management
- From open source: Uptime Kuma (83K stars), OneUptime offering free alternatives
8. 7. incident.io: The Slack-Native Challenger
Funding & Valuation
| Round | Amount | Date | Lead |
|---|---|---|---|
| Seed | $5.5M | September 2021 | — |
| Series A | $28.7M | July 2022 | Index Ventures |
| Series B | $62M | April 2025 | Insight Partners |
- Total raised: $96.2M from 53 investors
- Valuation: $400M (Series B)
- Revenue: $9M (2025) — 44x revenue multiple reflects growth expectations
- Incidents processed: 250,000+
- Teams: 1,500+
- Customers: Netflix, OpenAI, Airbnb, Etsy, Intercom, Skyscanner
How They Differentiated from PagerDuty
- Slack-native architecture: The entire incident lifecycle lives in Slack/Teams — no context-switching to a separate web app
- Speed to value: Teams deploy in days vs. weeks for PagerDuty
- Modern UX: Built from scratch vs. PagerDuty’s 15+ years of accumulated UI debt
- Time savings: Over 100 incidents/year, saves 1,500+ minutes (25+ hours) in coordination
- Transparent pricing: $19–$25/user/month vs. PagerDuty’s opaque enterprise pricing
- Direct engineering access: Shared Slack channels; bug fixes in hours, features in days
Origin Story
Built by former Monzo engineers frustrated with fragmented legacy tools. The founding insight: incident management should happen where teams already work (Slack), not in a separate tool. Teams like Intercom migrated from PagerDuty + Atlassian Statuspage to incident.io in weeks.
Pricing
- Team: $19/user/mo (+$10/user/mo for on-call)
- Pro: $25/user/mo (+$20/user/mo for on-call)
- Enterprise: ~$50/user/mo (unlimited status pages, Slack Enterprise Grid)
9. 8. Better Stack: The Unified Platform Play
Better Stack’s thesis: monitoring, status pages, logging, and incident management should be one product. This contrasts with the fragmented stack of Pingdom + Statuspage + PagerDuty + Datadog. Positioning: “30x cheaper than Datadog.”
| Metric | Data |
|---|---|
| Revenue | $3.4M (September 2025) |
| Total Funding | $28.6M (Series A-II: $10M, Jan 2024, led by KAYA) |
| Team | 31 people |
| Developers | 200,000+ |
| Paying Customers | 4,000+ |
| Profitability | “Unintentionally profitable” since 2023; all VC still in the bank |
| ESOP Buyback | $5M+ (employee shares) |
| Notable Customers | Accenture, Time Magazine, Decathlon, ESET, Brave, Drata |
| Recognition | Forbes Startup of the Year 2022 |
- Founded: 2021 by Juraj Masar and Veronika Kolejakova (Czech Republic)
- Products: Uptime monitoring, status pages, on-call/incident management, logs/telemetry
- Free tier: 10 monitors
- Paid: $29/mo per responder + $21/mo per 50 additional monitors + $12/mo status page add-on
$3.4M revenue with 31 people and all VC still in the bank — this is one of the most capital-efficient companies in the space. The “unintentionally profitable” status while growing aggressively suggests a sustainable business model.
10. 9. The Atlassian Ecosystem & Opsgenie Sunset
Acquisition Timeline
- 2016: Acquired Statuspage (undisclosed; YC-backed, founded 2013)
- 2018: Acquired Opsgenie for $295M (~20x revenue)
- Ongoing: Integrated both into Jira Service Management
The Opsgenie Sunset
- June 4, 2025: No new Opsgenie sales
- April 5, 2027: Full shutdown
- Migration path: Jira Service Management (Operations features)
This is a classic platform bundling play: Atlassian is forcing Opsgenie customers into JSM Premium/Enterprise, which now includes advanced on-call, escalation policies, and unlimited SMS/phone alerts. But not all customers will stay with Atlassian — the Opsgenie sunset creates a window for incident.io, Rootly, Better Stack, and others to capture migrating customers.
Bundling Strategy
- Service Collection: New bundle rolling JSM + incident management + on-call
- JSM Premium/Enterprise: Now includes what was Opsgenie Enterprise
- Statuspage: Remains separate but tightly integrated with JSM
- Atlassian total FY2024 revenue: $4.4B (individual product revenue not disclosed)
11. 10. Key Acquisitions
| Year | Acquirer | Target | Price | Category |
|---|---|---|---|---|
| 2014 | SolarWinds | Pingdom | $103M | Uptime monitoring |
| 2016 | Atlassian | Statuspage | Undisclosed | Status pages |
| 2018 | Atlassian | Opsgenie | $295M | IT alerting / on-call |
| 2020 | PagerDuty | Rundeck | $100M | DevOps automation |
| 2022 | PagerDuty | Catalytic | Undisclosed | Workflow automation |
| 2023 | Francisco Partners + TPG | New Relic | $6.5B | Full-stack observability |
| 2023 | PagerDuty | Jeli | Undisclosed | Incident analysis |
| 2024 | FireHydrant | Blameless | Undisclosed | SRE / incident management |
| 2025 | SolarWinds | Squadcast | Undisclosed | Incident response |
Patterns: Atlassian pursued horizontal integration (status + alerting + ITSM). PagerDuty acquired for product depth (automation, post-mortems). SolarWinds is rebuilding its monitoring stack (Pingdom + Squadcast). Smaller players are consolidating to survive (FireHydrant + Blameless).
12. 11. Pricing Models
Free Tier / Freemium
| Platform | Free Tier |
|---|---|
| UptimeRobot | 50 monitors at 5-min intervals (personal/non-commercial only) |
| Freshping | 50 monitors, 1-min intervals, 5 status pages, 10 users (forever free) |
| Atlassian Statuspage | 100 subscribers, 25 components |
| Better Stack | 10 monitors |
| Hyperping | 5 monitors + 1 status page |
| Uptime Kuma | Fully free (self-hosted) |
| OneUptime | Open source (self-host free) |
Paid Pricing Models
- Per-monitor: Better Stack ($21/mo per 50), Updown.io (pay-per-credit)
- Per-subscriber: Atlassian Statuspage (tiered 250/1K/5K/25K subscribers)
- Per-user / per-responder: incident.io ($19–50/user/mo), Better Stack ($29/mo per responder), PagerDuty (per-user)
- Flat rate: Hyperping ($24–164/mo, no per-user), Hund ($29/mo per 20 components), Oh Dear (15 EUR/mo for 5 pages)
- Enterprise / custom: Atlassian $1,499+/mo, PagerDuty custom, incident.io ~$50/user/mo
Per-subscriber pricing for status pages is increasingly seen as outdated. Flat-rate models (Hyperping, Hund) are gaining traction as teams resist paying more just because more customers want to see their status page.
13. 12. The Status Page as Marketing
Trust & Transparency
Public status pages serve a dual purpose: operational communication and brand trust signal.
- Reduced support load: Customers self-check service status instead of opening tickets
- Sales tool: Historical uptime (99.99% over 12 months) is proof for prospects
- Brand signal: Having a public status page signals operational maturity
- Enterprise requirement: Many procurement processes now require a vendor status page
Public vs Private
- Public: Customer-facing, builds trust, reduces support (status.github.com, status.slack.com)
- Private/Internal: Tracking vendor dependencies and internal service health
- Audience-specific: Personalized pages showing only relevant services (Fly.io model)
Notable Examples
GitHub, Slack, Apple, Google, Fly.io — all maintain clean, component-level status pages with real-time updates and historical data. The status page has evolved from an operational necessity to a competitive differentiator that signals engineering excellence.
14. 13. Opportunities & Gaps
- Managed Uptime Kuma: 83K+ GitHub stars with no official hosted version. A managed hosting service for Uptime Kuma (similar to how Supabase hosts Postgres) could capture enormous demand. The signal is clear: 83K developers want this tool but not everyone wants to self-host.
- AI-native incident management: Current tools bolt AI on top of legacy architectures. A ground-up AI-native platform with autonomous SRE agents could differentiate. AI saves 4.87 hours/incident on average, but operational toil rose from 25% to 30% — the market is early.
- Status pages for AI products: AI infrastructure has unique monitoring needs — model latency, GPU availability, inference throughput, model drift, rate limits. No status page tool is designed for this. AI spending projected at $1.5T in 2025.
- Opsgenie migration window: Thousands of customers forced to migrate by April 2027. Not all will stay with Atlassian — a targeted migration tool + compelling alternative could capture significant share.
- Unified monitoring + status + incident (affordable): Better Stack is proving this thesis at $3.4M revenue. OneUptime attempts it in open source. The “Supabase of DevOps” — a single platform handling monitoring, status, on-call, incidents, and post-mortems at accessible pricing.
- Internal status page aggregator: IsDown monitors 4,522+ vendor pages for internal teams. As microservices and third-party dependencies multiply, internal dependency health dashboards become critical.
- Flat-rate status pages: Per-subscriber pricing is unpopular. Simple, predictable flat-rate pricing (Hyperping, Hund model) for status pages has room to grow.
- Status page + customer communication: Bridging the gap between operational status and customer communication (targeted notifications based on affected services, customer-specific impact assessments, proactive outreach).