CyberGrants: Error with Saved One Click Reports

Update timeline

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.