Resolved after 4 hours 50 minutes, affecting CyberGrants, on July 21, 2026.
**Issue Summary:** On July 21st, 2026, the CyberGrants application experienced a service disruption between approximately 10:10 AM ET and 12:00 PM ET. During this period, some users may have experienced errors or been unable to access certain application features. The issue was resolved following a database restart. No customer data was lost or corrupted. **Root Cause:** CyberGrants uses Oracle as its database platform. A bug within Oracle's database engine \(a component owned and maintained by Oracle\) triggered a flood of internal errors that overwhelmed the database's diagnostic subsystem, ultimately causing the database to crash. On attempting to restart, residual memory corruption from the crash required an additional restart cycle to clear. This is a confirmed Oracle product defect, not an issue with the CyberGrants application code or Bonterra infrastructure. No system changes were made by Bonterra prior to the failure occurring. **Prevention:** * **Immediate:** We restarted the database to clear the failed state and verified all data remained intact. Downstream data replication processes were monitored through recovery and were confirmed to be operationally correct. * **Short-term:** We have opened a high-severity support case with Oracle to obtain a permanent software patch that addresses this defect. * **Long-term:** We are implementing enhanced monitoring to detect early warning signs of this type of failure \(abnormal internal error rates and diagnostic file growth\), enabling our team to intervene before users are significantly impacted. We are also working with Oracle to identify configuration changes or patches that will prevent this defect from being triggered in the first place. * **n.b.:** This is the second issue in the space of 8 days which has been caused by Oracle Database bugs. As a result, and in addition to the measures above, we are reviewing the architecture of the Oracle DB within AWS and exploring an option to fundamentally change it and thus making it more robust.
Affected components
Update timeline
- investigating Jul 21, 2026, 02:26 PM UTC
CyberGrants is currently not accessible. We are investigating this as the highest priority and we are working to resolve as quickly as possible. Please monitor this page for further updates.
- investigating Jul 21, 2026, 02:59 PM UTC
We are actively reviewing this issue and it remains our top priority. We appreciate your patience and ask that you continue to monitor this page for the latest information. Our next update will be posted by approximately 11:30 AM ET, if not sooner.
- investigating Jul 21, 2026, 03:33 PM UTC
We are continuing to investigate this issue. We appreciate your patience and ask that you continue to monitor this page for the latest information. Our next update will be posted by approximately 12:00 PM ET, if not sooner.
- monitoring Jul 21, 2026, 04:04 PM UTC
A fix has been implemented and tested. CyberGrants is now accessible, but we will continue to monitor closely to ensure there is no regression.
- resolved Jul 21, 2026, 07:17 PM UTC
This incident has been resolved.
- postmortem Jul 22, 2026, 12:59 PM UTC
**Issue Summary:** On July 21st, 2026, the CyberGrants application experienced a service disruption between approximately 10:10 AM ET and 12:00 PM ET. During this period, some users may have experienced errors or been unable to access certain application features. The issue was resolved following a database restart. No customer data was lost or corrupted. **Root Cause:** CyberGrants uses Oracle as its database platform. A bug within Oracle's database engine \(a component owned and maintained by Oracle\) triggered a flood of internal errors that overwhelmed the database's diagnostic subsystem, ultimately causing the database to crash. On attempting to restart, residual memory corruption from the crash required an additional restart cycle to clear. This is a confirmed Oracle product defect, not an issue with the CyberGrants application code or Bonterra infrastructure. No system changes were made by Bonterra prior to the failure occurring. **Prevention:** * **Immediate:** We restarted the database to clear the failed state and verified all data remained intact. Downstream data replication processes were monitored through recovery and were confirmed to be operationally correct. * **Short-term:** We have opened a high-severity support case with Oracle to obtain a permanent software patch that addresses this defect. * **Long-term:** We are implementing enhanced monitoring to detect early warning signs of this type of failure \(abnormal internal error rates and diagnostic file growth\), enabling our team to intervene before users are significantly impacted. We are also working with Oracle to identify configuration changes or patches that will prevent this defect from being triggered in the first place. * **n.b.:** This is the second issue in the space of 8 days which has been caused by Oracle Database bugs. As a result, and in addition to the measures above, we are reviewing the architecture of the Oracle DB within AWS and exploring an option to fundamentally change it and thus making it more robust.
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.
Amazon Web Services