Is beehiiv Down?

No — beehiiv is up

Reachable from all 8 checked regions

Average response time: 1395ms

Last checked 3 hours ago · checks run every 6 hours

Official status page: https://www.beehiivstatus.com

beehiiv uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

1593ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 23 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

23-day clean streak

Aug 22 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

lax

569ms

DNS 11ms TCP 2ms TLS 6ms TTFB 334ms

lhr

987ms

DNS 66ms TCP 2ms TLS 8ms TTFB 606ms

nrt

1618ms

DNS 110ms TCP 1ms TLS 9ms TTFB 871ms

ord

1158ms

DNS 7ms TCP 2ms TLS 10ms TTFB 1079ms

sin

2651ms

DNS 105ms TCP 1ms TLS 7ms TTFB 1575ms

sjc

664ms

DNS 54ms TCP 1ms TLS 7ms TTFB 473ms

syd

2493ms

DNS 143ms TCP 1ms TLS 9ms TTFB 1394ms

yyz

1025ms

DNS 48ms TCP 1ms TLS 6ms TTFB 957ms

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 18 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.
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. We only change the 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. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when beehiiv goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required