Activeprospect outage history

We have investigated reports of delayed facebook leads affecting LeadsBridge. We identified and solved the issue. Customers may have experienced delayed leads. Our team is actively monitoring and will provide an update as more information becomes available.

This incident has been resolved. Between approximately 14:40 and 17:40 UTC, customers may have experienced delayed leads for Facebook Lead Ads. LeadsBridge is operating normally. No leads were lost. We apologize for the disruption.

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

We are currently investigating an issue affecting LeadConduit customers using the Experian add-on. At this time, all leads processed through the Experian integration are returning an “Invalid or Expired Credentials” error. This behavior is occurring across all requests and is not isolated to individual customer configurations. Our team is actively working with Experian to determine the root cause of the issue and identify a resolution. We will provide updates as soon as more information becomes available. Thank you for your patience while we work to resolve this issue. — ActiveProspect Engineering Team

The issue affecting LeadConduit customers using the Experian add-on has been resolved, and the add-on is now processing leads successfully. We’ll continue to monitor the integration closely to ensure continued stability and will provide another update if anything changes. Thank you for your patience. — ActiveProspect Engineering Team

This incident has been resolved.

We are currently investigating an issue affecting LeadConduit customers using the Experian add-on. At this time, all leads processed through the Experian integration are returning an “Invalid or Expired Credentials” error. This behavior is occurring across all requests and is not isolated to individual customer configurations. Our team is actively working with Experian to determine the root cause of the issue and identify a resolution. We will provide updates as soon as more information becomes available. Thank you for your patience while we work to resolve this issue. — ActiveProspect Engineering Team

The issue affecting LeadConduit customers using the Experian add-on has been resolved, and the add-on is now processing leads successfully. We’ll continue to monitor the integration closely to ensure continued stability and will provide another update if anything changes. Thank you for your patience. — ActiveProspect Engineering Team

This incident has been resolved.

We are investigating an issue affecting the TikTok Lead Generation integration. Our initial findings indicate a potential TikTok API outage. This issue is impacting the bridge editor and may also be impacting lead synchronization. We are actively monitoring the situation and will provide updates as more information becomes available.

We have identified the TikTok API responsible for the issue. This API is currently returning errors, which is impacting lead synchronization. We continue to monitor the situation and will share further updates as they become available.

The outage affecting the TikTok Lead Generation API has been resolved. The API is no longer returning errors, and lead synchronization has resumed successfully. We will continue to monitor the situation to ensure ongoing stability.

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

On December 18, 2025, between 10:10 a.m. and 1:41 p.m. CST, TrustedForm experienced an issue that prevented snapshot creation for certificates on pages where a third-party script was running alongside the TrustedForm script. Certificates generated during this window will display an error message for the session replay and event log. At 1:41 p.m. CST, an update was deployed to the TrustedForm script that resolved the issue. However, snapshots cannot be retroactively generated for certificates created during this affected period. Next Steps Users are advised to review certificates generated during this timeframe. Affected customers will be contacted by their Customer Success Manager (if applicable) with additional guidance and next steps.

On December 15, 2025 between 11:53 AM and 12:22 PM CST, LeadConduit and SuppressionList user interfaces were unavailable within the ActiveProspect platform. The issue was fully resolved at 12:22 PM CST, and services have returned to normal operation. Lead processing was not affected.

On December 11, 2025 between 12:16 PM and 12:25 PM CST, customers making requests to cert.trustedform.com may have experienced increased latency, timeouts, and 5xx errors. Some users of TrustedForm may also have noticed slow page load times or intermittent errors during this period. The issue was fully resolved at 12:25 PM CST, and services have returned to normal operation. TrustedForm certificate creation was not impacted. Customers who received an error and have not yet retried their request should now be able to do so successfully.

On December 3, 2025 between 3:41 PM and 5:15 PM CST, customers making requests to cert.trustedform.com may have experienced increased latency, timeouts, and 5xx errors. Some users of TrustedForm may also have noticed slow page load times or intermittent errors during this period. The issue was fully resolved at 5:15 PM CST, and services have returned to normal operation. TrustedForm certificate creation was not impacted. Customers who received an error and have not yet retried their request should now be able to do so successfully.

We are currently experiencing a service disruption in LeadsBridge due to an ongoing outage in CloudFlare This is affecting the app and the webhook sync. Our engineering team is monitoring the external outage and working to mitigate the impact.

The external system (Cloudflare) identified the issue and is working on restoring service. Some services are recovering while others are still experiencing an issue. Webhooks service (lead sync) is now operational LeadsBridge App is still down

The engineering team has taken actions to mitigate the issue. All LeadsBridge services are currently operational. We will continue to monitor the situation closely to ensure stability.

The external system declared the outage solved. We've completed our monitoring activities: all the services are confirmed as operational. The incident has been fully resolved.

Batch File Configuration is currently unavailable in LeadConduit. Our cloud platform, AWS (https://health.aws.amazon.com/health/status) is actively working to resolve this issue with urgency. At this time, we do not have a definitive ETA to share. We will be providing hourly updates until this issue is resolved.

Batch File Configuration is still unavailable in LeadConduit. We appreciate your continued patience. Our cloud platform, AWS (https://health.aws.amazon.com/health/status) is actively working to resolve this issue with urgency. At this time, we do not have a definitive ETA to share. We will be providing hourly updates until this issue is resolved.

Earlier today, Batch File Configuration experienced issues due to the AWS outage. Those issues have been resolved. We appreciate your patience.

We are currently experiencing a service disruption in TrustedForm due to an ongoing outage in AWS us-east-1. This is affecting form certificate generation and verification operations in that region. Our engineering team is monitoring AWS recovery efforts and our teams are working to mitigate impact. We will provide updates as soon as service stability returns.

We are observing recovery across key TrustedForm components. AWS us-east-1 remains partially degraded, but service performance is improving as upstream AWS systems stabilize. Our team continues to monitor system health and validate full functionality. We will post another update once all services are fully restored and verified.

Some WebSDK events are experiencing delays, which may cause temporary inconsistencies in Insights data and Verify API responses. Our team is actively working on recovery and stabilization.

The WebSDK event delays have been resolved, and all systems are now operating normally. Customers should no longer experience inconsistencies in Insights or Verify responses. Our team will continue monitoring to ensure full stability.

We are seeing an increase in errors affecting TrustedForm services. Our engineering team is actively investigating the issue, related to the ongoing AWS us-east-1 incident. We will provide updates as we identify the root cause and implement mitigations.

We appreciate your continued patience. Our cloud platform, AWS (https://health.aws.amazon.com/health/status) is actively working to resolve this issue with urgency. At this time, we do not have a definitive ETA to share. We will be providing hourly updates until this issue is resolved.

Our cloud provider, AWS (https://health.aws.amazon.com/health/status), has implemented a fix for their systems. All TrustedForm services are now processing traffic as expected, and background systems are fully operational. While our automatic scaling tools are still being restored, we’ve increased system capacity to handle higher volumes. We’ll continue to monitor closely to ensure stability and will provide another update once all automated scaling systems are fully restored.

Resolved - As of 4:26 PM CDT on October 20, the issue related to the AWS outage has been fully resolved. All ActiveProspect services are now operating as expected. Thank you for your patience.

High latency observed from 6:40 AM–8:20 AM CDT. Issue has been resolved and systems are operating normally.