rewindex

ChangesFireHydrantRunbooks are not attaching

FireHydrant: Critical incident: Runbooks are not attaching

Major incidentoutage (model (Jev), 55%)Changed Detected status.firehydrant.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what FireHydrant removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: Runbooks are not attaching
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2024-01-03 20:35 UTC
AddedResolved time#5
Before: not present
After: 2024-01-03 23:47 UTC
AddedUpdate#6
Before: not present
After: Runbooks steps have been delayed in some cases. Retry mechanisms are complete. Impacted customers should see recovery and expected functionality.
AddedUpdate#7
Before: not present
After: This incident has been resolved.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

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.

Rewindex captured this after the last checkpoint; the next run () commits it.

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

History of this incident

Wednesday, January 3, 2024

1 incident change

Cite this

Critical incident: Runbooks are not attaching on FireHydrant’s status page, changed 2024-01-03 20:35 UTC (change 1 of 1).

Title
Critical incident: Runbooks are not attaching
Vendor
FireHydrant
Date
URL
https://rewindex.com/change/i78991854943b86

All FireHydrant changesFireHydrant profileMarkdownJSON