Is FeedBlitz Down?

Partially — FeedBlitz is degraded

FeedBlitz's status page: Degraded · problems at 1 of its 2 locations
FlareWarden checks: Website reachable · 8 of 8 regions · 659 ms

Right now

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

FeedBlitz's status page

status.feedblitz.com · read 4 minutes ago · checked every 3 minutes

Degraded

FeedBlitz's components, as its status page reports them
Component	Status
Knowledge Base	Operational
Content Delivery Network	Operational
Email Marketing	Operational
RSS feeds	Operational
Management Portal	Operational
Forms and Landing Pages	Operational

2 locations 1 reporting problems

Two Factor Authentication Texts, Europe · Degraded Performance

Locations change the verdict only once a quarter of them are in trouble.

Open their status page

FlareWarden checks

feedblitz.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: 659 ms
Checked: 24 minutes ago

By region

Amsterdam reachable, 860 ms
Dallas reachable, 136 ms
Newark reachable, 352 ms
Paris reachable, 854 ms
San Jose reachable, 422 ms
Stockholm reachable, 992 ms
Sydney reachable, 1415 ms
Toronto reachable, 243 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	40 ms	113 ms	116 ms	405 ms
Dallas	54 ms	9 ms	11 ms	105 ms
Newark	121 ms	34 ms	36 ms	248 ms
Paris	114 ms	118 ms	121 ms	498 ms
San Jose	80 ms	53 ms	57 ms	264 ms
Stockholm	52 ms	130 ms	133 ms	467 ms
Sydney	257 ms	187 ms	190 ms	850 ms
Toronto	35 ms	30 ms	32 ms	151 ms

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

History

Incidents FeedBlitz reported

Since Oct 22, 15 days · from status.feedblitz.com

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

No incidents reported in this window.

FeedBlitz website availability

Measured by FlareWarden · feedblitz.com

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

Last 30 days

55-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

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

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 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

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. 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 FeedBlitz 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 FeedBlitz 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 FeedBlitz goes down

We check FeedBlitz 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