Clay Outage History

Clay is up right now

Clay had 116 outages in the last 2 years — averaging 4.8 incidents per month.

There were 116 Clay outages since August 13, 2024. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.clay.com

Minor July 29, 2026

Legacy Audience Ads (beta) syncs are under-exporting audience members

Detected by Pingoru
Jul 29, 2026, 06:11 PM UTC
Resolved
Jul 29, 2026, 06:11 PM UTC
Duration
—
Affected: Clay service
Timeline · 3 updates
  1. identified Jul 28, 2026, 05:41 PM UTC

    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.

  2. identified Jul 28, 2026, 09:05 PM UTC

    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.

  3. resolved Jul 29, 2026, 06:11 PM UTC

    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.

Read the full incident report →

Minor July 26, 2026

AI Columns currently not running as expected

Detected by Pingoru
Jul 26, 2026, 01:19 AM UTC
Resolved
Jul 26, 2026, 01:19 AM UTC
Duration
—
Affected: Clay service
Timeline · 3 updates
  1. investigating Jul 25, 2026, 01:13 AM UTC

    We’re currently investigating this issue where AI columns become stuck after running.

  2. monitoring Jul 25, 2026, 01:55 AM UTC

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

  3. resolved Jul 26, 2026, 01:19 AM UTC

    We’ve fully resolved the issue. Thank you for your patience while we worked through it.

Read the full incident report →

Major July 16, 2026

app.clay.com is down

Detected by Pingoru
Jul 16, 2026, 01:44 PM UTC
Resolved
Jul 16, 2026, 01:44 PM UTC
Duration
—
Affected: Clay service
Timeline · 5 updates
  1. investigating Jul 16, 2026, 08:09 AM UTC

    We are investigating errors accessing app.clay.com

  2. monitoring Jul 16, 2026, 09:03 AM UTC

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

  3. monitoring Jul 16, 2026, 09:06 AM UTC

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

  4. monitoring Jul 16, 2026, 09:16 AM UTC

    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.

  5. resolved Jul 16, 2026, 01:44 PM UTC

    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.

Read the full incident report →

Minor July 15, 2026

Low Match Rates on Ads

Detected by Pingoru
Jul 15, 2026, 09:26 PM UTC
Resolved
Jul 15, 2026, 09:26 PM UTC
Duration
—
Affected: Clay service
Timeline · 2 updates
  1. investigating Jul 15, 2026, 03:53 PM UTC

    We're investigating reports of low match rates on Meta for the Ads product.

  2. resolved Jul 15, 2026, 09:26 PM UTC

    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.

Read the full incident report →

Minor July 8, 2026

Enrichment delays identified

Detected by Pingoru
Jul 08, 2026, 05:22 PM UTC
Resolved
Jul 08, 2026, 05:22 PM UTC
Duration
—
Affected: Clay service
Timeline · 2 updates
  1. identified Jul 08, 2026, 04:05 PM UTC

    We’ve identified an issue causing some enrichment to take longer than usual to complete. A fix is in progress.

  2. resolved Jul 08, 2026, 05:22 PM UTC

    We’ve fully resolved the issue.

Read the full incident report →

Minor July 8, 2026

Investigating: Slower AI enrichment runs

Detected by Pingoru
Jul 08, 2026, 09:15 AM UTC
Resolved
Jul 08, 2026, 09:15 AM UTC
Duration
—
Affected: Clay service
Timeline · 3 updates
  1. investigating Jul 06, 2026, 12:27 PM UTC

    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.

  2. monitoring Jul 06, 2026, 01:18 PM UTC

    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.

  3. resolved Jul 08, 2026, 09:15 AM UTC

    We’ve fully resolved the issue.

Read the full incident report →

Minor July 1, 2026

Incoming webhooks not properly processed

Detected by Pingoru
Jul 01, 2026, 12:01 AM UTC
Resolved
Jul 01, 2026, 12:01 AM UTC
Duration
—
Affected: Clay service
Timeline · 2 updates
  1. monitoring Jun 30, 2026, 10:18 PM UTC

    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.

  2. resolved Jul 01, 2026, 12:01 AM UTC

    We’ve fully resolved the issue.

Read the full incident report →

Minor June 12, 2026

Enrichment Run Failures

Detected by Pingoru
Jun 12, 2026, 11:29 PM UTC
Resolved
Jun 12, 2026, 11:29 PM UTC
Duration
—
Affected: Clay service
Timeline · 6 updates
  1. investigating Jun 09, 2026, 04:09 PM UTC

    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.

  2. identified Jun 09, 2026, 04:52 PM UTC

    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.

  3. identified Jun 09, 2026, 05:37 PM UTC

    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.

  4. identified Jun 09, 2026, 06:17 PM UTC

    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.

  5. monitoring Jun 09, 2026, 09:30 PM UTC

    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.

  6. resolved Jun 12, 2026, 11:29 PM UTC

    We’ve fully resolved the issue.

Read the full incident report →

Minor June 9, 2026

We are currently experiencing an issue where rows in a table aren't correctly loading

Detected by Pingoru
Jun 09, 2026, 04:21 PM UTC
Resolved
Jun 09, 2026, 04:21 PM UTC
Duration
—
Affected: Clay service
Timeline · 4 updates
  1. investigating Jun 09, 2026, 09:16 AM UTC

    We’re currently investigating this issue.

  2. monitoring Jun 09, 2026, 09:44 AM UTC

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

  3. resolved Jun 09, 2026, 03:14 PM UTC

    We’ve fully resolved the issue and tables are loading as expected.

  4. resolved Jun 09, 2026, 04:21 PM UTC

    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.

Read the full incident report →

Minor May 26, 2026

Clay is currently experiencing issues

Detected by Pingoru
May 26, 2026, 08:03 PM UTC
Resolved
May 26, 2026, 08:03 PM UTC
Duration
—
Affected: Clay service
Timeline · 3 updates
  1. investigating May 26, 2026, 07:00 PM UTC

    We’re investigating this.

  2. monitoring May 26, 2026, 07:10 PM UTC

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

  3. resolved May 26, 2026, 08:03 PM UTC

    We’ve fully resolved the issue.

Read the full incident report →

Minor May 25, 2026

AI actions complete time are showing slower than usual.

Detected by Pingoru
May 25, 2026, 11:58 AM UTC
Resolved
May 25, 2026, 11:58 AM UTC
Duration
—
Affected: Clay service
Timeline · 4 updates
  1. investigating May 25, 2026, 10:00 AM UTC

    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.

  2. investigating May 25, 2026, 10:12 AM UTC

    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.

  3. monitoring May 25, 2026, 10:53 AM UTC

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

  4. resolved May 25, 2026, 11:58 AM UTC

    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.

Read the full incident report →

Minor May 25, 2026

Records not populating from External Source imports

Detected by Pingoru
May 25, 2026, 08:53 AM UTC
Resolved
May 25, 2026, 08:53 AM UTC
Duration
—
Affected: Clay service
Timeline · 3 updates
  1. investigating May 22, 2026, 11:11 AM UTC

    We are currently investigating an issue where records are not added to tables following a successful import from external sources

  2. monitoring May 22, 2026, 01:47 PM UTC

    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.

  3. resolved May 25, 2026, 08:53 AM UTC

    We’ve fully resolved the issue.

Read the full incident report →

Minor May 25, 2026

Clay's enrichment actions shows stuck in the queue

Detected by Pingoru
May 25, 2026, 08:20 AM UTC
Resolved
May 25, 2026, 08:20 AM UTC
Duration
—
Affected: Clay service
Timeline · 3 updates
  1. investigating May 25, 2026, 06:58 AM UTC

    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.

  2. monitoring May 25, 2026, 08:07 AM UTC

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

  3. resolved May 25, 2026, 08:20 AM UTC

    We’ve fully resolved the issue.

Read the full incident report →

Minor May 23, 2026

Web scraping errors in AI columns

Detected by Pingoru
May 23, 2026, 12:04 AM UTC
Resolved
May 23, 2026, 12:04 AM UTC
Duration
—
Affected: Clay service
Timeline · 6 updates
  1. investigating May 22, 2026, 07:50 PM UTC

    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.

  2. identified May 22, 2026, 08:23 PM UTC

    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.

  3. monitoring May 22, 2026, 09:14 PM UTC

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

  4. identified May 22, 2026, 11:10 PM UTC

    We've identified the issue and are currently working on a fix.

  5. monitoring May 22, 2026, 11:32 PM UTC

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

  6. resolved May 23, 2026, 12:04 AM UTC

    We’ve fully resolved the issue. Impacted rows will need to be re-run.

Read the full incident report →

Minor April 27, 2026

Some Enrich Person and Professional Posts Actions are Experiencing Errors

Detected by Pingoru
Apr 27, 2026, 08:42 PM UTC
Resolved
Apr 27, 2026, 08:42 PM UTC
Duration
—
Affected: Clay service
Timeline · 2 updates
  1. identified Apr 23, 2026, 11:49 PM UTC

    Some actions remain impacted as we continue working with our upstream provider. We’ll provide further updates as progress continues,

  2. resolved Apr 27, 2026, 08:42 PM UTC

    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.

Read the full incident report →

Minor April 6, 2026

Find Employee Headcount by Criteria

Detected by Pingoru
Apr 06, 2026, 11:31 PM UTC
Resolved
Apr 06, 2026, 11:31 PM UTC
Duration
—
Affected: Clay service
Timeline · 1 update
  1. resolved Apr 06, 2026, 11:31 PM UTC

    We’ve fully resolved the issue. Please re-run the impacted Find Employee Headcount by Criteria enrichment to return successful results.

Read the full incident report →

Minor March 18, 2026

Workspace Level Credit Reporting Issues

Detected by Pingoru
Mar 18, 2026, 05:49 PM UTC
Resolved
Mar 18, 2026, 05:49 PM UTC
Duration
—
Affected: Clay service
Timeline · 1 update
  1. resolved Mar 18, 2026, 05:49 PM UTC

    We’ve fully resolved the issue and the full workspace credit usage history should be visible. Thanks for your patience!

Read the full incident report →