October 2025 Summaries

On October 20, 2025, FireHydrant experienced widespread service disruptions due to an AWS us-east-1 outage, impacting various integrations and functionalities like SMS, Voice, WhatsApp notifications, and authentication services. The incident was exacerbated when LaunchDarkly became unreachable, affecting feature flag evaluations and causing further disruptions in Signals UI and API access, multi-org SSO authentication, and runbook executions. Emergency mitigations included hardcoding critical feature flags and deploying patches to restore core functionalities, while automated paging and alert notifications remained operational. The incident was fully resolved by October 21, 2025, with no customer data compromised. In response, FireHydrant is implementing improvements such as defaulting feature flags to safe values, converting synchronous operations to asynchronous workflows, and enhancing third-party service monitoring to prevent future incidents.

FireHydrant has introduced several updates to enhance user experience and streamline incident management. Users can now Auto-Watch incidents for real-time notifications and define Milestone-Based Required Fields by Incident Type to ensure consistent data capture. The AI Scribe feature allows easy integration with Slack for incident discussions and automatically updates incident timelines with summaries. AI Summaries keep incident updates fresh by refreshing automatically with milestone changes, while automated audience-specific communications can be triggered based on AI Summary conditions in Runbooks. Post-incident retrospectives have been improved for better usability, allowing team-customized templates and export options. Additionally, Custom Roles and Permissions give teams control over incident management tasks while maintaining compliance and security standards.

FireHydrant has introduced two updates aimed at enhancing the management and communication of incident response. The first update, Auto-Watch Incidents, ensures stakeholders remain informed of critical incidents by automatically sending real-time email notifications for milestone and severity changes, and allowing users to subscribe to Saved Incident Views that align with their priorities. The second update, Milestone-Based Required Fields by Incident Type, enables teams to collect relevant data at appropriate times by specifying the necessary information for different types of incidents, allowing for tailored data collection without sacrificing consistency. These updates transform milestones from mere timeline markers into vital operational triggers, improving data governance and communication flow during incident management.