Is Clay down?

Last checked 1m ago
Current status
Clay is up

No incidents right now.

Official status page: https://status.clay.com · Polled every 5 minutes · 1 component tracked

Clay is operational right now. Last checked 1m ago; the most recent incident resolved 1d ago.

Real-time Clay status, recent outages, and incident history — pulled directly from Clay's official status page at https://status.clay.com every 5 minutes. Pingoru tracks 1 Clay service and has captured 13 incidents in the last 90 days (85.56% uptime). Get email, Slack, Discord, or webhook alerts the moment Clay reports a new incident — free for 5 monitors, no credit card.

Users who monitor Clay also follow these CRM services: HubSpot Intercom Jira Service Desk ActiveCampaign Teamwork Alchemer Formstack Help Scout Intapp Bullhorn View all 6,000+ providers
Clay uptime 85.56% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Jun 12, 2026, 11:29 PM UTC · Resolved Jun 12, 2026, 11:29 PM UTC
    Clay service
    Timeline · 6 updates
    • 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.

    • 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.

    • 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.

    • 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.

    • 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.

    • resolved · Jun 12, 2026, 11:29 PM UTC

      We’ve fully resolved the issue.

    Latest: We’ve fully resolved the issue.

  2. Resolved
    Started Jun 09, 2026, 04:21 PM UTC · Resolved Jun 09, 2026, 04:21 PM UTC
    Clay service
    Timeline · 4 updates
    • investigating · Jun 09, 2026, 09:16 AM UTC

      We’re currently investigating this issue.

    • 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.

    • resolved · Jun 09, 2026, 03:14 PM UTC

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

    • 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.

    Latest: 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 deliv…

  3. Resolved
    Started May 26, 2026, 08:03 PM UTC · Resolved May 26, 2026, 08:03 PM UTC
    Clay service
    Timeline · 3 updates
    • investigating · May 26, 2026, 07:00 PM UTC

      We’re investigating this.

    • monitoring · May 26, 2026, 07:10 PM UTC

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

    • resolved · May 26, 2026, 08:03 PM UTC

      We’ve fully resolved the issue.

    Latest: We’ve fully resolved the issue.

  4. Resolved
    Started May 25, 2026, 11:58 AM UTC · Resolved May 25, 2026, 11:58 AM UTC
    Clay service
    Timeline · 4 updates
    • 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.

    • 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.

    • 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.

    • 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.

    Latest: 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.

  5. Resolved
    Started May 25, 2026, 08:53 AM UTC · Resolved May 25, 2026, 08:53 AM UTC
    Clay service
    Timeline · 3 updates
    • 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

    • 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.

    • resolved · May 25, 2026, 08:53 AM UTC

      We’ve fully resolved the issue.

    Latest: We’ve fully resolved the issue.

See the full Clay outage history

8 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Clay outage history →

Or sign up free to get alerts when Clay breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 13 incidents View full outage history →