Is Virtuous down?

According to our monitoring system this service has become unresponsive, we’re investigating.

Service is back up.

We have detected an issue with one of our payment processors, Stripe, that is impacting ACH processing for a subset of customers, and we are currently investigating. We’ll update you soon.

We have determined that the current ACH issue is related to a Stripe disruption affecting a subset of customers. Our engineering team is working closely with Stripe to resolve this issue ASAP. We will continue to share updates as we have more information.

We have identified the issue as affecting manual ACH payment entry through our payment provider, Stripe. As a temporary mitigation, we have disabled manual ACH entry. Donors can continue to make ACH donations by securely logging into their bank account during checkout. Our engineering team is actively working with Stripe to resolve the issue. We will provide additional updates as soon as more information becomes available.

Stripe has resolved the issue affecting manual ACH payment entry, and we have re-enabled this feature. Donors can now submit ACH payments using either manual bank account entry or bank login. Our team will continue to closely monitor the experience to ensure everything is functioning as expected. We will provide additional updates if needed.

We continue to see elevated error rates affecting manual ACH payment entry on the Raise platform. Our team is actively investigating the issue. At this time, Virtuous Giving is operating normally and is not impacted. We will continue to provide updates as more information becomes available.

We have worked with Stripe to find a resolution and a fix has been deployed to address the issues with manual ACH processing. Manual ACH entry is now an available option on forms again.

According to our monitoring system this service has become unresponsive, we’re investigating.

Our engineering team continues to investigate the issue that is causing connectivity issues to the application. We have no yet identified the root cause. We will provide another update once we do. We appreciate your patience.

We have determined that the current CRM+ availability issue is related to Azure service disruption affecting connectivity to our environment. This impact has affected access to the CRM+ web application and API. Our engineering team continues working through the issue. We will continue to share updates as we have more information.

We have confirmed this issue is related to an Azure service disruption. Our engineering team is actively working with Azure and is also executing a recovery plan to move the application to an unaffected Azure region. Recovery time for that path is approximately 45 minutes.

While our original recovery plan was to move the application to an unimpacted region, Azure has since confirmed a broader networking incident. Based on the latest information provided by Azure, the issue extends beyond the web application itself and is affecting underlying Azure services we depend on, including storage and SQL. As a result, moving the web application to another region has not fully restored service while those dependencies remain impacted. The new application instance is up and running, but it is unable to connect to the storage account that provides the authentication keys. We apologize for the continued disruption. With this new information we are no longer able to provide an estimated time to recovery. We are evaluating additional options and will share another update shortly.

Since our last update, the CRM web application has been moved to the new region as part of our effort to bypass the Azure outage. Our team is now actively working through the remaining storage account dependencies required to restore service fully. Once storage access is confirmed, we will be able to determine whether SQL connectivity is also impacted. We continue to work closely with Azure as we evaluate the remaining recovery steps. We apologize for the continued disruption. We do not yet have an estimated time to recovery and will share another update as soon as we have more information.

The Azure team has shared that they identified a recent change strongly correlated with the connectivity incident and have initiated rollback actions. They have also indicated that service telemetry is beginning to show signs of recovery. CRM+ service now appears to be back online, and we are continuing to monitor the application closely as Azure recovery actions progress. Our team is validating stability across affected services before we confirm full resolution. We appreciate your patience throughout this incident and will share another update soon.

Service has remained stable, and we are now considering this incident resolved. Microsoft confirmed the disruption was caused by a recent change in Azure and completed rollback actions and recovery has progressed. Throughout the incident, our engineering team also took proactive steps to restore service and pursue additional mitigation options. That work included efforts to move service components to another region to bypass the Azure outage. We are continuing that work to strengthen regional redundancy in case of future incidents. Thank you for your patience throughout this incident.

According to our monitoring system this service has become unresponsive, we’re investigating.

Service is back up.

According to the system alerts the analytics data sync did not complete.  Our Engineering team is actively working to kick off the sync this morning. We will update this page as those efforts are completed.

Analytics syncs have been re-triggered this afternoon and should be up to date. Please reach out to support should further inconsistencies be noted. This incident will be moved to Resolved.