Skip to main content
FeedBlitz logo

Is FeedBlitz Down?

No — FeedBlitz is up

Reachable from all 8 checked regions

Average response time: 987ms

Last checked · checks run every 6 hours

Official status page: https://status.feedblitz.com

FeedBlitz uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
872ms
Avg response, 30 days

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

30-day history

9-day clean streak
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: no data
Aug 29: no data
Aug 30: no data
Aug 31: no data
Sep 1: no data
Sep 2: no data
Sep 3: no data
Sep 4: no data
Sep 5: no data
Sep 6: no data
Sep 7: no data
Sep 8: no data
Sep 9: no data
Sep 10: no data
Sep 11: no data
Sep 12: 100.00% uptime, 24 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 31 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 16 checks
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.

gru
1509ms
DNS 574ms TCP 150ms TLS 156ms TTFB 1057ms
iad
379ms
DNS 89ms TCP 43ms TLS 48ms TTFB 243ms
jnb
1902ms
DNS 303ms TCP 254ms TLS 257ms TTFB 1097ms
lax
474ms
DNS 135ms TCP 44ms TLS 48ms TTFB 295ms
lhr
738ms
DNS 44ms TCP 108ms TLS 112ms TTFB 400ms
nrt
1021ms
DNS 179ms TCP 134ms TLS 141ms TTFB 612ms
ord
267ms
DNS 104ms TCP 19ms TLS 22ms TTFB 191ms
sin
1609ms
DNS 313ms TCP 208ms TLS 218ms TTFB 971ms

What FeedBlitz does

FeedBlitz turns a blog's RSS feed into email, sending new posts to subscribers automatically, and also runs standalone newsletters, signup forms and landing pages. Bloggers and publishers use it as the delivery layer between their site and their mailing list. Because it polls a feed rather than being triggered by the publisher, a send happens without anyone pressing a button.

What an outage looks like

A post publishes on the blog normally and the email never arrives, with no error shown anywhere the publisher looks. Subscribers report missing issues before the publisher notices. The management portal fails to load, so campaigns cannot be scheduled or edited. Signup forms and landing pages stop accepting addresses, and two-factor text messages do not arrive, locking the publisher out.

What to do about it

Read status.feedblitz.com, which lists Email Marketing, RSS feeds, the Management Portal, Forms and Landing Pages, the CDN, the third-party services FeedBlitz uses, and two-factor authentication texts for North America and Europe as separate components. Match the symptom to the row. Do not resend a campaign you are unsure went out until Email Marketing reports operational, because a queued send and a resend both deliver.

Is it down for everyone, or just you?

If this page says FeedBlitz 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

F
Feedly
MailerLite
MailerLite
beehiiv
beehiiv
Brevo
Brevo

FeedBlitz outage FAQ

My post published but subscribers got no email. Is FeedBlitz down?
Possibly, and this failure is quiet by design. FeedBlitz reads your RSS feed and sends from it, so your blog publishes normally whether or not FeedBlitz is working, and nothing on your site indicates a problem. RSS feeds and Email Marketing are separate components on its status page: the feed can be read correctly while the send fails, or the feed poll can fail so the post is never noticed.
Should I resend a campaign I think did not go out?
Wait until Email Marketing is reported operational, then check the send history rather than resending. A campaign delayed by an incident and one that failed outright look the same from the dashboard, and if the original was queued it will deliver when the service returns, so a resend lands as a duplicate in every subscriber's inbox. Duplicates cost more in unsubscribes than a late issue does.
I cannot log in because the two-factor text never arrives.
Check which region you are in, because FeedBlitz reports two-factor authentication texts for North America and Europe as two separate components. One can fail while the other delivers, so a colleague signing in from the other region proves nothing about your problem. This is an account-access failure rather than a sending failure: your campaigns and subscriber list are unaffected while you are locked out.
Do signups stop while FeedBlitz is down?
They can, and it is worth knowing separately from sending. Forms and Landing Pages is its own component, so a subscribe form embedded on your site can fail while emails continue to send to existing subscribers. Visitors who try during the outage usually do not come back to try again, which makes this the quietest cost of an incident.
Is the problem FeedBlitz or something it depends on?
FeedBlitz answers this directly: it lists the third-party services it uses as a component of its own, alongside a Content Delivery Network row. When that row is the one reporting a problem, the cause sits upstream and the timeline belongs to the provider rather than to FeedBlitz. Checking it first saves raising a ticket about something FeedBlitz is also waiting on.

How we measure this

  • We request FeedBlitz'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 FeedBlitz 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 FeedBlitz 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