FireHydrant Outage History

FireHydrant is up right now

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.

Source: https://d5yfqjr6klqt.statuspage.io

Minor September 26, 2025

Google Meet Performance Degraded due to Upstream Concerns

Detected by Pingoru
Sep 26, 2025, 04:43 PM UTC
Resolved
Sep 26, 2025, 05:22 PM UTC
Duration
39m
Timeline · 3 updates
  1. investigating Sep 26, 2025, 04:43 PM UTC

    We are currently investigating this issue.

  2. identified Sep 26, 2025, 04:45 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Sep 26, 2025, 05:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 9, 2025

Retrospective Templates not saving correctly

Detected by Pingoru
Sep 09, 2025, 02:11 PM UTC
Resolved
Sep 09, 2025, 05:26 PM UTC
Duration
3h 15m
Timeline · 4 updates
  1. investigating Sep 09, 2025, 02:11 PM UTC

    We are currently investigating this issue.

  2. identified Sep 09, 2025, 04:02 PM UTC

    Certain Retrospective Template fields ("sections" & "fields) are not respecting the PATCH behavior

  3. monitoring Sep 09, 2025, 04:51 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Sep 09, 2025, 05:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 28, 2025

We've observed an availability or performance issue with Slack

Detected by Pingoru
Aug 28, 2025, 01:50 PM UTC
Resolved
Aug 28, 2025, 03:35 PM UTC
Duration
1h 45m
Timeline · 5 updates
  1. investigating Aug 28, 2025, 01:50 PM UTC

    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.

  2. investigating Aug 28, 2025, 01:57 PM UTC

    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.

  3. investigating Aug 28, 2025, 02:27 PM UTC

    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

  4. investigating Aug 28, 2025, 03:33 PM UTC

    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.

  5. resolved Aug 28, 2025, 03:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 31, 2025

Incident page unable to load with "__esModule" error

Detected by Pingoru
Jul 31, 2025, 07:00 PM UTC
Resolved
Jul 31, 2025, 07:18 PM UTC
Duration
18m
Timeline · 7 updates
  1. investigating Jul 31, 2025, 07:00 PM UTC

    We are currently investigating this issue.

  2. identified Jul 31, 2025, 07:00 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Jul 31, 2025, 07:02 PM UTC

    We are currently issuing a rollback of suspect code which should resolve the issue. Firehydrant remains operational for Slack, API, and other vectors.

  4. identified Jul 31, 2025, 07:03 PM UTC

    We are currently issuing a rollback of suspect code which should resolve the issue. Firehydrant remains operational for Slack, API, and other vectors.

  5. monitoring Jul 31, 2025, 07:05 PM UTC

    A fix has been implemented and we are monitoring the results.

  6. monitoring Jul 31, 2025, 07:06 PM UTC

    We have deployed a solution and our team will continue to monitor for any regressions.

  7. resolved Jul 31, 2025, 07:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 23, 2025

Increased latency on runbooks

Detected by Pingoru
Jul 23, 2025, 06:57 PM UTC
Resolved
Jul 23, 2025, 07:05 PM UTC
Duration
8m
Timeline · 4 updates
  1. investigating Jul 23, 2025, 06:57 PM UTC

    We are currently investigating this issue.

  2. investigating Jul 23, 2025, 06:57 PM UTC

    We are investigating reports of increased latency in runbook performance. Our engineering team is actively engaged in finding a root cause and remediation.

  3. identified Jul 23, 2025, 07:02 PM UTC

    The issue has been identified and a fix is being implemented.

  4. resolved Jul 23, 2025, 07:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 15, 2025

Third party Slack integrations experiencing connectivity issues

Detected by Pingoru
Jul 15, 2025, 07:09 PM UTC
Resolved
Jul 16, 2025, 02:09 PM UTC
Duration
19h
Affected: Slack
Timeline · 5 updates
  1. identified Jul 15, 2025, 07:09 PM UTC

    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

  2. identified Jul 15, 2025, 08:31 PM UTC

    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

  3. identified Jul 15, 2025, 09:19 PM UTC

    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

  4. identified Jul 16, 2025, 02:08 PM UTC

    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

  5. resolved Jul 16, 2025, 02:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 11, 2025

Some automation traffic received false HTTP 401

Detected by Pingoru
Jul 11, 2025, 10:40 PM UTC
Resolved
Jul 11, 2025, 10:40 PM UTC
Duration
Timeline · 1 update
  1. resolved Jul 14, 2025, 05:13 PM UTC

    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.

Read the full incident report →

Minor July 2, 2025

Signals-adjacent features are lagging

Detected by Pingoru
Jul 02, 2025, 03:54 PM UTC
Resolved
Jul 02, 2025, 04:46 PM UTC
Duration
51m
Timeline · 5 updates
  1. investigating Jul 02, 2025, 03:54 PM UTC

    We are currently investigating this issue.

  2. investigating Jul 02, 2025, 03:56 PM UTC

    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.

  3. identified Jul 02, 2025, 04:01 PM UTC

    The issue has been identified and a fix is being implemented.

  4. identified Jul 02, 2025, 04:03 PM UTC

    We have worked through the backlog of alerts and are monitoring performance

  5. resolved Jul 02, 2025, 04:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 26, 2025

Unable to start incidents in Microsoft Teams

Detected by Pingoru
Jun 26, 2025, 06:20 PM UTC
Resolved
Jun 26, 2025, 06:36 PM UTC
Duration
16m
Timeline · 4 updates
  1. investigating Jun 26, 2025, 06:20 PM UTC

    We are currently investigating this issue.

  2. identified Jun 26, 2025, 06:20 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Jun 26, 2025, 06:26 PM UTC

    We have deployed a fix to MS Teams and are waiting to confirm that this solves the issue

  4. resolved Jun 26, 2025, 06:36 PM UTC

    This incident has been resolved.

Read the full incident report →