rewindex

CompaniesFireHydrantIncidents

FireHydrant: Slack experiencing latency when declaring incidents

MinorStatus: resolvedStarted Resolved (53 min)4 updatesstatus.firehydrant.com (opens in new tab)

Affected components: Slack

Timeline of updates

  1. resolved

    We are investigating an issue with Slack being able to declare incidents. Please use the web UI in the meantime.

  2. resolved

    Slack is experiencing latency in posting messages when declaring an incident. The web UI continues to be fully functional.

  3. resolved

    We have identified the source of the issue and are working through the backlog of Slack notifications

  4. resolved

    We have worked through the backlog of Slack notifications and have mitigated the issue. We will continue to keep an eye on the issue.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

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

Cite this

Status incident (vendor impact label: minor) posted by FireHydrant, started 2026-01-20 17:01 UTC, resolved after 53 min, 4 update(s).

Title
Slack experiencing latency when declaring incidents
Vendor
FireHydrant
Date
URL
https://rewindex.com/company/firehydrant/incidents/dce21003-3b61-4282-968a-524e29c6be93

FireHydrant profileRecent FireHydrant incidentsAll outages on January 20, 2026FireHydrant in January 2026MarkdownJSON