Clay Outage History
12 incidents recorded over the last 365 days, 12 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Clay Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 4, 2026 | Clay Login Issue: app.clay.com is downWe’ve fixed the issue and will continue to monitor the situation. Please refresh your browser window to access Clay. | 42 min | Resolved |
| Oct 27, 2026 | Some enrichments, AI columns slow to processSome enrichments including AI columns are slow to process starting at at 12:47pm EDT. We've identified the issue and working to resolve it. | 1h 13m | Resolved |
| Oct 20, 2026 | Webhook, Audiences, enrichment delaysWe've resolved the issue causing processing delays across Audiences, some enrichments, and webhooks. For enrichments with cells stuck in Queued or Awaiting Callback, retrying that cell should run the enrichment… | 30h 46m | Resolved |
| Oct 14, 2026 | HTTP API actions returning errorsFrom 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. | 36 min | Resolved |
| Sep 30, 2026 | Account Agent Runs in Audiences FailedUsers 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). | 23h 8m | Resolved |
| Sep 23, 2026 | Ad syncs and API/CLI batch runs failingEarlier 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… | 12h 6m | Resolved |
| Sep 15, 2026 | Enrich Person and Signal Run degradationWe'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. | 384h 14m | Resolved |
| Sep 15, 2026 | Enrichment Action ErrorsWe 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… | 7h 58m | Resolved |
| Sep 9, 2026 | Enrich Person is not returning correct data in some casesEnrich 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… | 45h 28m | Resolved |
| Aug 13, 2026 | Issues with Audiences and Table LookupsWe’ve mitigated the issue and will continue to monitor the situation. We appreciate your patience. | 3h 38m | Resolved |
| Aug 12, 2026 | Unexpected Behavior in Claygent Workflows NodeWe’re continuing to monitor the situation and appreciate your patience. | 43h 50m | Resolved |
| Aug 10, 2026 | High errors and latency issueWe 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… | 6h 20m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Clay incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Clay Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Clay acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Clay outage in this window ran 16d, against a mean recovery of 1d 22h. If you depend on Clay in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.