Is beehiiv Down?

No — beehiiv is up

beehiiv's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 797 ms

Right now

The verdict is the worse of these two. How we decide

beehiiv's status page

beehiivstatus.com · read 2 minutes ago · checked every 3 minutes

Operational

beehiiv's components, as its status page reports them
Component	Status
Publication websites	Operational
App Admin	Operational
Public API	Operational
MCP	Operational
Sending emails	Operational
Email Metrics	Operational
Embed forms	Operational
SendGrid API v3	Operational
SendGrid Event Webhook	Operational
Email statistics collection	Operational

Open their status page

FlareWarden checks

beehiiv.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 797 ms
Checked: 1 hour ago

By region

Ashburn reachable, 445 ms
Dallas reachable, 486 ms
Frankfurt reachable, 663 ms
Johannesburg reachable, 1900 ms
Los Angeles reachable, 629 ms
Newark reachable, 526 ms
Paris reachable, 745 ms
São Paulo reachable, 986 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	44 ms	2 ms	6 ms	435 ms
Dallas	54 ms	1 ms	7 ms	482 ms
Frankfurt	59 ms	2 ms	12 ms	655 ms
Johannesburg	178 ms	1 ms	5 ms	1417 ms
Los Angeles	186 ms	3 ms	13 ms	558 ms
Newark	42 ms	3 ms	9 ms	514 ms
Paris	37 ms	2 ms	11 ms	737 ms
São Paulo	126 ms	2 ms	10 ms	858 ms

We check that beehiiv.com loads, not every feature behind it. Test it yourself

History

Incidents beehiiv reported

Since Oct 22, 15 days · from beehiivstatus.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

beehiiv website availability

Measured by FlareWarden · beehiiv.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 1019ms

Last 30 days

69-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of beehiiv.com from multiple regions every 6 hours. beehiiv's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 69 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What beehiiv does

beehiiv is a newsletter publishing platform. Writers compose and schedule posts, manage subscriber lists, run advertising and monetisation, and publish a website for each publication. Sending goes out through SendGrid, which beehiiv reports as its own dependency. Publishers depend on it for two separate jobs: delivering email, and hosting the archive readers reach from search and social.

What an outage looks like

Scheduled sends stall or fail, or the admin app will not load while publication websites keep serving. Email Metrics and statistics collection are separate components, so open and click numbers can freeze while delivery is fine, which reads like a failed send when it is a reporting gap. Embed forms stop capturing subscribers on external sites.

What to do about it

Check beehiivstatus.com and identify which half is affected. beehiiv lists the SendGrid API and the SendGrid Event Webhook as components of its own, so a sending incident is often upstream at SendGrid rather than inside beehiiv. Do not resend a campaign because metrics look empty: statistics collection is reported separately from sending, and a stalled dashboard is not proof mail failed.

Is it down for everyone, or just you?

If this page says beehiiv is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

beehiiv outage FAQ

My newsletter shows zero opens. Did the send fail?

Not necessarily. beehiiv reports Sending emails, Email Metrics and Email statistics collection as three separate components. An incident confined to metrics or statistics collection leaves delivery working while the numbers you use to judge it stop updating. Confirm against the Sending emails component before concluding the campaign did not go out, and never resend on empty metrics alone.

Is a beehiiv sending problem actually a SendGrid problem?

It can be. beehiiv publishes SendGrid API v3 and SendGrid Event Webhook as components on its own status page, which means it treats SendGrid as a dependency it monitors rather than an internal detail. When those rows are the ones affected, the failure is upstream and beehiiv recovers when SendGrid does.

My publication website is up but I cannot log in to beehiiv.

That is a normal split. Publication websites and App Admin are separate components, and the reader-facing sites are served independently of the authoring application. Readers arriving from search or social see nothing wrong while you cannot publish. Check the App Admin row, and expect the archive to keep serving through an authoring-side incident.

Do subscriber sign-ups get lost when embed forms are down?

Embed forms are their own component, and beehiiv does not publish queueing behaviour for them on its status page. Assume sign-ups attempted during that window did not land. If the form sits on a site you control, a temporary fallback that collects addresses locally protects the ones you would otherwise never see again.

Will a scheduled send go out if beehiiv is down at that moment?

beehiiv does not publish what happens to a send scheduled during an incident, so do not assume it fires late or fires at all. After the Sending emails component recovers, check the campaign state directly rather than trusting the schedule. Resending blindly risks a duplicate to subscribers who already received it.

How we measure this

We request beehiiv's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where beehiiv publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of beehiiv itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when beehiiv goes down

We check beehiiv every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required