FeedBlitz had 11 outages in the last 2 years totaling 297h 44m of downtime — averaging 0.5 incidents per month.
There were 11 FeedBlitz outages since February 5, 2025 totaling 297h 44m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
Mailings are being sent and engagement being recorded. Historical data and other issues related to this incident will be tracked separately.
Historic engagement data is currently no available in the reporting UI. The resolution is in progress and we expect to have it wrapped up on Sunday
We're making steady progress here and are 82% complete, but that does shift the ETA for completion to Monday
This incident has been resolved.
Starting around 4pm today, a core server and its backup experienced an overload, causing some services to be unavailable. we have identified the problem and are restoring capabilities
Unfortunately recovery seems further away than expected based on earlier estimates. Our teams continue to work the issue
We are continuing to work on a fix for this issue.
the app is now up and running. Engagement reports are however incomplete; these will be addressed over the coming days.
The disruption to mailings and the console were resolved overnight. A new incident will be opened as teams wrap up work on historic data
At approximately 4:30am this morning two core elements of FeedBlitz failed. We are currently working on restoring the service
FeedBlitz is now working albeit slowly. We're now working on restoring full performance and identifying any missed mailings
Services are now restored to full capacity. We are now working on sendng out any mailings that were missed during the outage
FeedBlitz is now running as expected. We apologize for the inconvenience this Christmas morning! If a mailing did not go out as expected, or did not reach the expected audience, you may log in, go to the relevant list's dashboard, and use the edit & resend / clone functions to (re)send the email to anyone who did not receive it at first. The root cause of the incident was an initial failure of a system, which correctly failed over to its backup. However, that backup also failed approximately an hour later. We are reviewing why that happened, and how to make the service more resilient to multiple devops issues in teh future.
Due to today's AWS outage, ads may not be served correctly and reporting is not up to date. Our provider is working the issue, and we will update this incident when we can.
Our ad service has established an incident for this issue, which can be found at https://status.liveintent.com/incidents/jxgrnfkccwxl
Ads are now being served into RSS feeds and new mailings; it is unclear as to whether ads served that previously resulted in broken images for emails generated while AWS was unhappy will be served correctly if refreshed now, however. Some reporting has appeared, but it seems to be very much delayed today as the relevant AWS services recover.
Ad serving is fully up to speed.
Our hosts are working on restoring the site. It being down doesn't affect mailings or RSS feed serving or tracking, the FeedBlitz service is 100% up.
The www site is up and running, however the change may take up to 24 hours to roll out to you.
This incident has been resolved.
The error has been corrected and we apologize for the inconvenience.
We are currently investigating this issue.
The issue has been identified and a correction put in place. Scheduled broadcast mailings are now catching up; we apologize for the inconvenience. RSS powered mailing were unaffected by this issue.
This incident has been resolved.
For some time this afternoon a technical issue as affected the availability of the app, engagement metrics, and scheduled mailings. The team is aware of the issue and is working to restore services as quickly as they can.
A fix has been implemented and we are monitoring the results.
FeedBlitz is still recovering from yesterday's tech issue, and is functioning in a degraded capacity. We apologize for the inconvenience while our teams continue to work to restore full functionality.
The system is now fully functional apart from per-user engagement data. We will keep this incident open until all elements of FeedBlitz are at 100%
The issue with FeedBlitz systems caused by a storage malfunction last week has been resolved. Unfortunately, recovery of engagement data from the afternoon of Feb 6 and most of Feb 7 has only been partial as some raw data was lost during outage. We regret and apologize for any inconvenience this may cause. Going forward we are changing our logging policies to allow for more robust data recovery, and performing an in-depth technical review to avoid the risk of this kind of incident recurring.