All Systems Operational
LeadConduit Operational
90 days ago
100.0 % uptime
Today
LeadConduit Classic Operational
90 days ago
100.0 % uptime
Today
TrustedForm Application ? Operational
90 days ago
99.97 % uptime
Today
TrustedForm Script ? Operational
90 days ago
99.98 % uptime
Today
SuppressionList Operational
90 days ago
100.0 % uptime
Today
ActiveProspect ID Operational
90 days ago
100.0 % 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.
had a major outage
had a partial outage
Past Incidents
Jan 18, 2020

No incidents reported today.

Jan 17, 2020

No incidents reported.

Jan 16, 2020

No incidents reported.

Jan 15, 2020

No incidents reported.

Jan 14, 2020

No incidents reported.

Jan 13, 2020

No incidents reported.

Jan 12, 2020

No incidents reported.

Jan 11, 2020

No incidents reported.

Jan 10, 2020

No incidents reported.

Jan 9, 2020

No incidents reported.

Jan 8, 2020
Resolved - TrustedForm is operating at 100%. The claim API was down from approximately 12:50pm central to 1:30pm. There are no other impacts from this outage. If you see something strange or have further questions, please reach out to support@activeprospect.com.

We're still working through what happened with the cluster and we will take whatever action is necessary to prevent this from occurring again. Again, we really appreciate your patience during this outage. Thank you.
Jan 8, 14:05 CST
Monitoring - The database cluster repair has completed. Certificates generated during this outage appear to be properly formed. We are not seeing any evidence of data loss. 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. This is always the case, even when we aren't having a major service interruption such as this. 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 are continuing to monitor the health of the system. Once we are confident that it is fully recovered, we will mark this issue resolved.
Jan 8, 13:37 CST
Update - The cluster is currently repairing itself. At the current rate, we hope to see the repair complete within 15 minutes. The service may be operable before then. We will share additional updates as soon as we have them. Thank you for your patience while the team works through this issue.
Jan 8, 13:31 CST
Investigating - We are currently investigating a service outage caused by a failed database cluster. We're working on restoring that cluster to full operation currently, but don't yet know a timeline. Once we have done so, we expect the service to be back up and running at full capacity.
Jan 8, 13:15 CST
Jan 7, 2020

No incidents reported.

Jan 6, 2020

No incidents reported.

Jan 5, 2020

No incidents reported.

Jan 4, 2020

No incidents reported.