pingoru pingoru Clay Labs had 119 outages in the last 2 years totaling 927h 22m of downtime, averaging 4.9 incidents per month.
There were 119 Clay Labs outages since October 23, 2024 totaling 927h 22m of downtime. Each is summarised below. Incident details, duration, and resolution information.
We’ve fully resolved the issue. Affected actions may need to be re-run.
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. 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.
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.
The issue has been fully resolved.
The issue has been fully resolved.
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.
We’ve fully resolved the issue.
We’ve fully resolved the issue.
We’ve fully resolved the issue and all Claygent workflow nodes should be running as expected.
We’ve fully resolved the issue and all Claygent workflow nodes should be running as expected.
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
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've resolved an issue that was affecting function table links.
We've resolved an issue that was affecting function table links.
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'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’ve fully resolved the issue. Thank you for your patience while we worked through it.
We’ve fully resolved the issue. Thank you for your patience while we worked through it.
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.
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'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 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 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.
We’ve fully resolved the issue.
We’ve fully resolved the issue.
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'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’ve fully resolved the issue.
We’ve fully resolved the issue.
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’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’ve fully resolved the issue.
We’ve fully resolved the issue.
We’ve fully resolved the issue. Impacted rows will need to be re-run.
We’ve fully resolved the issue. Impacted rows will need to be re-run.
We’ve fully resolved the issue.
We’ve fully resolved the issue.
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.
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.