Clay Status | Status

Updates

• Jun 12, 2026 7:29 PM EDT

  We’ve fully resolved the issue.

  Resolved
• Jun 9, 2026 5:30 PM EDT (3 days, 1 hour, and 58 minutes earlier)

  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.

  Monitoring
• Jun 9, 2026 2:17 PM EDT (3 hours and 12 minutes earlier)

  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.

  Identified
• Jun 9, 2026 1:37 PM EDT (39 minutes earlier)

  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.

  Identified
• Jun 9, 2026 12:52 PM EDT (44 minutes earlier)

  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.

  Identified
• Jun 9, 2026 12:09 PM EDT (42 minutes earlier)

  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.

  Investigating