Is ActiveProspect down?

We are aware of an issue affecting some Seller Directory applications submitted for recently verified domains. Applicants whose domains were verified recently may experience errors or delays when submitting or progressing through the application process. Applications for domains verified prior to Wed, July 15, are not affected, and no submitted data has been lost. We have identified the cause and are working on a fix.

Resolved — Joining the Seller Directory is now working normally for recently verified domains. During the incident, customers whose domains were verified on or after Wed, July 15 may have been temporarily unable to join. If you were affected, you can now join as expected. We apologize for the inconvenience.

We identified an issue affecting consent language collection for a customer using the TrustedForm Certify SDK. Changes deployed on June 9 were found to be incompatible with that customer's website configuration, causing consent language to not be collected properly in certain browsers. The issue was reported on June 10 and was investigated immediately. The affected changes were rolled back shortly thereafter, and the rollback resolved the issue. We continue to monitor the service and have confirmed that consent language collection is functioning normally following the rollback. We apologize for the inconvenience and appreciate the customer's assistance in identifying the issue.

At 8:15am today, users experienced issues accessing the ActiveProspect application due to an application configuration error. An update caused an unintended redirect loop on the ActiveProspect application, preventing users from successfully accessing the platform. The issue was identified and corrected, and service has been fully restored. Throughout the incident, core ActiveProspect services continued to operate normally. No data was lost, and lead processing, certificate issuing, and other backend services remained unaffected. We apologize for the disruption and appreciate your patience while we worked to resolve the issue.

We identified an issue related to an update deployed to TrustedForm Certify on June 3 at approximately 8:30 AM CT. The update introduced behavior that caused TrustedForm assets to be blocked on some websites with restrictive Content Security Policies (CSPs). As a result, certificates created on those websites during the affected period may not have captured consent language correctly, which could have caused downstream verification requests to fail. The update was rolled back on June 4 at approximately 1:00 PM CT, and newly created certificates are no longer affected by this issue. It is important to note that TrustedForm certification has always required all necessary web assets to be accessible to TrustedForm resources. Implementations that restrict TrustedForm through CSP or other security controls may result in certificates with incomplete data and unexpected verification outcomes. To ensure proper operation, publishers using a CSP should review their configuration and verify that it complies with our implementation guidance: https://support.activeprospect.com/hc/en-us/articles/45013581545364-Getting-Started-with-Certifying-Leads-on-Sites-Using-a-Content-Security-Policy-CSP

During the deployment of a new application version at 1:40 PM CT, we observed a significant increase in connection errors and latency across the application. TrustedForm Certify experienced a partial outage from 1:42 PM CT until 1:48 PM CT. At this time our findings did not uncover impact to certifications submitted during this time. TrustedForm API was down from 2:06 to 2:25 PM CST The team is continuing to investigate the root cause. Additional updates will be shared as more information becomes available.