FeedBlitz Status · History · Incident #63906

RESOLVED

System-wide outage

Critical · Started Dec 25, 2025 · 8:20 AM

  • Duration

    1h 33m

  • Severity

    Critical

  • Detection lead

  • User reports

Summary

System-wide 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.


  • Started

    Dec 25, 2025 · 8:20 AM

  • Resolved

    Dec 25, 2025 · 9:54 AM

  • Duration

    1h 33m

  • Severity

    Critical

Event timeline

How this incident unfolded

  • Investigating

    Dec 25 · 8:20 AM FeedBlitz

    At 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 FeedBlitz

    FeedBlitz is now working albeit slowly. We're now working on restoring full performance and identifying any missed mailings

  • Monitoring

    Dec 25 · 9:00 AM FeedBlitz

    Services 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 FeedBlitz

    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.

Get alerted before the next FeedBlitz outage.

Pulsetic catches degradations minutes before vendors acknowledge them.