Struck in red is what FireHydrant removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
AddedTitle#1
Before: not present
After: Degraded availability in Fastly's Newark (EWR) region
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2024-07-08 18:27 UTC
AddedResolved time#5
Before: not present
After: 2024-07-08 19:47 UTC
AddedUpdate#6
Before: not present
After: We are currently being impacted by degraded availability in Fastly's Newark (EWR) region. We are monitoring Fastly's availability here: https://www.fastlystatus.com/incident/376675
AddedUpdate#7
Before: not present
After: We are currently investigating an incident impacting the availability of our services in Fastly's Newark (EWR) region. Customers may experience delays, performance issues, or difficulties in accessing our services if based in this region. We understand the impact this may have on your business operations and are monitoring the situation closely on Fastly's status page: https://www.fastlystatus.com/incident/376675
AddedUpdate#8
Before: not present
After: We are continuing to monitor the ongoing degraded availability in Fastly's Newark (EWR) region. Customers in that area and the east coast in general may be experiencing degraded availability of FireHydrant's services in their web browser. Access to FireHydrant via Slack and Microsoft Teams remains stable, and we recommend using FireHydrant from their installed chat integration.
AddedUpdate#9
Before: not present
After: We are seeing signs of recovery. We are continuing to monitor the ongoing degraded availability in Fastly's Newark (EWR) region
AddedUpdate#10
Before: not present
After: Impacted services are now operating normally.
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.