FeedBlitz Status · History · Incident #63906
RESOLVEDSystem-wide outage
Critical · Started Dec 25, 2025 · 8:20 AM
FeedBlitz Status · History · Incident #63906
RESOLVEDCritical · Started Dec 25, 2025 · 8:20 AM
Duration
1h 33m
Severity
Critical
Detection lead
—
User reports
—
Summary
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.
Started
Dec 25, 2025 · 8:20 AM
Resolved
Dec 25, 2025 · 9:54 AM
Duration
1h 33m
Severity
Critical
Event timeline
Investigating
Dec 25 · 8:20 AM FeedBlitzAt approximately 4:30am this morning two core elements of FeedBlitz failed. We are currently working on restoring the service
Identified
Dec 25 · 8:25 AM FeedBlitzFeedBlitz is now working albeit slowly. We're now working on restoring full performance and identifying any missed mailings
Monitoring
Dec 25 · 9:00 AM FeedBlitzServices are now restored to full capacity. We are now working on sendng out any mailings that were missed during the outage
Resolved
Dec 25 · 9:54 AM FeedBlitzFeedBlitz 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.
Pattern
Test incident for training purposes - please ignore, we will reset this shortly.
Sep 10, 2026 · 8m
View incident →Currently unable to send emails and track engagement
Mar 11, 2026 · 9h 30m
View incident →Engagement data missing from UI and reports
Mar 7, 2026 · 3d 6h 2m
View incident →Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.