Clay app down
Timeline · 1 update
- resolved Oct 29, 2025, 09:39 PM UTC
This incident is resolved. app.clay.com is functioning normally and enrichments are running as expected since 4:05pm Eastern.
Clay had 66 outages in the last 2 years — averaging 2.7 incidents per month.
There were 66 Clay outages since May 19, 2025. Each is summarised below — incident details, duration, and resolution information.
This incident is resolved. app.clay.com is functioning normally and enrichments are running as expected since 4:05pm Eastern.
The issue affecting Claygent columns has been resolved. All Claygent column executions should now run successfully. We appreciate your patience.
Systems have fully recovered.
We’ve fully resolved the issue.
We’ve fully resolved the issue.
We’ve fully resolved the issue.
The issue has been fully resolved.
We’ve fully resolved the issue.
We’ve fully resolved the issue and have contacted affected customers. We were able to restore any lost data, as well as refund any credits that may have been lost.
We’ve fully resolved the issue.
We’ve fully resolved the issue.
We’ve fully resolved the issue.
We’ve fully resolved the issue.
We’ve fully resolved the issue.
We’ve fully resolved the issue. You can now re run the source and that should fix the issue!
We’ve fixed the issue and will continue to monitor the situation. We appreciate your patience. You should be able to re-run your search with the following steps: 1. In your table, locate the Find People column. 2. Click on the column header and select "Edit source." 3. Confirm your Limit is set properly, and edit the input if needed. This action will re-run the entire search. 4. Scroll down to the Run settings. 5. Click "Run now".
We’ve fully resolved the issue.
We’ve fully resolved the issue and ensured that credit balances have been restored to their correct amounts.
We’ve fully resolved the issue.
We’ve fully resolved the issue.
We’ve fully resolved the issue.
We’ve fully resolved the issue.
This issue has been resolved.
We’ve fully resolved the issue.
We’ve fully resolved the issue.