Minor incident

Bonterra & NGP VAN Incidents & Maintenance: CyberGrants: Issues with Credit Card Donations

Affected: CyberGrants

Current status of Bonterra & NGP VAN Incidents & Maintenance: Operational — live Bonterra & NGP VAN Incidents & Maintenance status

Timeline

1. Nov 2, 2026, 21:23 UTC
   investigating
   We are currently investigating an issue that is causing errors with credit card donations. We are reviewing this as a top priority and working to resolve as quickly as possible. Please monitor this page for updates.
2. Nov 2, 2026, 21:45 UTC
   investigating
   We are continuing to investigate the issue as a top-priority. Please continue to monitor this page for further updates.
3. Nov 2, 2026, 22:15 UTC
   investigating
   Our team continues to troubleshoot the issue and are working to remediate as soon as possible. Thank you for your continued patience. Please continue to monitor this page for further updates.
4. Nov 2, 2026, 22:46 UTC
   investigating
   We are continuing our investigation and we are working to resolve the issue as soon as possible. Please continue to monitor this page for further updates.
5. Nov 2, 2026, 23:16 UTC
   investigating
   Our team continues to troubleshoot the issue and are working to remediate as soon as possible. Thank you for your continued patience. Please continue to monitor this page for further updates.
6. Nov 2, 2026, 23:46 UTC
   identified
   We have identified the root cause of the issue and we are actively exploring solutions for remediation. Thank you for your continued patience. Please continue to monitor this page for further updates.
7. Nov 3, 2026, 00:18 UTC
   identified
   We are working to identify the needed solution for remediation. Thank you for your continued patience. Please continue to monitor this page for further updates.
8. Nov 3, 2026, 01:01 UTC
   identified
   Our team continues to evaluate remediation options, and the next update will be provided tomorrow morning. We sincerely apologize for the disruption and inconvenience this has caused, and we appreciate your patience. Please check this page for further information.
9. Nov 3, 2026, 13:19 UTC
   identified
   Our team is still working to identify a solution for remediation. We sincerely apologize for the continued impact and inconvenience this issue has caused. We appreciate your patience and encourage you to check this page for further information.
10. Nov 3, 2026, 14:01 UTC
    identified
    Our team continues to investigate this issue and evaluate remediation options. Thank you for your continued patience, and please check this page for further information.
11. Nov 3, 2026, 14:30 UTC
    identified
    Our team is still looking into this issue and exploring possible fixes. We appreciate your ongoing patience, and please check back on this page for more information.
12. Nov 3, 2026, 14:59 UTC
    identified
    Our team is actively investigating this issue and reviewing potential solutions. Thank you for bearing with us, and please check this page regularly for the latest updates.
13. Nov 3, 2026, 15:33 UTC
    identified
    Our team is still working through this issue and considering potential solutions. We truly appreciate your patience, and please check this page again soon for more information.
14. Nov 3, 2026, 16:00 UTC
    identified
    Our team remains focused on this issue and is exploring the best path to a resolution. Thank you for your continued understanding, and please keep an eye on this page for new information.
15. Nov 3, 2026, 16:30 UTC
    identified
    Our team is still working on this issue and evaluating the best path to a fix. Thank you for your patience, and please check back on this page for further updates.
16. Nov 3, 2026, 17:03 UTC
    identified
    We’re continuing to work on this issue and are focused on finding the most effective solution. Thank you for your patience, and please check this page for any additional updates.
17. Nov 3, 2026, 17:33 UTC
    identified
    Our team remains committed to resolving this issue and is working to identify the best solution. We appreciate your patience, and please check back on this page for the latest information.
18. Nov 3, 2026, 17:55 UTC
    identified
    Our team is still dedicated to resolving this issue and is working toward the right solution. Thank you for your patience, and please return to this page for the latest updates.
19. Nov 3, 2026, 18:30 UTC
    identified
    Our team is still addressing this issue and working to determine the best solution. Thank you for your continued patience, and please check this page again for any new updates.
20. Nov 3, 2026, 18:59 UTC
    identified
    Our team is continuing to research this issue and assess possible resolutions. We’re grateful for your patience, and please visit this page again for additional information.
21. Nov 3, 2026, 19:28 UTC
    identified
    Our team is still looking into this issue and exploring possible fixes. We appreciate your ongoing patience, and please check back on this page for more information.
22. Nov 3, 2026, 19:56 UTC
    identified
    Our team is continuing to look into this issue and assess possible resolutions. We’re grateful for your patience, and please visit this page again for additional information.
23. Nov 3, 2026, 20:29 UTC
    identified
    Our team remains focused on this issue and is exploring the best path to a resolution. Thank you for your continued understanding, and please keep an eye on this page for new information.
24. Nov 3, 2026, 20:54 UTC
    identified
    Our team is still hard at work on this issue and determining the best way to resolve it. We appreciate your understanding, and please check back on this page for any new information.
25. Nov 3, 2026, 21:25 UTC
    identified
    Our team is still addressing this issue and working to determine the best solution. Thank you for your continued patience, and please check this page again for any new updates.
26. Nov 3, 2026, 21:55 UTC
    identified
    Our team is still working to identify a solution for remediation. We sincerely apologize for the continued impact and inconvenience this issue has caused. We appreciate your patience and encourage you to check this page for further information.
27. Nov 3, 2026, 22:35 UTC
    identified
    We’re still working on the needed fix. We’re sorry for the ongoing disruption and appreciate your patience. Please check this page for updates.
28. Nov 3, 2026, 23:06 UTC
    identified
    We’re currently investigating potential fixes for this issue. We apologize for the ongoing inconvenience and appreciate your patience while we work toward a resolution. Please check back here for the latest updates.
29. Nov 3, 2026, 23:36 UTC
    identified
    Our team is continuing to investigate a resolution to this issue. We sincerely apologize for the disruption and appreciate your patience and understanding. Further updates will be posted on this page as they become available.
30. Nov 4, 2026, 00:00 UTC
    identified
    Our team remains focused on identifying a resolution to this issue. We apologize for the disruption this has caused and thank you for your patience and understanding. Please continue to check this page, where we will share further updates as soon as they are available.
31. Nov 4, 2026, 01:03 UTC
    identified
    Our team is currently testing a potential solution to this issue and will confirm once it has been validated. We apologize for the disruption this has caused and thank you for your continued patience and understanding. Further updates will be shared on this page as soon as they are available.
32. Nov 4, 2026, 01:37 UTC
    identified
    We are currently testing a proposed solution to this issue. We regret the disruption this has caused and appreciate your continued patience and understanding. Additional updates will be posted on this page as they become available.
33. Nov 4, 2026, 02:08 UTC
    identified
    Our team is currently evaluating a proposed solution to this issue. We apologize for the inconvenience and sincerely appreciate your patience and understanding. We will share additional updates on this page as soon as they are available.
34. Nov 4, 2026, 02:31 UTC
    identified
    We are currently testing a potential fix for this issue. We understand the disruption this has caused and apologize for the inconvenience. Thank you for your continued patience. Please check this page for further updates as they become available.
35. Nov 4, 2026, 03:13 UTC
    identified
    We are currently testing a potential fix for this issue. We understand the disruption this has caused and apologize for the inconvenience. Thank you for your continued patience. We will post our next update tomorrow morning.
36. Nov 4, 2026, 15:44 UTC
    monitoring
    A fix has been implemented and successfully tested, and credit card giving is now available to donors. We’ve also introduced a new update as part of this resolution. We’re continuing to monitor closely to ensure no further issues arise. Please keep an eye on the page for updates, and contact support if you notice any problems.
37. Nov 4, 2026, 20:41 UTC
    monitoring
    Update: Since the fix was implemented, credit card donations have been processing successfully throughout the day. Based on this, we're confident credit card donations are working as expected. We'll continue to monitor closely. If you see any issues, please contact Support. We sincerely apologize for the disruption and appreciate your patience
38. Nov 5, 2026, 22:29 UTC
    monitoring
    Credit card donations are processing normally. We believe the issue has been fully remediated, and we are continuing to monitor all activity closely. If you experience any problems, please contact Support. We sincerely apologize for the disruption and inconvenience this issue has caused, and we thank you for your patience.

Updates as published by Bonterra & NGP VAN Incidents & Maintenance (original).