cloud.cloudquery.io recovered
Timeline · 1 update
- investigating Jun 11, 2026, 04:06 AM UTC
cloud.cloudquery.io went down
CloudQuery had 7 outages in the last 2 years totaling 25h 36m of downtime — averaging 0.3 incidents per month.
There were 7 CloudQuery outages since June 12, 2025 totaling 25h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.
cloud.cloudquery.io went down
cloudquery.io went down
We have identified errors that lead to the SaaS platform being unavailable for some users. We are rolling back a recent update.
This incident has now been resolved
We are currently investigating an incident with our cloud service provider affecting multiple services. Customers may be experiencing widespread 500 errors, and some platform features including the dashboard and API may be unavailable. We are working urgently to identify the root cause and restore normal service. Further updates will be provided as soon as more information becomes available.
All service are back to normal operations. The underlying issue with our cloud infrastructure provider has been mitigated, and operations are now functioning normally.
We're currently experiencing intermittent errors affecting some of our services. This is due to an ongoing issue with our cloud infrastructure provider in the US-EAST-1 region. Status: Our team is actively monitoring the situation. The underlying infrastructure issue is being resolved by our provider. Impact: Some users may experience increased error rates or slower response times.
We're seeing significant improvements in our service stability. The underlying DNS issue with our cloud infrastructure provider has been largely mitigated, and most operations are now functioning normally. Our team will continue to monitor the situation.
Due to a third party outage, many requests to api.cloudquery.io are currently timing out, which can have an effect on syncs. We are monitoring the situation and will provide further updates here.
Services back to normal operation
The API was down due to a third party provider outage, which lasted for just over an hour.
The incident is resolved and all services are operational.