FireHydrant had 9 outages in the last 2 years totaling 26h 14m of downtime — averaging 0.4 incidents per month.
There were 9 FireHydrant outages since June 26, 2025 totaling 26h 14m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
Certain Retrospective Template fields ("sections" & "fields) are not respecting the PATCH behavior
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our systems have detected an availability or performance update with Slack and we're investigating the impact. We'll update with further information as it becomes available. Our web UI is not impacted and can be accessed at https://app.firehydrant.io/ You can also visit Slack's status page at https://status.slack.com/ for more information.
Slack Apps are displaying "We can't fully display this message" Per slack's status page: "We've identified the cause and are working on a fix for the Slack Apps displaying a "We can't fully display this message" error for apps that utilize drop-down options. We'll provide another update as soon as we have more news to share. We apologize for the trouble in the meantime."" Slack Status Page: https://slack-status.com/2025-08/54ca351d3ad76351 Our web UI is not impacted and can be accessed at https://app.firehydrant.io/ You can also visit Slack's status page at https://status.slack.com/ for more information.
Slack has identified the cause of the issue and is working on a fix. Per Slack status page: "We've identified the cause and are working on a fix for the Slack Apps displaying a "We can't fully display this message" error for apps that utilize drop-down options. We'll provide another update as soon as we have more news to share. We apologize for the trouble in the meantime." Slack status page: https://slack-status.com/2025-08/54ca351d3ad76351
Issue has been resolved, per Slack: "We've resolved the issue some users were experiencing related to Slack apps/integrations displaying an error message when selecting dropdown options. Affected users may need to refresh their client (Cmd/Ctrl + Shift + R) to capture the fix. We apologize for the trouble, but appreciate you bearing with us as we worked to get things back in order." FireHydrant's web UI was not impacted during this incident can be accessed at https://app.firehydrant.io/. Slack functionality is now restored, affected users may need to refresh their client (Cmd/Ctrl + Shift + R) to capture the fix.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
We are currently issuing a rollback of suspect code which should resolve the issue. Firehydrant remains operational for Slack, API, and other vectors.
We are currently issuing a rollback of suspect code which should resolve the issue. Firehydrant remains operational for Slack, API, and other vectors.
A fix has been implemented and we are monitoring the results.
We have deployed a solution and our team will continue to monitor for any regressions.
This incident has been resolved.
We are currently investigating this issue.
We are investigating reports of increased latency in runbook performance. Our engineering team is actively engaged in finding a root cause and remediation.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Slack has reopened their earlier incident regarding third party Slack integration connections. We are continuing to monitor the situation and the web UI remains fully functional. You can follow along on Slack's status page for more information: https://slack-status.com/2025-07/1ce16e396a56dcf8
We are continuing to monitor the situation and the web UI remains fully functional. You can follow along on Slack's status page for more information: https://slack-status.com/2025-07/1ce16e396a56dcf8
We are continuing to monitor the situation throughout the evening and the web UI remains fully functional. You can follow along on Slack's status page for more information: https://slack-status.com/2025-07/1ce16e396a56dcf8Jul
Slack has marked their incident as resolved and their status page indicates that dropdown menus for end users should now be fully functional. You can view more on Slack's status page: https://slack-status.com/2025-07/1ce16e396a56dcf8
This incident has been resolved.
Some GET requests from automations returned HTTP 401 despite the correct authorization setup due to a misconfigured traffic redirect. User interactions were not affected. This was resolved as of 10:55 PM UTC.
We are currently investigating this issue.
We have identified an issue with Signals escalation policies. New escalation targets created within the last 2 hours will see a lag in receiving alerts. We have identified the issue and are working through the backlog.
The issue has been identified and a fix is being implemented.
We have worked through the backlog of alerts and are monitoring performance
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
We have deployed a fix to MS Teams and are waiting to confirm that this solves the issue
This incident has been resolved.