Constituent API returns 503 consistently since 5/13

In several of my client's environments we have been receiving 503 “service unavailable” errors in much higher rates since last Friday. This is specifically on endpoints of the Constituent API (i.e. phones, constituents, constituent codes, etc.). These requests have been running around 4 to 5 am EST.

Categories