GiveGab Enterprise incident

CyberGrants: Reported Performance Issues

Resolved after 3 hours 39 minutes, affecting CyberGrants, on May 4, 2026.

postmortem May 07, 2026, 02:11 PM UTC

**Issue Summary:** On May 4th, 2026, when an email campaign was sent with call to action the event search pages were slow to respond and timed out in some cases. **Root Cause:** An edge case in the event configuration was identified that caused the SQL execution plan to be very costly. The increased load on the system in conjunction with the slow query plan caused slowness/timeouts. **Prevention:** Short term, we vertically scaled the database, and also altered the event configuration slightly to help optimize the query. As for a permanent solution we are working to ensure that this edge case is covered correctly by the query optimizer. That may involve altering the query used by the application and/or adding covering indexes to ensure the query optimizer picks the best plan.

Started
May 04, 2026, 03:05 PM UTC
Resolved
May 04, 2026, 06:45 PM UTC
Duration
3h 39m
Detected by Pingoru
May 04, 2026, 03:05 PM UTC

Affected components

CyberGrants

Update timeline

  1. investigating May 04, 2026, 03:05 PM UTC

    We are currently reviewing an issue that is causing delays/latency issues with CyberGrants. This is a top priority and we are actively working to remediate as soon as possible. Please monitor this page for further updates.

  2. monitoring May 04, 2026, 04:22 PM UTC

    We have completed an update to address the delay/latency issue. We will continue to monitor to ensure there are no further issues. Please continue to monitor this page for further updates.

  3. resolved May 04, 2026, 06:45 PM UTC

    This incident has been resolved.

  4. postmortem May 07, 2026, 02:11 PM UTC

    **Issue Summary:** On May 4th, 2026, when an email campaign was sent with call to action the event search pages were slow to respond and timed out in some cases. **Root Cause:** An edge case in the event configuration was identified that caused the SQL execution plan to be very costly. The increased load on the system in conjunction with the slow query plan caused slowness/timeouts. **Prevention:** Short term, we vertically scaled the database, and also altered the event configuration slightly to help optimize the query. As for a permanent solution we are working to ensure that this edge case is covered correctly by the query optimizer. That may involve altering the query used by the application and/or adding covering indexes to ensure the query optimizer picks the best plan.

Your product runs on more than GiveGab Enterprise

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →