All FE API endpoint FAILING

Alex Wong · January 20

@Erik Leaver I open this ticket already, please help: 020719732

I noticed the issue started yesterday 1/19/2026 9PM data sync. All FE API were failing. I tried it on the API console as well, it is failing.

HTTP/1.1 500 Internal Server Error


content-length: 149

content-type: application/problem+json


{

    "statusCode": 500,

    "message": "Internal server error",

    "activityId": "ef0723bf-50f7-46b5-a6be-e9e0f4453e0f",

    "status": 500,

    "title": "Internal server error"

}

I tried on both our org's production and test environment.

Erik Leaver · January 20

Hi @Alex Wong Thanks for flagging. Case looks like it's been resolved. Can you confirm?

Alex Wong · January 20

@Erik Leaver

Resolved for a ALLOUT FE complete fail. However, I am getting a lot of 502 and 503 Service Unavailable from RE API lokos like all center around Gift APIs

Alex Wong · January 20

a lot more gift error, but some constituent call to get error too.

Alex Wong · January 20

@Erik Leaver I am getting 50+ errors on various flow from data sync flow to webhook flow that get gift/constituent info just within the last hour. This is very bad. Let me know if you want me to open another ticket and send to you

Erik Leaver · January 20

Yeah, re-open the existing case (or create new). Status shows everything is up…

Alex Wong · January 20

this is only very small parts of the error i get from my error handling in the flow

Dennis Ladnier · January 20

I am confirming that I am also seeing sporadic (but frequent) 503 errors - started a few days ago.

Across multiple RE endpoints

Data Intelligence Consultant · January 20

@Erik Leaver Confirming that I have continued to see the 503's off and on all day today

Ken Swift · January 21

Our Aqueduct and SwiftGrants products rely heavily on the Sky APIs and have been receiving 503 errors for the past couple of days. Aqueduct has a lot of retry logic and sometimes has to retry 5 or 6 times before it's successful. Our clients are getting very anxious, since the Blackbaud Status page shows no issues, so it's difficult to convince them this a Blackbaud Sky API issue.

Erik Leaver · January 21

@Dennis Ladnier & @Data Intelligence Consultant @Ken Swift Please create cases for these issues - that way I can track and support can better see the breadth of impact. If you can, please include:

The exact date/time the user received the error
The exact error message you are receiving
The Endpoint you are attempting to call
The Environment ID of your authorized Blackbaud solution
The email address belonging to the Blackbaud account of the user attempting the call

David Hecht · January 21

I am also getting these same errors this morning. It is sporadic. Some of my smaller sematic models did get refreshed after several tries, but the larger ones keep failing. This is just one example and the specific API keeps changing.

Erik Leaver · January 21

@David Hecht please file a case & send me the number.

David Hecht · January 21

@Erik Leaver - Here is the case number:

020721853

Please let me know if you need anything else from me. Thanks for the help!

Data Intelligence Consultant · January 22

@Erik Leaver

Blackbaud Support Case 020724020

Erik Leaver · January 22

Thanks @Data Intelligence Consultant . Updates on the issue are on the status page. Working as hard as we can to resolve.

Alex Wong · January 22

@Erik Leaver it's day 3 now, I hope Blackbaud understand that this is as bad as full on RE outage at this point.

Alex Wong · January 22

@Erik Leaver the issue is no longer "intermittent". Every call to Get Gift on Developer Console is failing

David Hecht · January 23

@Erik Leaver I checked again this morning and continue to have failures. Just wanted to let you know. Thanks!

Erik Leaver · January 23

@David Hecht Unfortunately yes. I understand the severity of the issue and we will continue to post updates on status.blackbaud.com.

Dan Bonville · January 23

We are also encountering this issue on Constituent List queries with increasing regularity, certainly not "sporadic" at this point.

Any update or ETA could assist us with client communications.

Erik Leaver · January 23

@Dan Bonville Updates are on https://status.blackbaud.com . That's our official channel for providing updates to service incidents.

Data Intelligence Consultant · January 23

I see where BB posted to their overall status page that they made a configuration change and monitoring.

At least for me, my api calls are still seeing sporadic 503 failures

Erik Leaver · January 23

@Data Intelligence Consultant please update your ticket with that information.

There should also be an escalate button with cases that can be used

Data Intelligence Consultant · January 23

@Alex Wong are you still seeing the issues on your side? Thanks

Alex Wong · January 23

RE API is still failing significantly. The status page "update" does not mention the situation is being handled. It only sounds to me that BB added / made change in order to better detect the problem.

Data Intelligence Consultant · January 24

@Erik Leaver @Alex Wong last night and, so far, this morning I have seen no 503 errors - finger's crossed.

Alex Wong · January 24

Same here, working on restoring all sync

Data Intelligence Consultant · January 26

https://community.blackbaud.com/discussion/comment/310110#Comment_310110

ticket is updated

All FE API endpoint FAILING

Answers

Categories