beehiiv: Third-party infrastructure incident
Affected components: Publication websites
Timeline of updates
- identified
We have identified an issue triggered by one of our third-party cloud infrastructure vendors that is resulting in degraded performance. The main components currently affected are publication websites. The third-party vendor is aware of the issue and actively working on a fix. We will post updates as we have them.
- identified
We are continuing to work on a fix for this issue.
- identified
The third-party cloud vendor has implemented a fix. We will continue to monitor.
- monitoring
A fix has been implemented and we are monitoring the results.
- resolved
The fix from the third-party vendor looks to have worked and all systems are operational on our end now. We will continue to monitor for any changes.
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. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
9309eee7c92e99ce…
Impact, status and times are the vendor’s own, as last archived. View on www.beehiivstatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by beehiiv, started 2025-10-20 20:33 UTC, resolved after 0 min, 5 update(s).
- Title
- Third-party infrastructure incident
- Vendor
- beehiiv
- Date
- URL
- https://rewindex.com/company/beehiiv/incidents/gpd2mrnz4wmt
beehiiv profileRecent beehiiv incidentsAll outages on October 20, 2025beehiiv in October 2025MarkdownJSON