Is FireHydrant Down Right Now? Check if there is a current outage ongoing.

The site is currently experiencing latency upon first loading the web ui. Slack users may also be experiencing latency using /fh new. Our underlying infrastructure provider is currently experiencing an incident. Please continue to refer back to this page for updates.

We are currently investigating this issue.

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

We have detected a broad inability to connect to make SSL connections across integrations. Our engineers have addressed this in a fix which should be deployed within the next few minutes.

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

We have identified the issue and are working on a fix. Our web UI is not impacted and can be accessed at https://app.firehydrant.io/

We are currently investigating this issue.

Slack's issues have been resolved. All systems are operational

We are continuing to monitor the situation and are standing by. You can continue to get updates on the incident on Slack's status page at https://slack-status.com Our web UI is not impacted and can be accessed at https://app.firehydrant.io/

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.

Zoom is reporting that it's services have been restored. "If you are still having connection issues please flush your DNS cache and attempt to reconnect." - Zoom Status Page https://status.zoom.us/incidents/pw9r9vnq5rvk

Zoom is currently experiencing an incident that may impact FireHydrant's ability to attach Zoom meetings to incidents and invite scribes. We're monitoring the incident closely and will provide an update when we're back in business!

We are currently investigating this issue.

This incident has been resolved.

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

We are currently shipping a fix for disconnection messages on retrospectives. Users can reconnect to a given retrospective field by clicking the reconnect button.

Slack reports that full functionality has been restored. If you're still encountering any trouble, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux).

Slack states that while some users may notice improvements, they remain focussed on resolving the issues and are working on this with the highest urgency. "Remediation work involves repairing affected database shards, which are causing feature degradation issues. This has become a diligent process to ensure we're prioritizing the database replicas with the most impact." The FireHydrant UI remains unaffected, and we're continuing to monitor Slack's status page for updates https://slack-status.com/2025-02/1b757d1d0f444c34

Slack has identified the cause of the issue and are continuing to monitor their health metrics, but are still not fully resolved. Some users may still have issues loading their workspaces. "Our work is still ongoing to restore affected backend services to returning functionality to impacted features." https://slack-status.com/2025-02/1b757d1d0f444c34

Slack is "still working to restore functionality to affected Slack features such as sending messages, workflows, threads and other API-related features"

Slack continues to report issues with connecting or loading Slack. "Our investigation is still in progress with regard to deprecated functionality for Slack features such as workflows, threads, sending messages and API-related features. We'll be back with more updates as soon as they're available." You can monitor the status of Slack's incident at https://slack-status.com/2025-02/1b757d1d0f444c34

Slack reports they are "We're continuing our efforts to restore functionality to affected features such as workflows, sending messages, threads and API-related features. Users may also experience issues when attempting to log-in. We appreciate your continued patience. More updates will be shared as soon as possible.", This may affect your ability to use FireHydrant's Slack integration. We recommend using our web UI to manage incidents reliably https://app.firehydrant.io/ You can also visit Slack's status page at https://slack-status.com/2025-02/1b757d1d0f444c34 for more information.

Slack reports they are "still working to restore functionality to affected Slack features such as sending messages, workflows, threads and other API-related feature", which may affect your ability to use FireHydrant's Slack integration. We recommend using our web UI to manage incidents reliably https://app.firehydrant.io/ You can also visit Slack's status page at https://slack-status.com/2025-02/1b757d1d0f444c34 for more information.

Slack is also reporting some workflows may also be experiencing issues, which may impact your ability to use FireHydrant's Slack integration and workflows. Our web UI is not impacted and can be accessed at https://app.firehydrant.io/

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

Slack is reporting trouble connecting or loading Slack, and that a variety of API endpoints, sending/receiving messages, and some threads loading are impacted. We will continue to monitor their status page for updates. You can monitor the status of Slack's incident at https://slack-status.com/2025-02/1b757d1d0f444c34 for more information.

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.

Earlier this morning our upstream provider resolved the incident. We’ve also noticed no additional problems and are closing this out.

We've received updates from our upstream provider that the documentation platform is back up and they are continuing to monitor the situation. Accessing https://docs.firehydrant.com also shows the portal is now accessible again. We will also continue to keep an eye on the situation on our side.

Our upstream provider for documentation, ReadMe, is currently experiencing an outage where both customer-facing docs and API reference docs are down. Please reference their statuspage for latest updates: https://www.readmestatus.com/

We are currently investigating this issue.

We have confirmed no data loss occurred with retrospectives and our fix is working. A detailed root cause analysis will be shared in an upcoming blog post. We apologize for any inconvenience this has caused.

We're are continuing to implement a solution to the rendering issues and ensuring that all data is displayed properly

We've identified an issue with how data is being displayed in the new Retrospective view. While we're working on a fix, we've temporarily reverted to our previous Retrospective experience.

We've identified an issue with how data is being displayed in the new Retrospective view. While we're working on a fix, we've temporarily reverted to our previous Retrospective experience.

We have identified the issue and are reverting to the previous Retrospective experience

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

This incident has been resolved.

We have applied a fix and API latency has returned to normal.

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

A fix has been implemented and API latency is recovering

We are experiencing some latency with our API. Slack, web, mobile, Teams, and Signals are unaffected

We are experiencing some latency with our API. Slack, web, mobile, Teams, and Signals are unaffected

We are experiencing some latency with our API. Slack, web, mobile, Teams, and Signals are unaffected

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

All services are operational

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

Users are unable to declare incidents via the web UI do to a misconfiguration. We have identified the issue and are rolling the fix now. Slack and MS Teams incident management remain unaffected

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

This incident has been resolved.

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

We are continuing to drain the Slack queue and seeing continued improvement in Slack notification latency

We are continuing to process the backlog of Slack updates. Web application functionality remains operational

We are continuing to process the backlog of Slack updates and seeing improved progress

We are continuing to process the backlog of Slack updates

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

We are currently investigating this issue.

This incident has been resolved.

New incident behavior should be working as expected. We are continuing to work through the backlog of events in the queue and monitoring performance

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

We are continuing to work through the queue of backlogged requests and monitoring performance

We are continuing to work through the queue of backlogged requests

We have identified the issue and are continuing to work through a backlog of requests in the queue

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

Our systems have detected an availability or performance update with Slack and we're investigating the impact. Additionally, our site is currently experiencing a higher than normal load time, and may be causing pages to be slow or unresponsive. We're investigating the cause and will provide an update as soon as possible.

We are currently investigating this issue.

This incident has been resolved.

The backlog of jobs have been cleared and performance is recovering.

We are continuing to investigate this issue.

The team is investigating an incident affecting the FireHydrant platform. We'll follow-up with more information as it becomes available.

This incident has been resolved.

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

We are continuing to work on a fix for this issue.

We are continuing to work on a fix for this issue.

Our upstream provider, Microsoft, is currently experiencing an issue which is affecting our ability to authenticate into Microsoft Teams. We are in contact with Teams support to actively resolve the issue. We will resolve this incident once we have received confirmation the issue has been resolved from our upstream provider.

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

FireHydrant experienced a prolonged delay of runbook executions due to a sudden outlier amount of traffic to our services. This traffic caused a shared worker queue to flood and go into a "spin lock" preventing other work from executing, such as runbook attachment. Existing incidents were not impacted from this incident, and our systems have been scaled to handle traffic spikes like the one experienced in the future.

All backlogs have successfully cleared and Runbooks are functioning as expected

We've processed the backlog of Runbook attachments and are seeing Runbooks execute as expected

We've identified a backlog of runbook attachments and are working to process them

We are continuing to investigate an issue with runbooks not attaching to incidents automatically, and manually attached runbooks not executing

We're investigating an issue with Runbooks failing to attach to incidents

We are currently investigating this issue.

This incident has been resolved.

We have mitigated the issue with our Jira Cloud integration. Please reach out to your Customer Support Manager if you are still experiencing issues.

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

We have identified the issue with our Jira Cloud integration and are working on a fix.

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

We are investigating issues with our Jira Cloud integration

We are currently investigating this issue.

Impacted services are now operating normally.

We are seeing signs of recovery. We are continuing to monitor the ongoing degraded availability in Fastly's Newark (EWR) region

We are seeing signs of recovery. We are continuing to monitor the ongoing degraded availability in Fastly's Newark (EWR) region

We are continuing to monitor the ongoing degraded availability in Fastly's Newark (EWR) region. Customers in that area and the east coast in general may be experiencing degraded availability of FireHydrant's services in their web browser. Access to FireHydrant via Slack and Microsoft Teams remains stable, and we recommend using FireHydrant from their installed chat integration.

We are currently investigating an incident impacting the availability of our services in Fastly's Newark (EWR) region. Customers may experience delays, performance issues, or difficulties in accessing our services if based in this region. We understand the impact this may have on your business operations and are monitoring the situation closely on Fastly's status page: https://www.fastlystatus.com/incident/376675

We are currently investigating an incident impacting the availability of our services in the Fastly Newark (EWR) region. Our team is aware of the issue and are monitoring Fastly's incident here: https://www.fastlystatus.com/incident/376675 Customers may be experiencing delays, performance issues, or difficulties in accessing our services if based in this region. We understand the impact this may have on your business operations and are committed to restoring full functionality as soon as possible. While our team works to address the root cause, we do not have any workarounds to suggest at this time. We will continue to provide updates on the progress of our resolution efforts. We apologize for the inconvenience and appreciate your patience and understanding as we work to restore normal service levels. Please continue to monitor our status page for the latest information.

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

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 has resolved the issue on their side.

Slack has determined that the majority of users should no longer be experiencing issues, although the root cause of the incident is still under investigation. 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.

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

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 has resolved this on their side. We are resolving.

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.

This incident has been resolved.

We are still monitoring Slack's status page. It appears Slack is still having some issues with files and image previews, but other services are reportedly back up and running. We have not observed any issues today with modal loading latency so far, but have noticed a few delays with message delivery. To hard reload Slack, please use cmd/ctrl + R . As a reminder, our web UI is not impacted and can be accessed at https://app.firehydrant.io/.

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

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.

This incident has been resolved.

We are aware of an incident with Slack modal focusing. As a workaround, incidents may be declared and managed in the FireHydrant web UI,

We are aware of an incident with Slack modal focusing. As a workaround, incidents may be declared and managed in the FireHydrant web UI,

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

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.

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. Slack is reporting that they are seeing recovery across some of their systems https://status.slack.com/ Our web UI is not impacted and can be accessed at https://app.firehydrant.io/

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

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.

This incident has been resolved.

Runbooks steps have been delayed in some cases. Retry mechanisms are complete. Impacted customers should see recovery and expected functionality.

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

This incident has been resolved.

A fix has been implemented

Some runbooks may be loading inconsistently. The issue has been identified and we are currently working on a fix.

This incident has been resolved.

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

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.

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.

This incident has been resolved.

We identified an issue with some Slack commands and implemented a fix.

We've detected elevated error rates with slack commands and are investigating.

This incident has been resolved.

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

Slack message posting and channel creation looks to be improving. We haven't seen any errors in either workflow since 17:30 UTC. We'll keep monitoring and provide another update soon. #hugops to our friends at Slack

We're continuing to monitor Slack's status. Message posting is succeeding in most cases (5% failure rate) but channel creation is still unavailable (100% failure rate since 16:01 UTC) https://status.slack.com/2023-08/8ec13e4962a9bf43

We're seeing this impact the ability to users to send Slack messages to existing channels as well. Please remind your teams to use the chat functionality in FireHydrant in the interim. https://app.firehydrant.io

We're monitoring an upstream availability issue with Slack and will provide updates as they're made available to us. As a workaround, your teams can use the chat functionality built into the FireHydrant app (https://app.firehydrant.io).

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.

This incident has been resolved.

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

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

We have identified the issue. We are validating a fix.

Users may be unable to update tasks from the incident overview page. We're working to remediate this but in the interim, tasks can be updated from the task overview page: https://app.firehydrant.io/incidents/tasks

The team is investigating an incident affecting the FireHydrant platform. We'll follow-up with more information as it becomes available.

We are monitoring the rollback.

One failure for role assignment for an on-call user in runbooks was detected, a fix is in place and being deployed.

This incident has been resolved.

We've identified the issue and have restored service.

We're investigating reports of trouble accessing the FireHydrant UI. Our API and Slack functionality are not impacted.

The team is investigating an incident affecting the FireHydrant platform. We'll follow-up with more information as it becomes available.

This incident has been resolved.

We are resolving this incident. We have addressed the issue that was originally causing the problem when the incident was declared. We will do follow up work to address edge cases.

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

We have identified the issue and are working on a fix.

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

We are investigating an issue, where some users are unable to declare incidents.

We are currently investigating this issue.

This incident has been resolved.

We've identified and fixed the issue. We will continue to monitor error rates.

We are continuing to investigate this issue.

We're investigating an elevated amount of errors related to Runbook execution around Slack and Zoom integrations.

A substantial increase traffic to status pages caused a capacity overload, and our infrastructure didn't scale in time to meet demand. After increasing our capacity, status page behavior returned to normal.

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.

The issue with listing status pages has been reolved.

We have mitigated the issue. We are working toward a final fix.

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

We are still working on the fix for this issue.

We have identified the issue and are working on fix.

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

We are investigating an issue preventing status page lists from loading.

We are currently investigating this issue.

This incident has been resolved.

We're continuing to monitor the situation but overall platform availability is stable. A small percentage of traffic is still subject to performance constraints but core functionality is unaffected at this point (99.994% over the last 24 hours)

We've identified the source of the performance degradation and have isolated that traffic, restoring service for the remainder of the platform. We'll continue monitoring throughout the evening and will share another update tomorrow.

We've identified the issue and confirmed that this is affecting a small percentage of requests. We're working to remediate the issue and will provide another update soon.

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

The team is investigating an incident affecting the FireHydrant platform. We'll follow-up with more information as it becomes available.

This incident has been resolved.

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

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

We are currently investigating this issue.

This incident has been resolved.

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

We have identified the issue and we are working on a fix.

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

We are investigating an issue that is blocking new users from registering.

We are currently investigating this issue.

This incident has been resolved.

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

This issue impacting the performance of Slack runbook steps has been remediated. We'll continue to monitor the situation.

We're investigating delays in executing Slack-specific runbook steps and we'll update with more information soon.

The team is investigating an incident affecting the FireHydrant platform. We'll follow-up with more information as it becomes available.

This incident has been resolved.

We have reverted to V2 of Recaptcha and users should be able to login. We will fully resolve once we've identified a long term solution.

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

We have identified an issue with our upgrade to Recaptcha V3 that is preventing some users from logging in. We are in the process of reverting back to V2.

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

This incident has been resolved.

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

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

We are currently investigating this issue.

This incident has been resolved.

We will continue to monitor performance before resolving.

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.

This incident has been resolved.

We've identified and fixed the performance issue and have re-enabled incident participation stats for everyone. They should now be visible in retrospectives once again.

The team has identified a more resilient fix and is working towards implementation. We continue to have the internal API endpoint disabled, only impacting the display of Incident Statistics in the Command Center.

The team has identified and put in a stop-gap fix to address the small percentage of users who experienced timeout errors today. We have temporarily disabled an internal endpoint around incident statistics. This does not impact the Analytics page. Please reach out to our support team if there are any further questions.

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

We're monitoring the impact of an minor availability issue for our platform. Between 16:09 and 16:13 UTC a small percentage of users may have received timeout errors; we're continuing to investigate but the platform is fully available.

The team is investigating an incident affecting the FireHydrant platform. We'll follow-up with more information as it becomes available.

We have deployed a fix for this issue.

This incident has been resolved.

The team has identified the issue and is working on a fix.

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

It has been reported that users using Required Fields are unable to open an incident from a PagerDuty alert in Slack using "Yes, Open" option. The current work around is to declare it using "Yes, Open & Edit" and ensuring required fields are filled out. The team is investigating. Please reach out to support@firehydrant.com if you are experiencing any further issues.

We are currently investigating this issue.

We have deployed a fix for this issue.

We have identified the issue and a fix. Another update will be posted once the fix is deployed.

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

This performance issue has been resolved.

We've mitigated the performance issue and are continuing to monitor the situation.

The team is investigating an incident affecting the FireHydrant platform. We'll follow-up with more information as it becomes available.

This incident has been resolved.

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

We have identified the issue and are working on shipping a fix.

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

We are observing that for some customers, third-party linked alerts are not auto-resolving upon Incident resolution. We are looking into the issue and will post once a fix is identified.

We are currently investigating this issue.

This incident has been resolved.

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

We have identified the issue and we are working on shipping a fix.

We are currently investigating an issue with a limited number of timeline events loading in the UI.

We are currently investigating this issue.

This incident has been resolved.

The team is investigating an incident affecting the FireHydrant platform. We'll follow-up with more information as it becomes available.

This incident has been resolved.

The team is investigating an incident affecting the FireHydrant platform. We'll follow-up with more information as it becomes available.