Activeprospect Status

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. 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.

We identified an issue in TrustedForm related to recent changes that were not compatible with certain Content Security Policies (CSPs). As a result, session replays generated during the impact window may not contain snapshots and may display the message: “This replay could not be loaded” The affected changes were deployed at approximately 8:20 AM CT and rolled back at 1:49 PM CT. The issue has been resolved, and new session replays are functioning normally. However, session replays and snapshots impacted during the incident window could not be recovered. We apologize for the disruption and appreciate your patience while we worked to resolve the issue.

Today between 12:26 PM and 12:45 PM CT, TrustedForm experienced elevated latency on its API. During this time, some customers may have encountered 500 errors or longer-than-normal response times. The issue has been resolved and performance has returned to normal. We will continue to monitor the system.

Today between 9:04 AM and 11:00 AM CT, TrustedForm experienced elevated latency on its API. During this time, some customers may have encountered 500 errors or longer-than-normal response times. The issue has been resolved and performance has returned to normal. We will continue to monitor the system.

This incident has been resolved.

This incident has been resolved.

It's confirmed that the TikTok API error is no longer occurring. The incident is resolved

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

We have completed the necessary steps for today's database migration. We will be finishing in a follow-up maintenance tomorrow during the same time period.

The scheduled maintenance has been completed.