FireHydrant: Signals-adjacent features are lagging
Timeline of updates
- update
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.
- update
We have worked through the backlog of alerts and are monitoring performance
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
d98370fe4f1dadd8…
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 2025-07-02 15:43 UTC, resolved after 1.1 h, 2 update(s).
- Title
- Signals-adjacent features are lagging
- Vendor
- FireHydrant
- Date
- URL
- https://rewindex.com/company/firehydrant/incidents/5fd82f3e-daa6-465d-ae9e-04d0d368f934
FireHydrant profileRecent FireHydrant incidentsAll outages on July 2, 2025FireHydrant in July 2025MarkdownJSON