Blackbaud incident

Active Issue Alert -Raisers Edge 000661074

Notice Resolved View vendor source →

Blackbaud experienced a notice incident on February 26, 2026 affecting Blackbaud Luminate Online® and Raiser's Edge®, lasting 1h 34m. The incident has been resolved; the full update timeline is below.

Started
Feb 26, 2026, 04:10 PM UTC
Resolved
Feb 26, 2026, 05:44 PM UTC
Duration
1h 34m
Detected by Pingoru
Feb 26, 2026, 04:10 PM UTC

Affected components

Blackbaud Luminate Online®Raiser's Edge®

Update timeline

  1. investigating Feb 26, 2026, 04:10 PM UTC

    We have identified an issue impacting some of our customers causing errors when attempting to log in or use features within the affected service. Our engineers are diagnosing the event and working to resolve it for you as quickly as possible. Please continue to reference this page for updates.

  2. investigating Feb 26, 2026, 04:12 PM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 26, 2026, 04:16 PM UTC

    We are continuing to investigate this issue.

  4. investigating Feb 26, 2026, 04:21 PM UTC

    A subset of customers are receiving the message "Error saving records" when trying to import or process a global change for constituent data. Our engineers are investigating the issue and working to resolve it for you as quickly as possible. Please continue to reference this page for updates.

  5. identified Feb 26, 2026, 05:03 PM UTC

    A subset of customers are receiving the message "Error saving records" when trying to import or process a global change for constituent data. Our engineers are investigating the issue and working to resolve it for you as quickly as possible. Please continue to reference this page for updates.

  6. monitoring Feb 26, 2026, 05:37 PM UTC

    A subset of customers are receiving the message "Error saving records" when trying to import or process a global change for constituent data. Our engineers are investigating the issue and working to resolve it for you as quickly as possible. Please continue to reference this page for updates.

  7. resolved Feb 26, 2026, 05:44 PM UTC

    This incident has been resolved.