Operations | Monitoring | ITSM | DevOps | Cloud

On March 2, 2026 at 23:30:24 UTC, we experienced an issue where the Zoom AI scribe was unable to join calls, rendering Zoom meeting transcription unavailable for all users. On March 2, 2026 at 23:30:24 UTC, we experienced an issue where the Zoom AI scribe was unable to join calls, rendering Zoom meeting transcription unavailable for all users. The issue persisted from approximately February 28 through March 5, 2026.

The hidden blockers slowing down your incident response and how to remove them before they become reliability risks. Incidents rarely go wrong because of one big failure. Most of the time, it’s a handful of small, familiar mistakes that slow teams down, muddy communication, or create confusion in the heat of the moment. Fortunately, these mistakes are predictable and fixable.

All the things you may have missed that will make your incident management smarter, faster, and simply easier. We ship updates every week because we want you to get the most out of FireHydrant. But we also know it's hard to stay up to date and read every week's changelog (even though we know reading changelogs is the highlight of your week ).

Stay in the loop on key incidents with Auto-Watch and ensure data consistency at every milestone with Required Fields by Incident Type.

When coverage gets complicated, Schedule Rotations keeps it simple. On-call can get real messy, real fast. One minute you’ve got a neat little schedule for the two people rotating primary and secondary. Next thing you know, you’ve got engineers in three time zones, a new hire shadowing incidents, and your “simple” rotation has turned into a board game with no rules. So we fixed it.

Tips and best practices to help you get up and running with FireHydrant's Model Context Protocol integration. Manage incidents, alerts, and retrospectives directly through AI assistants like Claude or Cursor. Welcome to the FireHydrant MCP Server user guide! This guide will help you get up and running with FireHydrant's Model Context Protocol integration, allowing you to manage incidents, alerts, and retrospectives directly through AI assistants like Claude or Cursor.

A DIY project to turn alerts into real-world signals using FireHydrant’s Hacker Mode.

Complex escalation policy? No problem. Alert Visualization shows exactly how your alert will route, before it ever fires.

We’re going beyond notifications — and building the most powerful, flexible, and team-first on-call experience on the market. When we launched Signals, it was because alerting and on-call desperately needed a reset. Legacy tools hadn’t evolved with the way modern teams work — they were individual-centric, inflexible, and wildly overpriced. Signals changed that.

Opsgenie set a high bar. For years, it helped teams respond faster and stay on top of incidents with reliable alerting and on-call management. At FireHydrant, we’ve always admired how Opsgenie modeled incident data and structured its workflows — it was one of the best in the game. But as Atlassian sunsets Opsgenie and teams face the pressure to migrate, there’s a real decision to make: move into Jira Service Management, or find a new solution that fits your team’s needs and scale.