GiveGab Enterprise Outage History

Started Oct 20, 2026, 06:25 PM UTC· resolved Oct 20, 2026, 06:26 PM UTC

1. investigating Oct 20, 2026, 06:25 PM UTC

   Test Only

2. resolved Oct 20, 2026, 06:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 07, 2026, 06:48 PM UTC· resolved Oct 07, 2026, 08:58 PM UTC

1. investigating Oct 07, 2026, 06:48 PM UTC

   We are currently investigating an issue that is preventing some users from accessing some NGP VAN Products. We are working as quickly as possible to resolve this and will share an update as soon as we have one.

2. monitoring Oct 07, 2026, 07:19 PM UTC

   As of 3:15 PM ET, we have mitigated the earlier issue that prevented some users from accessing some NGP VAN Products. We are continuing to monitor for any further issues.

3. resolved Oct 07, 2026, 08:58 PM UTC

   The earlier issue is resolved, we are continuing to monitor for any further issues.

Read the full incident report →

Started Sep 29, 2026, 07:06 PM UTC· resolved Sep 30, 2026, 12:57 PM UTC

1. identified Sep 29, 2026, 07:06 PM UTC

   We are currently addressing an issue that is preventing users from accessing organization records within NPO Hub. The root cause has been identified and we are working on a solution to remediate the issue. The needed fix is scheduled to be deployed within the next hour. Please monitor this page for further updates.

2. monitoring Sep 29, 2026, 07:35 PM UTC

   The needed fix has been successfully deployed and tested. While the issue has been remediated, we will monitor closely to ensure there is no regression. Please continue to monitor this page for further updates.

3. resolved Sep 30, 2026, 12:57 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 21, 2026, 02:33 PM UTC· resolved Sep 24, 2026, 07:46 PM UTC

1. investigating Sep 21, 2026, 02:33 PM UTC

   We have identified some disruption on certain forms and are actively investigating. We'll share updates here as we have more information. Next update will be posted at approximately 11:00 AM ET, if not sooner.

2. investigating Sep 21, 2026, 03:21 PM UTC

   We are continuing to review this issue as a top priority. Thank you for your patience and please continue to monitor this page for further updates. Next update will be posted at approximately 12:30 AM ET, if not sooner.

3. investigating Sep 21, 2026, 04:30 PM UTC

   Our team is actively working to resolve this issue and it remains our top priority. We appreciate your patience and ask that you continue to check this page for the latest updates. Our next update will be posted by approximately 1:30 PM ET, if not earlier.

4. identified Sep 21, 2026, 05:30 PM UTC

   We have identified the root cause of the issue and we are actively working on a solution. Thank you for your continued patience. Please continue to monitor this page for further updates. Next update will be posted at approximately 2:30 PM ET, if not sooner.

5. identified Sep 21, 2026, 06:36 PM UTC

   The root cause of this issue has been identified and we are taking immediate steps to implement a resolution. We appreciate your continued patience and ask that you monitor this page for the latest updates. Next update will be posted at approximately 3:30 PM ET, if not sooner.

6. identified Sep 21, 2026, 08:18 PM UTC

   We have found the source of this issue and are doing everything we can to get it resolved as quickly as possible. We appreciate your continued patience and ask that you monitor this page for the latest updates.

7. monitoring Sep 22, 2026, 12:26 PM UTC

   An update has been applied to address the disruption affecting certain forms. We are actively monitoring to ensure there is no regression. Please continue to monitor this page for further updates.

8. identified Sep 22, 2026, 02:21 PM UTC

   We have identified the root cause of this issue and are still actively working on the resolution. We appreciate your continued patience and ask that you monitor this page for the latest updates. Next update will be posted at approximately 11:30 AM ET, if not sooner."

9. identified Sep 22, 2026, 03:54 PM UTC

   We have identified the root cause of this issue and we are actively working toward a resolution. We thank you for your continued patience and encourage you to keep an eye on this page for the most up-to-date information. Our next update is expected by approximately 1:00 PM ET, or earlier if progress allows.

10. identified Sep 22, 2026, 05:03 PM UTC

    Our team is actively working on resolving this issue and continues to make progress toward a solution. We appreciate your patience and ask that you monitor this page for the latest updates. Our next update is expected by approximately 2:00 PM ET, or earlier if progress allows.

11. identified Sep 22, 2026, 05:58 PM UTC

    Our team continues to work diligently toward a resolution and is making steady progress on this issue. We thank you for your patience and encourage you to check this page regularly for the most current updates. Our next update is expected by approximately 3:00 PM ET, or earlier if progress allows.

12. identified Sep 22, 2026, 06:56 PM UTC

    Our team continues to work diligently toward a resolution and is making steady progress on this issue. We thank you for your patience and encourage you to check this page regularly for the most current updates. Our next update is expected by approximately 4:00 PM ET, or earlier if progress allows.

13. identified Sep 22, 2026, 08:16 PM UTC

    Our team is actively working on resolving this issue and continues to make progress toward a solution. We appreciate your patience and ask that you monitor this page for the latest updates. Our next update is expected by approximately 5:00 PM ET, or earlier if progress allows.

14. identified Sep 22, 2026, 09:01 PM UTC

    Our team remains engaged and is making progress toward resolving this issue. Please continue to monitor this page for updates.

15. identified Sep 23, 2026, 02:15 PM UTC

    Our team continues to work diligently toward a resolution and is making progress on this issue. We thank you for your patience and encourage you to check this page regularly for the most current updates. Our next update is expected by approximately 11:15 AM ET, or earlier if progress allows.

16. identified Sep 23, 2026, 03:34 PM UTC

    We are actively working toward a resolution. We thank you for your continued patience and encourage you to keep an eye on this page for the most up-to-date information. Our next update is expected by approximately 12:30 PM ET, or earlier if progress allows.

17. identified Sep 23, 2026, 04:53 PM UTC

    Our team is actively working on resolving this issue and continues to make progress toward a solution. We appreciate your patience and ask that you monitor this page for the latest updates. Our next update is expected by approximately 2:00 PM ET, or earlier if progress allows.

18. identified Sep 23, 2026, 06:01 PM UTC

    We are making steady progress toward a resolution and our team remains fully engaged in addressing this issue. We thank you for your continued patience and encourage you to check this page for the most current updates. Our next update is expected by approximately 3:00 PM ET, or earlier if progress allows.

19. identified Sep 23, 2026, 07:00 PM UTC

    We are actively working toward a resolution. We thank you for your continued patience and encourage you to keep an eye on this page for the most up-to-date information. Our next update is expected by approximately 4:00 PM ET, or earlier if progress allows.

20. identified Sep 23, 2026, 08:54 PM UTC

    Our team is actively working on resolving this issue and continues to make progress toward a solution. We appreciate your patience and ask that you monitor this page for the latest updates.

21. monitoring Sep 24, 2026, 04:21 PM UTC

    An update has been applied to address the disruption affecting certain forms. We are actively monitoring to ensure there is no regression. Please continue to monitor this page for further updates.

22. resolved Sep 24, 2026, 07:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Started Sep 03, 2026, 10:18 PM UTC· resolved Sep 03, 2026, 11:28 PM UTC

1. investigating Sep 03, 2026, 10:18 PM UTC

   We have identified an issue where Survey Response options for some Survey Questions are not displaying correctly in the Create a List page section. Our team is working as quickly as possible to resolve this and will share an update as soon as we can.

2. resolved Sep 03, 2026, 11:28 PM UTC

   As of 7:25pm eastern, the earlier issue where Survey Response options for some Survey Questions were not displaying correctly in the Create a List page section has been resolved. We are continuing to monitor for any further issues.

Read the full incident report →

Started Sep 03, 2026, 07:11 PM UTC· resolved Sep 04, 2026, 04:41 PM UTC

1. investigating Sep 03, 2026, 07:11 PM UTC

   We are aware that some users are currently experiencing slower than usual response times within the application, particularly on pages that rely on our API, such as Users/Roles, as well as with Alert Notifications. Our Engineering Team has identified the issue and is actively working on a resolution. We'll continue to post updates here as we learn more. We apologize for any inconvenience.

2. identified Sep 03, 2026, 07:40 PM UTC

   The root cause impacting Apricot slowness has been identified. A fix is scheduled to be deployed later this evening to remediate this issue. We apologize for any inconvenience. Please monitor this page for further updates.

3. monitoring Sep 04, 2026, 09:11 AM UTC

   A fix was deployed last evening. We will continue to monitor closely to ensure there is no further issues. Please continue to monitor this page for further updates.

4. resolved Sep 04, 2026, 04:41 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 03, 2026, 05:42 PM UTC· resolved Sep 03, 2026, 06:56 PM UTC

1. investigating Sep 03, 2026, 05:42 PM UTC

   We have identified an issue where omni-search, the search feature in the top-right of the interface, is not working for some Users. Our team is working as quickly as possible to resolve this and will share an update as soon as we can.

2. identified Sep 03, 2026, 06:43 PM UTC

   We have identified the issue causing omni-search, the search feature in the top-right of the interface, to not work for some Users and our team is working as quickly as possible to implement the solution. We will continue to provide updates as this work continues.

3. resolved Sep 03, 2026, 06:56 PM UTC

   As of 2:50pm eastern, the earlier issue where omni-search, the search feature in the top-right of the interface, was not working for some users has been resolved. We are continuing to monitor for any further issues

Read the full incident report →

Started Sep 01, 2026, 04:01 PM UTC· resolved Sep 01, 2026, 10:06 PM UTC

1. monitoring Sep 01, 2026, 04:01 PM UTC

   There is an external issue that may cause intermittent connection issues into a few Bonterra applications. We are monitoring very closely and we will post further updates as additional details become available.

2. resolved Sep 01, 2026, 10:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 31, 2026, 04:13 PM UTC· resolved Sep 02, 2026, 05:48 PM UTC

1. identified Aug 31, 2026, 04:13 PM UTC

   We have identified an issue where recurring commitments that processed over the weekend are not displaying on the front end of the database. We are working through the backlog now, and we expect that these records will be visible within the next 24 hours.

2. identified Sep 01, 2026, 06:29 PM UTC

   As previously communicated, we are continuing our work regarding recurring commitments that processed over the weekend but are not displaying on the front end of the database. While most records are now visible, we expect the remainder to finish throughout the day today and tomorrow morning, 9/2/26.

3. resolved Sep 02, 2026, 05:48 PM UTC

   All recurring commitments that previously were not displaying on the front end of the database are now updated and displaying as intended. We continue to monitor incoming settlements to ensure intended visibility.

Read the full incident report →

Started Aug 27, 2026, 01:18 PM UTC· resolved Aug 27, 2026, 05:22 PM UTC

1. investigating Aug 27, 2026, 01:18 PM UTC

   We are aware of an issue currently impacting performance in Cybergrants Sandbox. We understand the disruption this may cause and want to assure you that this is our top priority.

2. investigating Aug 27, 2026, 02:02 PM UTC

   We are continuing to investigate some remaining latency/slowness when performing searches on Sandbox. Please continue to monitor this page for further updates. We will provide another update around 10:30am EST

3. monitoring Aug 27, 2026, 02:35 PM UTC

   We have implemented a fix and have completed testing. While the issue has been addressed, we will continue to monitor to ensure there is no regression. Please continue to monitor this page for further updates.

4. resolved Aug 27, 2026, 05:22 PM UTC

   The incident has been successfully resolved.

Read the full incident report →

Started Aug 20, 2026, 08:17 PM UTC· resolved Aug 21, 2026, 02:04 PM UTC

1. monitoring Aug 20, 2026, 08:17 PM UTC

   At approximately 8 AM ET on 8/21/26, we will be performing a production update, which should take an hour to complete. During this window, some users may experience brief disruptions or slower performance. We are monitoring closely and expect minimal impact. Thank you for your patience.

2. resolved Aug 21, 2026, 02:04 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 17, 2026, 04:15 PM UTC· resolved Aug 17, 2026, 08:37 PM UTC

1. investigating Aug 17, 2026, 04:15 PM UTC

   We are actively investigating an issue that is causing general slowness and performance delays throughout the Apricot & ETO applications. This is a top priority and we are working to resolve as soon as possible. Please continue to monitor this page for further updates. Next update will be posted no later than 12:45 PM ET.

2. investigating Aug 17, 2026, 04:24 PM UTC

   We are continuing to investigate this issue.

3. investigating Aug 17, 2026, 04:47 PM UTC

   We are continuing our review to identify the root cause impacting Apricot & ETO general slowness and performance delays. This is a top priority and we are working to resolve as soon as possible. Please continue to monitor this page for further updates. Next update will be posted at approximately 1:15 PM ET, if not sooner.

4. monitoring Aug 17, 2026, 05:22 PM UTC

   We have implemented a fix and have completed testing. While the issue has been addressed, we will continue to monitor to ensure there is no regression. Please continue to monitor this page for further updates.

5. resolved Aug 17, 2026, 08:37 PM UTC

   The incident has been successfully resolved.

Read the full incident report →

Started Aug 13, 2026, 05:33 PM UTC· resolved Aug 14, 2026, 03:18 PM UTC

1. investigating Aug 13, 2026, 05:33 PM UTC

   We are currently investigating an issue that is preventing some charities from editing payee details within customer specific agency portals. This issue is not impacting NPO Hub, and it is also not impacting all charities or all customer specific agency portals. This is a top priority and we are working to resolve as quickly as possible. Please monitor this page for further updates.

2. investigating Aug 13, 2026, 06:46 PM UTC

   At this time, we are still investigating the issue to identify the root cause and needed solution. We apologize for any inconvenience and we are working to remediate as quickly as possible. Please continue to monitor this page for further updates.

3. investigating Aug 13, 2026, 07:30 PM UTC

   We are continuing our investigation as a top priority and we are working to resolve as soon as possible. Please continue to monitor this page for further updates.

4. identified Aug 13, 2026, 08:07 PM UTC

   The cause of the issue has been identified and we are currently preparing a solution that will be deployed later this evening, after 9 PM ET. We apologize for any inconvenience. Another update will be posted once this evening's deployment has been completed.

5. monitoring Aug 14, 2026, 02:04 AM UTC

   A fix has been successfully deployed and tested. While the issue has been resolved, and payee records can now be edited, we will continue to monitor closely to ensure there is no regression. We will post further updates tomorrow.

6. resolved Aug 14, 2026, 03:18 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 05, 2026, 07:54 PM UTC· resolved Aug 07, 2026, 10:10 PM UTC

1. investigating Aug 05, 2026, 07:54 PM UTC

   We are actively investigating an issue that is causing intermittent errors and slowness when accessing specific Apricot pages. We are reviewing this issue as a high priority and working to address as quickly as possible. Please monitor this page for further updates.

2. investigating Aug 05, 2026, 08:37 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 5:00 PM ET, if not sooner.

3. investigating Aug 05, 2026, 09:10 PM UTC

   Our team is still investigating the issue impacting Apricot performance and we are working to resolve it as soon as possible. Please continue to monitor this page for further updates.

4. investigating Aug 05, 2026, 10:12 PM UTC

   We are continuing our investigating into this issue and hoping to remediate as soon as possible. Please monitor this page for further updates.

5. identified Aug 05, 2026, 10:46 PM UTC

   The root cause of the issue has been identified and a solution is currently being prepared. The needed fix will be deployed no later than tomorrow morning to fully remediate the performance issues. Please continue to monitor this page for further updates.

6. identified Aug 06, 2026, 01:17 PM UTC

   We remain active with the implementation of the needed fix to remediate the issue. We appreciate your patience and ask that you continue to monitor this page for additional updates.

7. investigating Aug 06, 2026, 02:41 PM UTC

   An update was deployed to remediate the issue. While we are seeing some performance improvements, we are continuing to investigate the root cause to address further. Please monitor this page for further updates.

8. identified Aug 06, 2026, 07:57 PM UTC

   An additional fix is scheduled to be deployed this evening to assist with current performance issues. We appreciate your patience and ask that you continue to monitor this page for additional updates.

9. monitoring Aug 07, 2026, 03:36 PM UTC

   A fix was deployed last night to remediate the performance issues. While performance has returned to normal, we will continue to monitor closely to ensure there is no regression.

10. resolved Aug 07, 2026, 10:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Started Aug 05, 2026, 03:14 PM UTC· resolved Aug 05, 2026, 05:10 PM UTC

1. investigating Aug 05, 2026, 03:14 PM UTC

   We are currently investigating an issue with Results. It is being reviewed as a top priority and we are working to resolve as soon as possible. Please continue to monitor this page for further updates.

2. monitoring Aug 05, 2026, 03:17 PM UTC

   A fix has been implemented and Results is again accessible. We will continue to monitor closely to ensure there are no further issues. Please continue to monitor this page for further updates.

3. resolved Aug 05, 2026, 05:10 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 29, 2026, 05:16 PM UTC· resolved Jul 29, 2026, 06:43 PM UTC

1. investigating Jul 29, 2026, 05:16 PM UTC

   We are currently investigating an issue that is causing login errors for some Apricot users. We are reviewing this as a top priority and are working to resolve the issue as quickly as possible. Please monitor this page for further updates. Next update will be posted at approximately 1:45 PM ET, if not sooner.

2. investigating Jul 29, 2026, 05:46 PM UTC

   We are aware of an issue affecting login access for a limited number of Apricot users and are actively working to resolve it. Our team is treating this as a top priority. Please monitor this page for further updates. Next update will be posted at approximately 2:15 AM ET, if not sooner.

3. monitoring Jul 29, 2026, 06:02 PM UTC

   We have implemented a fix and have completed testing. While the issue has been addressed, we will continue to monitor to ensure there is no regression. Please continue to monitor this page for further updates.

4. resolved Jul 29, 2026, 06:43 PM UTC

   The incident has been successfully resolved.

Read the full incident report →

Started Jul 29, 2026, 03:45 PM UTC· resolved Jul 29, 2026, 06:54 PM UTC

1. identified Jul 29, 2026, 03:45 PM UTC

   CyberGrants is currently experiencing an issue that is preventing watchlist scanning from executing. In order to remediate the issue, a component of the application will need to be restarted. Since this is a core function, we will be restarting the applicable component at 12:15 PM ET and it should take approximately 5 - 10 minutes to complete. During this time, CyberGrants will be offline. We apologize for any inconvenience. Please monitor this page for further updates.

2. monitoring Jul 29, 2026, 04:23 PM UTC

   CyberGrants has been been restarted and the watchlist scanning has resumed. We will continue to monitor closely to ensure there is no regression. Please continue to monitor this page for further updates.

3. resolved Jul 29, 2026, 06:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 29, 2026, 02:42 PM UTC· resolved Jul 29, 2026, 04:34 PM UTC

1. investigating Jul 29, 2026, 02:42 PM UTC

   We are currently investigating an issue that is preventing some users from logging into their databases. We are working as quickly as possible to resolve this and will share an update as soon as we have one.

2. investigating Jul 29, 2026, 04:07 PM UTC

   We are continuing to investigate the issue affecting navigation and login for some users. We will share an update as soon as we have one.

3. monitoring Jul 29, 2026, 04:32 PM UTC

   As of 12:18PM ET, we have resolved the earlier issue that prevented some users from accessing the database. We are continuing to monitor for any further issues.

4. resolved Jul 29, 2026, 04:34 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 24, 2026, 01:21 PM UTC· resolved Jul 24, 2026, 07:26 PM UTC

1. investigating Jul 24, 2026, 01:21 PM UTC

   We are currently investigating an issue that is impacting some customers from accessing the Payment Section within request records. We are reviewing this as a top priority and are working to resolve as quickly as possible. Please monitor this page for updates.

2. investigating Jul 24, 2026, 01:33 PM UTC

   As part of our investigation, we have identified that the issue is impacting multiple sections within request records, which includes both accessing and display of specific sections. Please continue to monitor this page for further updates.

3. identified Jul 24, 2026, 01:49 PM UTC

   We have identified the root cause of the issue and we are actively working on a solution. Thank you for your continued patience. Please continue to monitor this page for further updates.

4. identified Jul 24, 2026, 02:15 PM UTC

   The root cause of this issue has been identified and we are taking immediate steps to implement a resolution. We appreciate your continued patience and ask that you monitor this page for the latest updates. Next update will be posted at approximately 10:45 AM ET, if not sooner.

5. identified Jul 24, 2026, 02:45 PM UTC

   We have found the source of this issue and are doing everything we can to get it resolved as quickly as possible. We appreciate your continued patience and ask that you monitor this page for the latest updates. Next update will be posted at approximately 11:15 AM ET, if not sooner.

6. identified Jul 24, 2026, 02:52 PM UTC

   At approximately 11:15 AM ET, we will be deploying a fix to remediate the issue. During this time, there may be a brief impact to CyberGrants performance. We apologize for any further inconvenience. Please continue to monitor this page for further updates.

7. monitoring Jul 24, 2026, 03:21 PM UTC

   We have implemented a fix and have completed testing. While the issue has been addressed, we will continue to monitor to ensure there is no regression. Please continue to monitor this page for further updates.

8. monitoring Jul 24, 2026, 04:54 PM UTC

   At approximately 1:00 PM ET, we will be deploying an additional update to remediate a formatting issue. During this time, there may be a brief impact to CyberGrants performance. We apologize for any further inconvenience. Please continue to monitor this page for further updates.

9. monitoring Jul 24, 2026, 05:34 PM UTC

   At this time, all identified issues have been addressed, but we will continue to monitor to ensure there is no regression. Please continue to monitor this page for further updates.

10. resolved Jul 24, 2026, 07:26 PM UTC

    The incident has been successfully resolved.

11. postmortem Jul 31, 2026, 04:18 PM UTC

    **Issue Summary:** On July 24th, 2026, the CyberGrants application was erroring on some requests. This increased error rate was due to a recent deployment that changed some number formatting functions causing some numbers to be formatted incorrectly or produce an error. **Root Cause:** CyberGrants application deploy updated a formatting function that in some edge cases caused errors or incorrect formats. **Prevention:** * **Short-term:** We deployed a hotfix to the code to update the function. * **Long-term:** We are reviewing automated testing to ensure edge cases are covered.

Read the full incident report →

Started Jul 23, 2026, 03:15 PM UTC· resolved Jul 23, 2026, 03:24 PM UTC

1. investigating Jul 23, 2026, 03:15 PM UTC

   We are currently investigating an issue that is causing users to not be able to access mobilize.us. We are working as quickly as possible to resolve this and will share an update as soon as we have one.

2. resolved Jul 23, 2026, 03:24 PM UTC

   As of 11:22 AMET, we have resolved the earlier issue that caused users to not be able to access mobilize.us. We are continuing to monitor for any further issues.

Read the full incident report →

Started Jul 21, 2026, 02:26 PM UTC· resolved Jul 21, 2026, 07:17 PM UTC

1. 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.

2. 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.

3. 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.

4. 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.

5. resolved Jul 21, 2026, 07:17 PM UTC

   This incident has been resolved.

6. 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.

Read the full incident report →

Started Jul 20, 2026, 01:30 PM UTC· resolved Jul 20, 2026, 09:12 PM UTC

1. investigating Jul 20, 2026, 01:30 PM UTC

   We are currently investigating an issue that is causing an error when running saved one-click reports within CyberGrants. We apologize for any impact and inconvenience caused, and we are reviewing this as a top priority. Please note, the issue appear to be related to saved one-click reports, so new reports can be configured and generated without issue. Please monitor this page for further updates.

2. investigating Jul 20, 2026, 02:01 PM UTC

   We are continuing to review this issue as a top priority. Thank you for your patience and please continue to monitor this page for further updates. Next update will be posted at approximately 10:30 AM ET, if not sooner.

3. investigating Jul 20, 2026, 02:32 PM UTC

   We are actively working on this and it remains our top priority. We appreciate your patience during this time. Please continue to check this page for updates. Next update will be posted at approximately 11:00 AM ET, if not sooner.

4. investigating Jul 20, 2026, 03:03 PM UTC

   We continue to investigate this priority issue and we are working to remediate it as soon as possible. Please continue to monitor this page for further updates. Next update will be posted at approximately 11:30 AM ET, if not sooner.

5. investigating Jul 20, 2026, 03:30 PM UTC

   We are actively investigating this issue and working diligently toward a resolution. We appreciate your patience and ask that you check back on this page for the latest updates. Next update will be posted at approximately 12:00 PM ET, if not sooner.

6. investigating Jul 20, 2026, 04:00 PM UTC

   We are continuing to investigate this issue and are committed to resolving it as quickly as possible. We appreciate your patience and ask that you check back on this page for the latest updates. Next update will be posted at approximately 12:30 PM ET, if not sooner.

7. identified Jul 20, 2026, 04:35 PM UTC

   We have identified the root cause of the issue and we are actively working on a solution. Thank you for your continued patience. Please continue to monitor this page for further updates. The next update will be posted at approximately 1:00 PM ET, if not sooner.

8. identified Jul 20, 2026, 05:02 PM UTC

   The root cause has been identified and a solution is actively underway. Thank you for your patience, please continue to check this page for updates. Next update will be posted at approximately 1:30 PM ET, if not sooner.

9. identified Jul 20, 2026, 05:33 PM UTC

   We are actively working on the solution to remediate the issue. Please continue to check this page for further updates. Next update will be posted at approximately 2:00 PM ET, if not sooner.

10. identified Jul 20, 2026, 05:58 PM UTC

    Work to resolve this issue is actively in progress and we are focused on getting this fixed as quickly as possible. Please check back on this page for updates. Next update expected by 2:30 PM ET, or earlier if available.

11. identified Jul 20, 2026, 06:36 PM UTC

    We continue to work on the needed fix to resolve this issue. It remains a top priority and we appreciate your patience. As a reminder, new ad hoc/one-click reports can be configured as an immediate workaround solution, while we continue to address the issue impacting the saved reports. Please continue to check this page for further updates. Next update will be posted at approximately 2:30 PM ET, if not sooner.

12. monitoring Jul 20, 2026, 07:04 PM UTC

    We have implemented and tested a fix to remediate the issue. Saved one-click reports are now working as expected and we will continue to monitor closely to ensure there is no regression. Please continue to monitor this page for further updates.

13. resolved Jul 20, 2026, 09:12 PM UTC

    This incident has been resolved.

14. postmortem Aug 03, 2026, 01:42 PM UTC

    **Issue Summary:** On July 20th, 2026, the CyberGrants application was erroring on some requests related to reports. This increased error rate was due to a service failing to restart, compounded by an internal only certificate expiring preventing auto-restart. **Root Cause:** One of the back-end reporting servers failed, and the auto-restart feature also failed due to a recently expired internal-only certificate. The certificate was updated and service restarted as expected. **Prevention:** * **Short-term:** Back-end certificate was updated with a longer life. * **Long-term:** We are updating the certificate inventory to ensure this is not missed in the future.

Read the full incident report →

Started Jul 16, 2026, 04:01 PM UTC· resolved Jul 16, 2026, 04:17 PM UTC

1. investigating Jul 16, 2026, 04:01 PM UTC

   We are currently investigating an issue that is causing some users to be unable to access the database. We are working as quickly as possible to resolve this and will share an update as soon as we have one.

2. resolved Jul 16, 2026, 04:17 PM UTC

   As of 12:12PM ET, we have resolved the earlier issue that caused some users to be unable to access the database. We are continuing to monitor for any further issues.

Read the full incident report →

Started Jul 13, 2026, 12:02 PM UTC· resolved Jul 13, 2026, 07:03 PM UTC

1. investigating Jul 13, 2026, 12:02 PM UTC

   We are aware of an issue affecting areas of the CyberGrants platform. Some users are experiencing errors when accessing certain features. Our team is actively investigating and working to resolve the issue.

2. investigating Jul 13, 2026, 12:32 PM UTC

   We are continuing to investigate this issue with the highest priority.

3. investigating Jul 13, 2026, 01:00 PM UTC

   We are actively investigating this issue as a top priority. Please continue to monitor this page for further updates.

4. investigating Jul 13, 2026, 01:30 PM UTC

   We are continuing to investigate this issue as a top priority. Please continue to monitor this page for further updates.

5. investigating Jul 13, 2026, 02:00 PM UTC

   We are actively investigating this issue as a top priority. Please continue to monitor this page for further updates.

6. investigating Jul 13, 2026, 02:31 PM UTC

   We are continuing to investigate this issue as a top priority. Please continue to monitor this page for further updates.

7. investigating Jul 13, 2026, 03:01 PM UTC

   We are actively investigating this issue as a top priority. Please continue to monitor this page for further updates.

8. investigating Jul 13, 2026, 03:31 PM UTC

   We are actively exploring a few options to remediate the issue that is impacting current CyberGrants performance. We are engaged with our external partner Oracle for support, but we are also going to restart specific CyberGrants components that is going to require CyberGrants to be offline. Within the next 30 minutes, CyberGrants will be offline for approximately 20 minutes. We apologize for the inconvenience and appreciate your patience as we work to address this priority issue.

9. investigating Jul 13, 2026, 04:02 PM UTC

   We are in the process of taking CyberGrants offline. It has been slightly delayed, but the downtime should begin within the next 30 minutes. Thank you for your continued patience. We will provide our next status update at approximately 12:30 PM ET.

10. investigating Jul 13, 2026, 04:32 PM UTC

    CyberGrants is currently offline. We are actively restarting the system which should take approximately 20 minutes. We apologize for the inconvenience and appreciate your patience as we work to address this priority issue. We will provide our next status update at approximately 1:00 PM ET.

11. monitoring Jul 13, 2026, 04:47 PM UTC

    CyberGrants is back online and we have completed testing. At this time, they system is performing as expected, but we will continue to monitor closely to ensure there is no regression.

12. resolved Jul 13, 2026, 07:03 PM UTC

    This incident has been resolved.

13. postmortem Jul 14, 2026, 01:13 PM UTC

    **Issue Summary:** Between July 12th and 13th, 2026, the search functionality within CyberGrants was unavailable. Users were unable to search for grants, organizations or Applications, and some automated background processes e.g. file imports, also failed. The issue began at approximately 3:51 AM ET on July 12th and was resolved by 12:35 PM ET on July 13th 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 text search engine \(a component owned and maintained by Oracle\) caused the search service to fail. Specifically, Oracle’s internal process responsible for handling search queries crashed due to a defect in Oracle’s own proprietary software code. Once in this failed state, any operation that relied on text-based search, including grant searches, organization lookups, and certain automated imports, returned errors until the database was restarted. 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. Any background jobs that failed during the outage were identified and reprocessed successfully. * **Short-term:** We have opened a support case with Oracle to obtain a permanent software patch that addresses this defect. * **Long-term:** We are implementing additional monitoring to detect any future search service failures within minutes of them occurring, enabling our team to respond before users are significantly impacted. We're also reviewing our database configuration with Oracle to identify any settings that may further reduce the likelihood of this defect being triggered in the first place.

Read the full incident report →

Started Jul 11, 2026, 02:07 PM UTC· resolved Jul 11, 2026, 04:22 PM UTC

1. investigating Jul 11, 2026, 02:07 PM UTC

   We are aware that some users are experiencing issues logging into Apricot. Our team is actively investigating the root cause and will provide updates as more information becomes available. We apologize for any disruption this may cause.

2. monitoring Jul 11, 2026, 02:34 PM UTC

   The login issue affecting Apricot has been resolved. Our team will continue to monitor to ensure everything remains stable.

3. resolved Jul 11, 2026, 04:22 PM UTC

   This incident has been resolved.

Read the full incident report →