rewindex

ChangesbeehiivPublication websites inaccessible

beehiiv: Critical incident: Publication websites inaccessible

Major incidentoutage (model (Jev), 99%)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: Publication websites inaccessible
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2025-06-10 16:24 UTC
AddedResolved time#5
Before: not present
After: 2025-06-10 16:24 UTC
AddedAffected components#6
Before: not present
After: App Admin, Public API, Publication websites
AddedUpdateinvestigating#7
Before: not present
After: We've been notified of an issue with our upstream platform provider and are currently assessing the impact on beehiiv publication websites.
AddedUpdateidentified#8
Before: not present
After: Publication websites may be slow or inaccessible, and App Admin performance is degraded while our platform provider resolves ongoing issues. We're monitoring the situation closely.
AddedUpdateidentified#9
Before: not present
After: Publication websites may be slow or inaccessible due to ongoing issues with our platform provider. Heroku is still investigating and remediating issues with their services: https://status.heroku.com/incidents/2822. We continue to monitor this situation closely.
AddedUpdatemonitoring#10
Before: not present
After: While our upstream provider continues to have issues, we have resolved the performance issues on our end and publication websites and admin access is restored.
AddedUpdateresolved#11
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

Tuesday, June 10, 2025

1 incident change

All beehiiv changesbeehiiv profileMarkdownJSON