CloudQuery Outage History

CloudQuery is up right now

Pingoru has recorded 5 incidents for CloudQuery: 2 in the last 12 months and 0 in the last 90 days.

Source: status.cloudquery.io

5incidents recorded
2last 12 months
0last 90 days
10 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking CloudQuery in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 142 (0%)

Incidents, newest first

Major March 2, 2026 CloudQuery Platform unavailable for some tenants 19m cloudquery.io

Started Mar 02, 2026, 11:50 AM UTC· resolved Mar 02, 2026, 12:09 PM UTC

  1. investigating Mar 02, 2026, 11:50 AM UTC

    We have identified errors that lead to the SaaS platform being unavailable for some users. We are rolling back a recent update.

  2. resolved Mar 02, 2026, 12:09 PM UTC

    This incident has now been resolved

Read the full incident report →

Minor November 18, 2025 Service outages 20h 23m cloudquery.io, cloud.cloudquery.io, api.cloudquery.io, api.cloudquery.io/plugins

Started Nov 18, 2025, 12:32 PM UTC· resolved Nov 19, 2025, 08:55 AM UTC

  1. investigating Nov 18, 2025, 12:32 PM UTC

    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.

  2. resolved Nov 19, 2025, 08:55 AM UTC

    All service are back to normal operations. The underlying issue with our cloud infrastructure provider has been mitigated, and operations are now functioning normally.

Read the full incident report →

Minor October 20, 2025 Service Disruption - Intermittent Errors 2h 51m cloudquery.io, cloud.cloudquery.io, api.cloudquery.io, api.cloudquery.io/plugins

Started Oct 20, 2025, 09:24 AM UTC· resolved Oct 20, 2025, 12:15 PM UTC

  1. investigating Oct 20, 2025, 09:24 AM UTC

    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.

  2. resolved Oct 20, 2025, 12:15 PM UTC

    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.

Read the full incident report →

Major July 18, 2025 api.cloudquery.io partially unavailable 28m api.cloudquery.io

Started Jul 18, 2025, 03:23 PM UTC· resolved Jul 18, 2025, 03:51 PM UTC

  1. investigating Jul 18, 2025, 03:23 PM UTC

    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.

  2. resolved Jul 18, 2025, 03:51 PM UTC

    Services back to normal operation

Read the full incident report →

Major June 12, 2025 Third party provider outage 1h 35m api.cloudquery.io, api.cloudquery.io/plugins

Started Jun 12, 2025, 07:25 PM UTC· resolved Jun 12, 2025, 09:00 PM UTC

  1. investigating Jun 12, 2025, 07:25 PM UTC

    The API was down due to a third party provider outage, which lasted for just over an hour.

  2. resolved Jun 12, 2025, 09:00 PM UTC

    The incident is resolved and all services are operational.

Read the full incident report →