rewindex

ChangesbeehiivElevated errors on publication websites

beehiiv: Critical incident: Elevated errors on publication websites

Major incidentcritical (vendor)Changed Detected www.beehiivstatus.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 beehiiv removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: Elevated errors on publication websites
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-02-18 03:25 UTC
AddedResolved time#5
Before: not present
After: 2026-02-18 03:25 UTC
AddedAffected components#6
Before: not present
After: Publication websites
AddedUpdateinvestigating#7
Before: not present
After: We are seeing increased error rates serving newsletter websites and are investigating.
AddedUpdateinvestigating#8
Before: not present
After: The majority of platform websites are currently unavailable due to an issue with our hosting provider Heroku, their runtime team is also working to resolve the issue.
AddedUpdateidentified#9
Before: not present
After: Our upstream provider Heroku has acknowledged the incident and it is working to remediate https://status.salesforce.com/incidents/20003708
AddedUpdateidentified#10
Before: not present
After: We are continuing to work on a fix for this issue.
AddedUpdatemonitoring#11
Before: not present
After: Newsletter websites are back! We continue to monitor closely.
AddedUpdateresolved#12
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, February 18

1 incident change

All beehiiv changesbeehiiv profileMarkdownJSON