rewindex

CompaniesFireHydrantIncidents

FireHydrant: Runbooks are not attaching

CriticalStatus: resolvedStarted Resolved (3.2 h)2 updatesstatus.firehydrant.com (opens in new tab)

Timeline of updates

  1. update

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

  2. update

    This incident has been resolved.

Changes Rewindex caught on this incident

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: critical) posted by FireHydrant, started 2024-01-03 20:35 UTC, resolved after 3.2 h, 2 update(s).

Title
Runbooks are not attaching
Vendor
FireHydrant
Date
URL
https://rewindex.com/company/firehydrant/incidents/e2d47a59-4a07-4f72-a4d2-c96fe64ad79b

FireHydrant profileRecent FireHydrant incidentsAll outages on January 3, 2024FireHydrant in January 2024MarkdownJSON