Companies/FireHydrant/Incidents

FireHydrant: Slack API Incident: Trouble connecting and loading

Timeline of updates

1. update2025-02-26 16:08 UTC

   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 (opens in new tab) for more information.

2. update2025-02-26 16:16 UTC

   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/ (opens in new tab)

3. update2025-02-26 16:34 UTC

   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/ (opens in new tab)

   You can also visit Slack's status page at https://slack-status.com/2025-02/1b757d1d0f444c34 (opens in new tab) for more information.

4. update2025-02-26 17:13 UTC

   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 (opens in new tab)

5. update2025-02-26 17:13 UTC

   Slack reports: 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/ (opens in new tab)

   You can also visit Slack's status page at https://slack-status.com/2025-02/1b757d1d0f444c34 (opens in new tab) for more information

6. update2025-02-26 18:29 UTC

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

7. update2025-02-26 20:53 UTC

   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 (opens in new tab)

8. update2025-02-26 22:25 UTC

   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 (opens in new tab)

9. update2025-02-27 00:56 UTC

   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).

Impact, status and times are the vendor’s own, as last archived. View on status.firehydrant.com (opens in new tab).

FireHydrant profileRecent FireHydrant incidentsAll outages on February 26, 2025FireHydrant in February 2025MarkdownJSON