At approximately 9:28am central time, our database cluster suffered the loss of its primary member. Normally during this condition, the cluster automatically fails over to one of the several surviving members. However, due to a recent infrastructure change the failover process failed unexpectedly.
After diagnosing the problem, our team set out to fix the infrastructure change that was preventing failover from working properly. At approximately 10:25am central time, the database cluster properly failed over to one of the surviving nodes.
During this outage SuppressionList API calls and TrustedForm claim API calls were failing. If you are directly calling the TrustedForm Claim API (rather than using LeadConduit to do so), you should retry your claim calls that resulted in error.
LeadConduit was still handling leads correctly but lead events were a few minutes delayed making it into the database. LeadConduit Classic was receiving leads correctly, but some were processed in a delayed fashion.
There should be no data loss from this outage. If you have any questions or concerns, please reach out to us at support@activeprospect.com