Clay had 119 outages in the last 2 years totaling 336h 36m of downtime — averaging 4.9 incidents per month.
There were 119 Clay outages since October 23, 2024 totaling 336h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.
From 2:06pm to 3:03pm Eastern, HTTP API and some other built-in enrichments were returning errors. We’ve fixed the issue and will continue to monitor the situation. We appreciate your patience.
We’ve fully resolved the issue. Affected actions may need to be re-run.
Users might see an error for some Account Agent in Audiences runs. The team has resolved this issue. Please rerun the Account Agent to get results (scheduled Account Agents will have results on the next scheduled run).
Users might see an error for some Account Agent in Audiences runs. We’ve fully resolved the issue and you were not charged credits for errored runs. Please rerun the Account Agent to get results (scheduled Account Agents will have results on the next scheduled run). You can see all your Account Agents and last run status is Audiences > Companies > Data Hub.
Our team has identified an issue causing the following behaviours. Ad syncs not completing Batch and workflow runs started through the Clay API or CLI failing Some batches started through the CLI can't be cancelled. At this time our team is investigating a resolution and advises not to reattempt any failed/stuck processes.
Earlier today our team identified an issue causing failures and errors to the following Clay functionality: Account Agents New Account Onboarding Campaigns Ad Syncs Batch and workflow runs started through the Clay API or CLI At this time we’ve fixed the issue and will continue to monitor the situation. We continue to advise not to reattempt any failed/stuck processes. We appreciate your patience
The issue has been fully resolved.
We're currently experiencing delays and increased error rates on Enrich Person due to an upstream data provider reducing their rate limits. Our team has applied mitigations to reduce impact and is actively monitoring the situation. We'll share updates as they become available.
Our team has applied mitigations to decrease delays on Enrich Persons. Please re-run errored cells if you are still experiencing rate limit issues and reach out to Support with any outstanding questions. We are continuing to improve the speed of this enrichment.
We've identified an issue causing Enrich Person and Signal runs to slow down, and in some cases timeout, due to increased rate limiting from one of our data providers. As a workaround, we recommend running Enrich Person through another provider in the meantime. We're actively working on a fix and will continue to post updates here.
A third-party data provider we rely on is experiencing a major disruption, affecting some actions in Clay. We're working on a number of updates to remedy this issue and will post updates as we have them. Enrich Person — degraded. Runs may be stale, or in some cases, fail. We recommend utilizing a different Enrich Person provider in the meantime. Job Changers Signal, Promotion Signal — failing. These will return an error and won't run. Monitor Professional Posts, Monitor Interactions — failing. All runs will return an error. We're working on an alternative action backed by a different provider. You are not charged for failed or errored runs.
We've fixed the issue impacting Enrich Person and Job Change/Promotion signals. We're actively working on a fix for Monitor Public Posts/Interactions sources.
We’ve fully resolved the issue.
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.
We’ve fully resolved the issue.
We’ve identified an issue with Enrich Person returning incorrect data in some cases and are currently working on a fix.
Enrich Person is now returning correct results on new enrichments. If you are still seeing incorrect data, please re-run the cells. The team is continuing to investigate some incorrect People data in Audience records and work towards a fix.
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’ve fully resolved the issue.
Claygent workflows are experiencing unexpected behavior. Edit the API key configuration on the workflow node, then re-save the setup to refresh the connection.
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 fully resolved the issue and all Claygent workflow nodes should be running as expected.
Users may experience issues with Audiences pages and table lookups.
We’ve identified the issue and are currently working on a fix.
We’ve mitigated the issue and will continue to monitor the situation. We appreciate your patience.
We’ve fully resolved the issue.
We are currently experiencing elevated error rates and increased latency across the Clay application. Our engineering team is actively investigating the issue and working to restore normal service as quickly as possible. We apologize for the inconvenience and appreciate your patience while we work to resolve this incident.
We are currently experiencing elevated error rates and increased latency across a small number of workspaces on the Clay application. We’re still investigating the issue and updates will be posted here as soon as we know more. We apologize for the inconvenience and appreciate your ongoing patience while we work to resolve this incident.
We are currently experiencing elevated error rates and increased latency across a small number of workspaces on the Clay application. As a result of this, webhook processing is currently paused for all workspaces. We’re still investigating the issue and updates will be posted here as soon as we know more. We apologize for the inconvenience and appreciate your ongoing patience while we work to resolve this incident.
Earlier today we experienced elevated error rates and increased latency across a small number of workspaces on the Clay application due to a partial outage with our cloud services provider. During this degradation webhook processing was temporarily disabled for all workspaces. This has now been resolved. Access to affected workspaces and tables has been restored and queued webhooks have processed. We apologize for any inconvenience caused
We’re currently investigating an issue that arises when you attempt to access a function
We're investigating an issue where Legacy Audience Ad syncs (beta) since Friday 7/24 with a NOT filter on the segment are under-exporting rows. We've identified the root cause and are working on deploying a fix.
We're investigating an issue where Legacy Audience Ad syncs (beta) since Friday 7/24 with a NOT filter on the segment are under-exporting rows. We've identified the root cause and are working on deploying a fix.
We've pushed a fix. We've re-synced all recurring v2 Ad Syncs to re-trigger ad platform syncs with the fixed data. Legacy ad syncs will repair themselves on their next scheduled sync.
We’re currently investigating this issue where AI columns become stuck after running.
We’ve fixed the issue and will continue to monitor the situation. We appreciate your patience.
We’ve fully resolved the issue. Thank you for your patience while we worked through it.
We are investigating errors accessing app.clay.com
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.
Clay was unavailable due to an upstream infrastructure provider outage that also affected several downstream providers, including intermittent SSO login issues. This has been resolved and the app is fully operational. Please re-send webhooks and re-run impacted cells.
We're investigating reports of low match rates on Meta for the Ads product.
We've solved this temporary issue contained to the Meta integration that should resolve for new syncs. We will continue monitoring match rates to ensure they continue recovering over time.
We’ve identified an issue causing some enrichment to take longer than usual to complete. A fix is in progress.
We’ve fully resolved the issue.
We're currently seeing slower-than-normal processing and some delays on AI enrichment runs. Our team is actively investigating. We'll post updates here as we learn more. Thanks for your patience.
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.
We’ve fully resolved the issue.
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.