All Systems Operational
LeadConduit Operational
90 days ago
99.98 % uptime
Today
LeadConduit Classic Operational
90 days ago
99.99 % uptime
Today
TrustedForm Application ? Operational
90 days ago
99.97 % uptime
Today
TrustedForm Script ? Operational
90 days ago
99.99 % uptime
Today
SuppressionList Operational
90 days ago
99.99 % uptime
Today
ActiveProspect ID Operational
90 days ago
99.99 % uptime
Today
TrustedForm Facebook Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Past Incidents
Sep 27, 2020

No incidents reported today.

Sep 26, 2020

No incidents reported.

Sep 25, 2020

No incidents reported.

Sep 24, 2020

No incidents reported.

Sep 23, 2020
Resolved - We have added network configuration and servers to restore the legacy functionality that allowed lead submissions to LeadConduit Classic via the `app.leadconduit.com` domain name, and it should be working as previously.
Sep 23, 21:22 CDT
Identified - Leads being submitted to LeadConduit Classic using the app.leadconduit.com domain name are now receiving an HTTP 301 (Moved Permanently) redirect to classic.leadconduit.com. Systems which cannot follow this redirect are currently unable to submit leads to LeadConduit Classic.

The LeadConduit Classic posting instructions have used the classic.leadconduit.com domain for 4 years and luckily most of our customers have implemented that domain for their lead submissions during that time. For those who hadn't yet made the change, we attempted to proactively reach out via email. We also noted in our system maintenance published a week ago that "LeadConduit Classic will only be available from classic.leadconduit.com" after the move.

Unfortunately it has come to our attention that we still have some impacted customers. It is currently our highest priority to restore the legacy functionality that allowed lead submissions to LeadConduit Classic via the app.leadconduit.com domain name. That effort is underway.

For some, the most expedient solution might be for all lead submissions to change from https://app.leadconduit.com/v2/PostLeadAction URL to https://classic.leadconduit.com/v2/PostLeadAction.
Sep 23, 18:08 CDT
Resolved - This incident has been resolved.
Sep 23, 13:19 CDT
Monitoring - All LeadConduit components – lead-handling, UI, and API – are running normally again. Leads "spooled" to disk are being replayed as quickly as possible.
Sep 23, 10:26 CDT
Identified - We've believe we've identified the root cause, and are working to address it. The system is more stable. Leads spooled will be replayed ASAP.
Sep 23, 10:12 CDT
Investigating - LeadConduit Classic is experiencing elevated error rates across lead-handling, UI, and API.
Sep 23, 09:47 CDT
Postmortem - Read details
Sep 23, 02:25 CDT
Completed - The scheduled maintenance has been completed.
Sep 23, 01:00 CDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 22, 19:00 CDT
Update - We will be undergoing scheduled maintenance during this time.
Sep 19, 14:10 CDT
Scheduled - In an effort to improve our service availability, security, and resilience, we intend to change our LeadConduit hosting provider set to occur at the referenced time. We expect lead handling to continue uninterrupted, but there will be a period of time where processed leads will appear after a delay of up to a few hours. As part of this transition, next.leadconduit.com will complete the long planned transition to app.leadconduit.com and LeadConduit Classic will only be available from classic.leadconduit.com.
In the meantime this notification will serve as a final reminder to verify that any firewalls are updated to allow our advertised outbound IP addresses. Those IP addresses are as follows:
3.225.52.7
54.234.167.189
3.225.20.135
54.160.26.104
54.161.58.164
107.20.45.90

As always, please reach out to support@activeprospect.com if you have questions or concerns.
Sep 17, 16:54 CDT
Sep 22, 2020
Resolved - At this time, the Claim API has remained stable.

If you are calling the TrustedForm claim API directly from your system, you will need to retry all claim calls that did not result in an HTTP 201. If you are processing leads through LeadConduit, all your failed claim calls will be automatically retried for you. There is non further action necessary on your part.

We take the reliability of TrustedForm very seriously and apologize for the inconvenience this caused.
Sep 22, 17:01 CDT
Monitoring - As of 3:17 PM central time claiming errors rates started to return to normal. We will continue to monitor error rates.

We apologize for this inconvenience and are looking into how to protect against this condition moving forward.
Sep 22, 15:32 CDT
Investigating - Starting around 2:44 pm central time, TrustedForm's claim API began experiencing an elevated error rate. We are working to identify the cause of the errors and we appreciate your patience as we work to resolve them.
Sep 22, 15:02 CDT
Sep 21, 2020

No incidents reported.

Sep 20, 2020

No incidents reported.

Sep 19, 2020

No incidents reported.

Sep 18, 2020

No incidents reported.

Sep 17, 2020

No incidents reported.

Sep 16, 2020

No incidents reported.

Sep 15, 2020

No incidents reported.

Sep 14, 2020

No incidents reported.

Sep 13, 2020

No incidents reported.