|
By Danielle Leong
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.
|
By Jessica Abelson
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.
|
By Jessica Abelson
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 ).
|
By Jessica Abelson
Stay in the loop on key incidents with Auto-Watch and ensure data consistency at every milestone with Required Fields by Incident Type.
|
By David Celis
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.
|
By Danielle Leong
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.
|
By AJ
A DIY project to turn alerts into real-world signals using FireHydrant’s Hacker Mode.
|
By Jessica Abelson
Complex escalation policy? No problem. Alert Visualization shows exactly how your alert will route, before it ever fires.
|
By Robert Ross
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.
|
By Jessica Abelson
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.
|
By FireHydrant
All the latest updates from FireHydrant, including more powerful ways to use AI and Incident Management upgrades.
|
By FireHydrant
Get a quick walkthrough of the FireHydrant platform. FireHydrant is the all-in-one incident management platform that helps teams resolve incidents up to 90% faster — and prevent them from happening again. From flexible alerting and powerful automation to retros and AI insights, it brings clarity and control to every step of your response.
|
By FireHydrant
With FireHydrant's new Alert Visualization feature, you can simulate an alert and see exactly how it routes through your escalation policies — who gets notified, when, and how. Change the time, scrub through steps, and catch misconfigurations before they become wake-up calls.
|
By FireHydrant
Catch up on everything that's shipped this past month (there's a lot!), including.
|
By FireHydrant
Run smarter, more effective retros. Customize retros, collaborate in real time, and surface key insights faster with AI. The new experience empowers you to spend less time documenting and more time working together as a team to uncover the insights that lead to real improvements in your process, roles, and technology.
|
By FireHydrant
Meet the only all-in-one incident management platform that is there with you from the first alert until you learn from the retrospective.
|
By FireHydrant
Engineers are bombarded with pages left and right. There's uncertainty about how to escalate. A constant blur exists between what's urgent and what can wait. This never-ending ping-pong game takes a toll. Burnout creeps in, and your engineering culture has taken a nose dive before you know it.
|
By FireHydrant
In this episode we chat with veteran cloud architect Masaru Hoshi about the challenges of alert fatigue, the importance of effective alerting systems, and fostering ownership in software teams. Masaru shares insights from his 30-year career, emphasizing the need for balance, trust, and collaboration in incident response.
- March 2026 (1)
- November 2025 (1)
- October 2025 (3)
- September 2025 (1)
- August 2025 (1)
- July 2025 (7)
- June 2025 (1)
- May 2025 (1)
- April 2025 (2)
- March 2025 (5)
- February 2025 (2)
- January 2025 (3)
- December 2024 (4)
- September 2024 (1)
- August 2024 (1)
- July 2024 (2)
- May 2024 (2)
- March 2024 (3)
- February 2024 (4)
- January 2024 (1)
- December 2023 (3)
- November 2023 (3)
- October 2023 (6)
- September 2023 (3)
- August 2023 (4)
- July 2023 (4)
- June 2023 (5)
- May 2023 (6)
- April 2023 (4)
- March 2023 (6)
- February 2023 (2)
- January 2023 (3)
- December 2022 (3)
- November 2022 (3)
- October 2022 (3)
- September 2022 (1)
- August 2022 (4)
- July 2022 (2)
- June 2022 (5)
- May 2022 (4)
- April 2022 (5)
- March 2022 (4)
- February 2022 (4)
- January 2022 (2)
- December 2021 (1)
- November 2021 (1)
- October 2021 (3)
- September 2021 (6)
- August 2021 (3)
- July 2021 (1)
- June 2021 (1)
- May 2021 (7)
- April 2021 (3)
- March 2021 (4)
- February 2021 (4)
- January 2021 (4)
- December 2020 (2)
- November 2020 (2)
- October 2020 (7)
- September 2020 (5)
- August 2020 (2)
- July 2020 (6)
- June 2020 (6)
- May 2020 (1)
- April 2020 (4)
- March 2020 (2)
- January 2020 (3)
- November 2019 (1)
- October 2019 (2)
- September 2019 (2)
- August 2019 (2)
- July 2019 (1)
- June 2019 (3)
- May 2019 (7)
- April 2019 (2)
Utilize SRE best practices using FireHydrant’s incident response platform to organize, investigate, and remedy faster.
FireHydrant helps teams respond to service disruptions easily and effectively. By allowing teams to “rally the troops” with only a few clicks and assign incident roles to responders, responsibilities are quickly defined and allow people to focus on what matters: restoring service.
Organize, Investigate, Remedy and Prevent faster with FireHydrant:
- Teams: Fill out your SRE roles and assign members to instantly delegate responsibility in an incident. Assign who owns what components to get the right people on the job.
- Slack Integration: If you're using Slack, FireHydrant gets even better. Quickly open incidents, notify other channels, and assemble your team easily all without leaving Slack.
- The Service Catalog: Keep a catalog of your environments and the things running in them with our service catalog feature. Make it easy to quickly find all of the gears of your product.
- The Changelog: Fire's typically start when something changes. That's why we offer a one stop shop for you to log all of the change occuring in your stack.
- Incident Logs: While you're fighting a fire, FireHydrant will transparently keep track of changes and Slack chat in your incident log automatically. You can easily filter notes and chat as well.
- Post mortem: Easily access all prior incidents with fine grain filtering to help make actionable changes to keep your system robust.