Clay had 56 outages in the last 2 years — averaging 2.3 incidents per month.
There were 56 Clay outages since July 14, 2025. Each is summarised below — incident details, duration, and resolution information.
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.
We’ve fully resolved the issue.
We are investigating an issue causing enrichment runs to hang or fail. Next update will be in 30 min or when we have more information.
We've identified the source of the issue and are implementing a backend workaround to restore normal processing while we continue investigating the root cause. During this time, webhooks may be delayed and some actions may be delayed or fail. Next update in 30 min or when we have more information.
We're rolling out a workaround and have seen partial recovery. Enrichment runs and table operations are back to normal, and we're now working to restore webhooks and async callbacks, which may still be delayed. We're continuing to investigate the underlying cause. Next update in 30 min or when we have more information.
We've implemented a backend workaround and functionality is restored. We still expect to see some delays in enrichment processing. Next update on resolution or when something changes.
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 fully resolved the issue.
We’re currently investigating this issue.
We’ve applied a fix for the issue and will continue to monitor the situation. We appreciate your patience.
We’ve fully resolved the issue and tables are loading as expected.
We've fully resolved this issue. During this period, some table views may have failed to load, existing rows may not have updated as expected, and Webhooks may have failed to deliver to their destination tables. If you believe any data was affected, please reach out to our support team and we'll be happy to help.
We’re investigating this.
We’ve identified the issue and implemented a mitigation. We’re continuing to monitor performance.
We’ve fully resolved the issue.
Clay’s AI enrichment actions are not completing tasks and remain stuck loading. We’re aware of the issue, and our engineers are currently investigating it. Sorry for the inconvenience, and we’ll share updates as soon as possible.
Clay’s AI enrichment actions are showing slow performance to complete tasks. We’re aware of the issue, and our engineers are currently investigating it. Sorry for the inconvenience, and we’ll share updates as soon as possible.
The latency issue has been mitigated. We will continue to monitor the situation. We appreciate your patience.
We’ve fully resolved the issue. If AI actions still appear stuck, please try force re-running the cells. You can also filter rows by “is queued” and bulk force re-run those rows.
We are currently investigating an issue where records are not added to tables following a successful import from external sources
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 fully resolved the issue.
We’re currently seeing Claygent enrichment actions stuck in the queue. This affects Clay’s enrichment actions and AI Claygent actions. We're currently investing the issue and working toward the fix.
We’ve fixed the issue and will continue to monitor the situation. We appreciate your patience.
We’ve fully resolved the issue.
We're currently investigating reports of web scraping failures when using AI actions in Clay. While cells completely successfully, they sometimes include error messages like "Error using the website scrape tool" in the response. We'll be sharing updates as soon as we have more information.
We've identified an issue leading to the scraping errors in AI columns, and are working on a fix. We'll share more updates as we progress to a resolution.
We’ve fixed the issue and will continue to monitor the situation. We appreciate your patience.
We've identified the issue and are currently working on a fix.
We’ve fixed the issue and will continue to monitor the situation. We appreciate your patience.
We’ve fully resolved the issue. Impacted rows will need to be re-run.
Some actions remain impacted as we continue working with our upstream provider. We’ll provide further updates as progress continues,
We’ve fully resolved the issue. To see results, please re-run any errored enrich person rows from this time. Job Change signals will catch up on their next scheduled run and do not require a re-run.
We’ve fully resolved the issue.
This has been resolved.
We’ve fully resolved the issue. Please re-run the impacted Find Employee Headcount by Criteria enrichment to return successful results.
Our monitoring indicates the issue has been resolved.
We’ve fully resolved the issue and the full workspace credit usage history should be visible. Thanks for your patience!
We’ve fully resolved the issue. Users can refresh their tables and re-run the HubSpot source.
The issue is resolved, we're monitoring that our systems are behaving properly and everything should now work at regular speed again.
We’ve fully resolved the issue.
The issue has been resolved.
We’ve fully resolved the issue.
The incident is resolved
We’ve fully resolved the issue.
Claygent columns configured to use private OpenAI keys from Zero Data Retention organizations are currently failing. Our engineering team has identified the cause and is working on a fix.
We’ve fully resolved the issue. You may need to refresh your browser page to ensure you see the dropdowns appearing in your enrichments!
The issue has been resolved. If you are still seeing the error with your Use AI column, re-save the column settings and try again.
Fix is verified and deployed