FireHydrant: Unable to declare incident from Slack
Affected components: Slack
Timeline of updates
- monitoring
Status Update: Slack Integration Unavailable
Incident: Unable to declare incident from Slack
We are currently investigating an incident affecting the ability to declare incidents through Slack.
What's happening: Our team is actively working to restore this functionality. We'll provide updates as we make progress on the resolution.
What you can do in the meantime: You can continue to declare incidents through our web interface or API until this is fully resolved.
We appreciate your patience and will update you shortly with more information.
- monitoring
We're continuing to investing this issue and recognize that it may be impacting the ability to declare incidents via web UI and mobile app, and causing a delay in acknowledging and displaying new alerts.
- monitoring
We've identified the root cause of these delays and are working to restore full functionality
- monitoring
We're continuing to monitor our fix to ensure full recovery
- monitoring
We've mitigated the incident and are working through the backlog of alerts to deliver them to users.
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. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-04 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
265aa12df1d1fcf5…
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-02-26 17:48 UTC, resolved after 3.8 h, 5 update(s).
- Title
- Unable to declare incident from Slack
- Vendor
- FireHydrant
- Date
- URL
- https://rewindex.com/company/firehydrant/incidents/b74e76eb-1c35-419b-a380-c5a734d3cfee
FireHydrant profileRecent FireHydrant incidentsAll outages on February 26, 2026FireHydrant in February 2026MarkdownJSON