Hey everyone! AWS has seen significant signs of recovery. Most requests should now be succeeding. We will continue to monitor the situation to ensure there's no degradation of services, but most features should be working as expected now. As the AWS incident has yet to be fully resolved you may encounter some issues regarding latency and performance. Thank you for your understanding. See below for the AWS update: https://health.aws.amazon.com/health/status And the Clay status page: https://status.clay.com/
During AWS recovery, you might see failed enrichments and processing delays. Performance issues can show up as latency where cell data takes longer to load, especially with larger tables or complex workflows.
Try a hard refresh if you're experiencing slowdowns - Command+Shift+R on Mac or Ctrl+Shift+R on Windows. Rate limits might also be more noticeable during recovery periods, particularly for AI features and heavier prompts.
Our services aim for 99.9% uptime, and we can't guarantee there won't be outages due to external infrastructure issues like this AWS situation. [1]
Is that what you were looking for?
If you still need help with the AWS-related issues or any other concerns, I’m here to assist. Would you like to provide more details about what you’re trying to resolve or understand?
Good news! We’ve heard back from the team, and the AWS issue has been resolved. Their systems are fully operational again -- and so is our platform.
Please try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if everything’s working on your end or if you’re still seeing any issues.
Thanks for your patience while we got this sorted out.
