Benevity incident

Intermittent Unavailability and Degraded Page Load Time for Community Investment Essential (formerly Benevity Grants)

Minor Resolved View vendor source →

Benevity experienced a minor incident on February 24, 2025 affecting Grants Essential (formerly Benevity Grants), lasting 3d 8h. The incident has been resolved; the full update timeline is below.

Started
Feb 24, 2025, 09:18 PM UTC
Resolved
Feb 28, 2025, 06:03 AM UTC
Duration
3d 8h
Detected by Pingoru
Feb 24, 2025, 09:18 PM UTC

Affected components

Grants Essential (formerly Benevity Grants)

Update timeline

  1. investigating Feb 24, 2025, 09:18 PM UTC

    We are currently experiencing degraded page load times and intermittent unavailability of CI Essential (formerly Benevity Grants). Benevity's Engineering and DevOps teams are investigating.

  2. monitoring Feb 24, 2025, 09:35 PM UTC

    All Community Investment - Essential Client sites are available and we are now seeing normal page load times. We are continuing to monitor for any further issues or recurrences.

  3. resolved Feb 28, 2025, 06:03 AM UTC

    This incident has been resolved.

  4. postmortem Mar 31, 2025, 11:43 PM UTC

    ### Summary On February 24, 2025, the Community Investment Essentials \(Benevity Grants\) platform experienced intermittent service disruptions starting at 3:14 PM EST. The issue was fully resolved, and normal service operation was restored by 4:30 PM EST. ### Impact During this period, some clients experienced intermittent access to the Community Investment Essentials platform. ### Root Cause The service disruption was caused by an overload of the unique submission validation check for applications. During a period of increased activity, this validation process became overwhelmed, leading to temporary service disruptions. ### Future Mitigation To prevent further disruptions, we optimized the application submission validation process to handle higher volumes of activity. This improvements will ensure greater stability and reliability, even during peak usage periods. ### Timeline of Events * Feb 24, 2025 at 3:14 PM EST - Initial alert received * Feb 24, 2025 at 3:49 PM EST - Issue identified * Feb 24, 2025 at 4:04 PM EST - Mitigation process started * Feb 24, 2025 at 4:30 PM EST - Incident resolved