Cutover vs PagerDuty

10-Q Financial Filing Analysis for PagerDuty (2026-08-27)

PagerDuty reported its Q2 fiscal 2027 results for the quarter ended July 31, 2026, delivering total revenue of $124.4 million, up 0.8% year-over-year. Operating income expanded significantly to $10.2 million from $3.6 million in Q2 fiscal 2026, driven by disciplined cost containment as total operating expenses dropped 6.6% to $94.2 million. GAAP net income attributable to PagerDuty reached $7.8 million ($4.7 million attributable to common stockholders), supported by sustained gross margins of 83.9% and strong operating cash flows of $81.2 million for the first half of the fiscal year. Concurrently, PagerDuty disclosed a strategic restructuring plan announced in August 2026 involving a 15% workforce reduction to enhance operational agility and realign resources around AI-driven operations and agentic workflows, resulting in estimated pre-tax charges of $5.5 million to $7.5 million primarily in Q3 fiscal 2027.

• Q2 fiscal 2027 revenue stood at $124.4 million with GAAP operating income of $10.2 million, up from $3.6 million in the prior-year period.
• Annual Recurring Revenue (ARR) reached $501.4 million with 15,506 total paid customers and a dollar-based net retention rate of 98%.
• Announced a corporate restructuring plan in August 2026 reducing headcount by ~15%, with expected restructuring charges between $5.5 million and $7.5 million.

See It, Approve It, Revoke It: Scoped OAuth for Public Apps

This blog post is part of PagerDuty’s ongoing series on how we’re helping customers navigate their journey towards autonomous operations. Read on to learn about...

OCI Monitoring Alarms: Six Readiness Traps That Cause Failures

The article explains six common reasons an Oracle Cloud Infrastructure (OCI) alarm can be created correctly yet fail to operate as an effective production control. It highlights mismatches between alarm evaluation interval and metric emission frequency; incorrect or overly narrow metric dimensions; pitfalls of absence alarms (including the need for groupBy); unproven notification paths and unconfirmed subscriptions; inadequate suppression and maintenance handling; and unreviewed trigger-delay settings. The piece provides validation checks, evidence sources (MQL query review, test records, notification receipt), and a ten-point readiness checklist to ensure alarms evaluate the right metric, at the right cadence, for the right resource and notify the right people with actionable guidance.

• The article identifies six failure modes for OCI alarms: metric interval mismatch, wrong dimensions, absence-alarm groupBy issues, unproven notification paths, uncontrolled maintenance/noise, and inappropriate trigger delay.
• Oracle documents that absent() returns 1 when a metric is absent for the entire interval and 0 when present; the default absence detection period is two hours and is configurable from 1 minute through 3 days.
• OCI supports alarm suppression for planned activity; suppression start and end times must each be within 90 days of the current time.