Clay Outage History

We identified an issue causing errors on Company enrichment actions in workflows (including Enrich Company and related lookups), along with intermittent errors on Company search via our public API. A fix was deployed and error rates returned to normal and we are continuing to monitor closely to confirm full stability.

Enrich Person is now returning correct results on new enrichments in tables and Audience records. If you are still seeing incorrect data, please re-run the cells. Additionally, you may have experienced degradation in Job Changer Signals data. This has now been resolved and will continue to improve over the course of today.

We're deployed a fix for new Claygent nodes. For existing Claygent workflows, continue to edit the API key configuration on the workflow node then re-save the setup to refresh the connection.

We’re continuing to monitor the situation and appreciate your patience.

We’ve mitigated the issue and will continue to monitor the situation. We appreciate your patience.

We’ve fixed the issue and will continue to monitor the situation. We appreciate your patience.

We’ve fixed the issue and will continue to monitor the situation. We appreciate your patience.

The errors stem from an outage with an upstream provider. We implemented a temporary workaround and are seeing recovery.

The upstream infrastructure provider outage is affecting other services and some Clay features. SSO to app.clay.com remains unstable, and some enrichment providers may experience errors.

We've fixed the issue that was causing slower-than-normal AI enrichment runs and delays, and we'll continue to monitor to make sure things are fully back to normal. Runs should now be processing at their usual speed. We appreciate your patience.

From 21:59 to 22:09 UTC, incoming webhooks received a 503 error code. We’ve fixed the issue and will continue to monitor the situation. We appreciate your patience.

While restoring normal processing, we identified that some data generated during the incident window may not have been saved correctly. As a result, a subset of enrichment results may be incomplete or missing. We’re currently assessing the full scope of the impact. Once we’ve confirmed which customers were affected, we’ll reach out directly with more information and next steps.

We’ve applied a fix for the issue and will continue to monitor the situation. We appreciate your patience.

We’ve identified the issue and implemented a mitigation. We’re continuing to monitor performance.

The latency issue has been mitigated. We will continue to monitor the situation. We appreciate your patience.

We have released a potential fix and are continuing to monitor the situation. New source imports should now run and populate rows as expected. Any imports that failed during the incident will need to be re-run manually.

We’ve fixed the issue and will continue to monitor the situation. We appreciate your patience.

We’ve fixed the issue and will continue to monitor the situation. We appreciate your patience.

We’ve fixed the issue and will continue to monitor the situation. We appreciate your patience.