chariot - Notice history

Between 4:04pm EST and 4:54pm EST, some donors using DAFpay were unable to start a donation due to a CORS error on our API. The issue was caused by an internal infrastructure change that removed the host responsible for responding to HTTP OPTIONS preflight requests. A fix was deployed and DAFpay service is fully restored. No donor data was affected.

This incident has been resolved. We are continuing to work to improve the resiliency and availability of our systems.

Between March 6 2:41PM EST and March 18 4:23PM EST, a subset of grant requests submitted by donors via DAFpay were not being correctly submitted to the DAF providers but were being recorded as successful on our end. This affected one major DAF provider.

This was due to a failure in our system which validated successful completion criteria of submitted DAFpay grant requests.

We mitigated the incident by temporarily disabling the DAF provider while our team worked on a fix. The fix was deployed shortly after and was confirmed to be effective.

We are working to strengthen our end-to-end validation to ensure grant requests are not marked successful unless positively confirmed by the DAF provider.

If your organization was impacted, our team will follow up directly with specific details and any actions required.

We've identified the impacted grants which includes a subset of DAFpay grant submissions since March 6 at 2:41PM.

We've identified an issue with DAFpay grant submissions affecting a major DAF provider.

We have disabled the DAF provider within DAFpay to stop the issue.

We are actively investigating the root cause.