Blackbaud incident

Active Issue Alert – Blackbaud CRM - 000662530

Minor Resolved View vendor source →

Blackbaud experienced a minor incident on March 6, 2026 affecting Blackbaud CRM™, lasting 18d 2h. The incident has been resolved; the full update timeline is below.

Started
Mar 06, 2026, 05:05 PM UTC
Resolved
Mar 24, 2026, 07:12 PM UTC
Duration
18d 2h
Detected by Pingoru
Mar 06, 2026, 05:05 PM UTC

Affected components

Blackbaud CRM™

Update timeline

  1. investigating Mar 06, 2026, 05:05 PM UTC

    We have identified an issue impacting a subset 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 Mar 06, 2026, 05:13 PM UTC

    We have identified an issue impacting a subset 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.

  3. identified Mar 06, 2026, 05:33 PM UTC

    We are currently experiencing an issue affecting a subset of Blackbaud CRM customers. Users may encounter 401 errors when attempting to make SOAP API calls to BBCRM. Our engineers are diagnosing the event and working to resolve it. Please continue to reference this page for updates.

  4. identified Mar 06, 2026, 06:31 PM UTC

    We are currently experiencing an issue affecting a subset of Blackbaud CRM customers. Users may encounter 401 errors when attempting to make SOAP API calls to BBCRM. Our engineers are diagnosing the event and working to resolve it. Please continue to reference this page for updates.

  5. identified Mar 06, 2026, 07:02 PM UTC

    We are currently experiencing an issue affecting a subset of Blackbaud CRM customers. Users may encounter 401 errors when attempting to make SOAP API calls to BBCRM. Our engineers are diagnosing the event and working to resolve it. Please continue to reference this page for updates.

  6. resolved Mar 24, 2026, 07:12 PM UTC

    This incident has been resolved.