ClickHouse Outage History
ClickHouse is up right nowPingoru has recorded 64 incidents for ClickHouse: 62 in the last 12 months and 15 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 9 | 92 of 720 (13%) |
| May 2026 | 6 | 167 of 744 (22%) |
| June 2026 | 2 | 100 of 720 (14%) |
| July 2026 | 6 | 16 of 744 (2%) |
| August 2026 | 4 | 8 of 744 (1%) |
| September 2026 | 8 | 40 of 720 (6%) |
| October 2026 | 3 | 10 of 568 (2%) |
Incidents, newest first
Minor October 23, 2026 Degraded support ticket submission and response 2h 47m SQLConsole, Authorization, ClickHouse Cloud API
Started Oct 23, 2026, 04:51 AM UTC· resolved Oct 23, 2026, 07:39 AM UTC
- identified Oct 23, 2026, 04:51 AM UTC
"Support Ticket Creation through Cloud Console is degraded, and other Salesforce integrated functions may be impacted due to an outage reported at Salesforce status page: https://status.salesforce.com/products/Salesforce_Services. Creating support tickets through the ClickHouse Cloud Console may intermittently fail or take longer than usual. Responses to existing support tickets may also be delayed. If you have trouble submitting a support request, please email [email protected]: mailto:[email protected] or use the support chat in the Cloud Console. For reference, Salesforce service updates are available on the Salesforce status page: https://status.salesforce.com/products/Salesforce_Services. "
- resolved Oct 23, 2026, 07:39 AM UTC
Salesforce team resolved the issue that prevented users from logging in. They identified an issue with a recent release that prevented login sessions from being created. Deployed a fix forward, and access is now restored. Users can log in and open their orgs again. https://status.salesforce.com/incidents/20004512
Minor October 20, 2026 Google Cloud Outage 6h 44m GCP europe-west2
Started Oct 20, 2026, 07:39 AM UTC· resolved Oct 20, 2026, 02:23 PM UTC
- identified Oct 20, 2026, 07:39 AM UTC
Google Cloud has reported that multiple services are experiencing issues in the europe-west2 region. We are working closely with Google support to restore normal behavior and will provide an update as soon as we have more information.
- identified Oct 20, 2026, 09:52 AM UTC
This is attributed to a Google outage in europe-west2. Latest updates from Google can be found at: https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj Currently only zone B is impacted. We are migrating workloads away from this zone.
- identified Oct 20, 2026, 10:04 AM UTC
This is attributed to a Google outage in europe-west2. Latest updates from Google can be found at: https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj Currently only zone B is impacted. Clusters in this region should be operational - accepting reads and writes, but provisioning of new services currently blocked until this zone is operational.
- identified Oct 20, 2026, 01:00 PM UTC
The zone is recovering. Clickpipes is fully restored but we continue to monitor until google reports all issues have been resolved.
- monitoring Oct 20, 2026, 01:03 PM UTC
We do not see any current impact on clickpipes or ClickHouse services, with full service restored. Google has not marked the incident as resolved, so we continue to monitor.
- resolved Oct 20, 2026, 02:23 PM UTC
The issue has been resolved. All services are fully operational.
Minor October 12, 2026 Support case creation unavailable 30m
Started Oct 12, 2026, 01:55 AM UTC· resolved Oct 12, 2026, 02:26 AM UTC
- investigating Oct 12, 2026, 01:55 AM UTC
We have identified an issue that prevents customers from creating new support cases and viewing existing cases in the ClickHouse Cloud console. Affected users may see an error when loading the support page or submitting a case. ClickHouse Cloud services, queries, and data are not affected. We are rolling out a fix now and expect it in production within the next 30–60 minutes.
- resolved Oct 12, 2026, 02:26 AM UTC
The issue preventing customers from creating and viewing support cases in the ClickHouse Cloud console has been resolved. Support case functionality is working normally again. If you couldn’t open a case during the affected window, please submit it again from the console.
Minor September 24, 2026 Streaming ClickPipes degradation in AWS eu-central-1 region 29m AWS eu-central-1
Started Sep 24, 2026, 08:42 AM UTC· resolved Sep 24, 2026, 09:11 AM UTC
- investigating Sep 24, 2026, 08:42 AM UTC
We detected an issue with network configuration in eu-central-1 region which causes failures for streaming Clickpipes in this region. Team is working on remediation
- monitoring Sep 24, 2026, 09:03 AM UTC
Remediation was applied and we see signs of improvement
- resolved Sep 24, 2026, 09:11 AM UTC
Remediation was applied and we don't see signs of degradation anymore. Team will continue monitoring and investigating the root cause.
Minor September 24, 2026 Some ClickPipes CDC pipes paused and can't be resumed 33m AWS ap-northeast-2, AWS eu-west-1, AWS us-east-2, AWS ap-southeast-2 and 27 more
Started Sep 24, 2026, 08:31 AM UTC· resolved Sep 24, 2026, 09:05 AM UTC
- investigating Sep 24, 2026, 08:31 AM UTC
We are aware about an issue where CDC ClickPipes were paused and can't be operated via API. ClickHouse team is investigating the issue. The issue affects subset of customers.
- investigating Sep 24, 2026, 08:35 AM UTC
The issue happened during planned maintenance. ClickHouse team is applying a remediation to resume paused pipes.
- monitoring Sep 24, 2026, 08:46 AM UTC
We are seeing signs of improvements in most regions and pipes are resumed.
- monitoring Sep 24, 2026, 09:01 AM UTC
All regions recovered except us-east-1 region. It is also progressing and expected to be remediated soon.
- resolved Sep 24, 2026, 09:05 AM UTC
All stuck pipes were resumed. ClickHouse team will continue monitoring and identifying the root cause to prevent similar issues in future.
Minor September 23, 2026 We are investigating an issue affecting Azure eastus2 region 30m eastus2
Started Sep 23, 2026, 03:28 PM UTC· resolved Sep 23, 2026, 03:59 PM UTC
- investigating Sep 23, 2026, 03:28 PM UTC
Investigating delays to provisioning and autoscaling We are investigating an issue affecting our Kubernetes infrastructure in Azure eastus2 region. Some customers may experience delays with provisioning and autoscaling of ClickHouse clusters. We are working closely with Azure support to restore normal behavior. We’ll provide another update within 30 minutes, or sooner if we have more information.
- monitoring Sep 23, 2026, 03:36 PM UTC
We have identified the cause of the disruption and already applying the remediation. We will monitor for recovery and send update as soon as it is fully recovered.
- resolved Sep 23, 2026, 03:59 PM UTC
The configuration change was reverted and we do not observe impact anymore. The ClickHouse Cloud team will work on preventing similar situations in future.
Minor September 22, 2026 We are investigating an issue with CH servers in Azure germanywestcentral region 5h 6m germanywestcentral, eastus2, westus3
Started Sep 22, 2026, 01:19 PM UTC· resolved Sep 22, 2026, 06:25 PM UTC
- investigating Sep 22, 2026, 01:19 PM UTC
We detected an issue with CHC clusters in some Azure regions. ClickHouse cloud team is investigating. Some operations might be degraded.
- investigating Sep 22, 2026, 01:21 PM UTC
Only germanywestcentral Azure region is affected.
- investigating Sep 22, 2026, 01:31 PM UTC
Only one Availability zone is affected in germanywestcentral Azure region. The problem affects internal component (ClickHouse Keepers). Some ClickHouse Services in this region may see increased latency on inserts or DDL queries.
- investigating Sep 22, 2026, 01:49 PM UTC
The problem is caused by Azure outage in the germanywestcentral region. ClickHouse Cloud team is working with Azure support. Impact: • New ClickHouse services can't be provisioned (appear as stuck in UI). • Some services may experience higher latency due to reduced capacity.
- identified Sep 22, 2026, 02:57 PM UTC
The Azure team is working on resolution of the issue. The ClickHouse Cloud team will relay any updates related to ClickHouse clusters operation. An excerpt from Azure incident status: "As per our investigation, we believe this stemmed from multiple underlying storage systems becoming unavailable at the same time, which led to attached virtual machines becoming unresponsive, restarting unexpectedly, or being temporarily unavailable. "
- monitoring Sep 22, 2026, 03:26 PM UTC
The issue is still present on Azure infrastructure side and ClickHouse Cloud team is actively monitoring for any impact for existing ClickHouse Clusters. Correction on earlier impact description: Provisioning of new instances is expected to work. Operations like autoscaling of the ClickHouse Keeper replicas can be stuck or slow. Latency for insert and DDL queries are not affected, thanks to cross-AZ redundancy.
- monitoring Sep 22, 2026, 05:02 PM UTC
Azure support shared they are working on fixing the underlying issue, we started seeing some recovery but the incident is not completely resolved yet. We are working with Azure to get this fixed as soon as possible.
- resolved Sep 22, 2026, 06:25 PM UTC
The underlying AZ has recovered and we are fully back online.
Minor September 16, 2026 Intermittent Issues with the Support tab 13h 49m ClickHouse Cloud API
Started Sep 16, 2026, 10:16 AM UTC· resolved Sep 17, 2026, 12:05 AM UTC
- investigating Sep 16, 2026, 10:16 AM UTC
We are investigating an issue with Salesforce that is affecting our Support tab. Some users may experience errors when accessing or managing support requests. Retrying the action usually resolves the issue. Our team is working to restore normal service, and we will provide an update as soon as more information becomes available. Thank you for your patience.
- identified Sep 16, 2026, 02:24 PM UTC
We have confirmed that the impact to our Support tab is related to this Salesforce incident "Salesforce incident": https://status.salesforce.com/incidents/20004433. Salesforce is rolling out a fix, and we are seeing strong signs of recovery. We have observed no further errors for nearly an hour and will continue monitoring the situation closely. We will provide another update when the incident is resolved or if any new information becomes available.
- monitoring Sep 16, 2026, 04:15 PM UTC
We are currently in monitoring phase. No errors have been observed in 2 hours and are awaiting confirmation from Salesforce before fully resolving the incident.
- resolved Sep 17, 2026, 12:05 AM UTC
Salesforce has confirmed the incident is resolved on their end.
Minor September 15, 2026 ClickPipes failing on Kinesis in AWS us-east-1 1d 5h AWS us-east-1
Started Sep 15, 2026, 06:57 PM UTC· resolved Sep 17, 2026, 12:43 AM UTC
- investigating Sep 15, 2026, 06:57 PM UTC
Currently investigating failures on AWS us-east-1 for customers using ClickPipes on Kinesis in this region.
- identified Sep 15, 2026, 08:03 PM UTC
The issue has been identified as a change on AWS related to Kinesis IAM permissions and appears to be currently isolated to us-east-1. While we work with AWS to mitigate this issue, we recommend to update your IAM policy to include a trailing wildcard (/*) to the resource for the kinesis:RegisterStreamConsumer action like so: { "Effect": "Allow", "Action": [ "kinesis:RegisterStreamConsumer" ], "Resource": [ "arn:aws:kinesis:{REGION}:{ACCOUNT_ID}:stream/{STREAM_NAME}/*" ] } Once this is applied, you must restart your ClickPipe for the changes to take affect.
- identified Sep 15, 2026, 10:45 PM UTC
AWS has confirmed the issue on their end and are in the process of rolling back the change. The ETA for this rollback in us-east-1 is by end of day tomorrow. Signs of gradual recovery are expected in us-east-1 as the rollback progresses across AZs during this time. In the meantime, if your ClickPipe is still affected, please update your IAM policy as instructed in the previous status update.
- identified Sep 16, 2026, 03:17 AM UTC
AWS has confirmed that on September 15, 2026, beginning at 11:15 AM PDT, customers experienced elevated AccessDeniedException errors when calling the RegisterStreamConsumer API for Amazon Kinesis Data Streams (Kinesis) in the N. Virginia (us-east-1) Region. The root cause was a recent change that introduced a defect in how RegisterStreamConsumer requests are authorized, causing each request to be evaluated against the specific consumer resource (for example, arn:aws:kinesis:::stream//consumer/) rather than the stream resource (for example, arn:aws:kinesis:::stream/). As a result, IAM policies that granted kinesis:RegisterStreamConsumer only at the stream level, which previously succeeded and aligns with our published documentation, no longer matched the request and returned AccessDeniedException. AWS has begun rolling back this change in the affected Region, and expect calls that were previously permitted at the stream level to succeed again once the rollback completes on September 16, 2026, by 6:00 PM PDT. As a workaround, please update your IAM policy as instructed in the previous status update.
- identified Sep 16, 2026, 03:21 PM UTC
AWS has confirmed that on September 15, 2026, beginning at 11:15 AM PDT, customers experienced elevated AccessDeniedException errors when calling the RegisterStreamConsumer API for Amazon Kinesis Data Streams (Kinesis) in the N. Virginia (us-east-1) Region. The root cause was a recent change that introduced a defect in how RegisterStreamConsumer requests are authorized, causing each request to be evaluated against the specific consumer resource (for example, arn:aws:kinesis:::stream//consumer/) rather than the stream resource (for example, arn:aws:kinesis:::stream/). As a result, IAM policies that granted kinesis:RegisterStreamConsumer only at the stream level, which previously succeeded and aligns with our published documentation, no longer matched the request and returned AccessDeniedException. AWS has begun rolling back this change in the affected Region, and expect calls that were previously permitted at the stream level to succeed again once the rollback completes on September 16, 2026, by 6:00 PM PDT. As a workaround, please update your IAM policy as instructed in the previous status update.
- resolved Sep 17, 2026, 12:43 AM UTC
This incident has been resolved. AWS has confirmed that the Enhanced Fanhout (EFO) Kinesis pipes in us-east-1 region are fully operational. Please contact ClickHouse Support if you experience any further issues: https://console.clickhouse.cloud/support
Minor September 14, 2026 Distributed Cache performance degradation in AWS us-east-1 3h 59m us-east-1, us-east-1
Started Sep 14, 2026, 08:36 PM UTC· resolved Sep 15, 2026, 12:35 AM UTC
- investigating Sep 14, 2026, 08:36 PM UTC
ClickHouse is investigating degraded Distributed Cache performance affecting multiple ClickHouse Cloud customers. Distributed Cache is a feature currently in Private Preview. We will provide further updates as they become available.
- identified Sep 14, 2026, 09:28 PM UTC
ClickHouse has identified the cause and proceeding with remedying impacted services.
- monitoring Sep 14, 2026, 10:41 PM UTC
Impacted services have been updated and are now fully operational. ClickHouse is monitoring.
- resolved Sep 15, 2026, 12:35 AM UTC
This incident has been resolved. Distributed Cache performance in the region is back to normal. Please contact ClickHouse Support if any services in the Distributed Cache Private Preview are experiencing any remaining issues: https://console.clickhouse.cloud/support
Minor September 1, 2026 Service degradation in GCP us-central-1 19m us-central1
Started Sep 01, 2026, 04:11 PM UTC· resolved Sep 01, 2026, 04:30 PM UTC
- investigating Sep 01, 2026, 04:11 PM UTC
Due to networking issues in GCP us-central1 zone b (see https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev), ClickHouse Cloud services can be degraded as well. Symptoms can be temporarily unavailable metrics and monitoring dashboards. Creation of new services and ClickPipes pipelines can be temporarily unavailable as well. Existing ClickHouse Services are not affected and are operating normally.
- investigating Sep 01, 2026, 04:19 PM UTC
After careful investigation we could not determine any impact of the GCP service degradation: https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev (in zone b) on ClickHouse Cloud functionality.
- resolved Sep 01, 2026, 04:30 PM UTC
All systems operational. GCP incident has no impact on ClickHouse Cloud.
Minor August 23, 2026 Slow provisioning times of services in GCP europe-west4 region 32m europe-west4
Started Aug 23, 2026, 10:14 AM UTC· resolved Aug 23, 2026, 10:47 AM UTC
- investigating Aug 23, 2026, 10:14 AM UTC
It may take longer time to provision a new service.
- resolved Aug 23, 2026, 10:47 AM UTC
Issue was resolved. Services are provisioning successfully.
Minor August 17, 2026 Provisioning of new CDC pipes for Postgres might be delayed or failing 1h 53m AWS ap-northeast-2, AWS eu-west-1, AWS us-east-2, AWS ap-southeast-2 and 27 more
Started Aug 17, 2026, 03:23 PM UTC· resolved Aug 17, 2026, 05:17 PM UTC
- identified Aug 17, 2026, 03:23 PM UTC
We identified an issue where new CDC ClickPipes can't be provisioned due to dependency on GitHub availability (https://www.githubstatus.com/incidents/zkxwbgr0cnmx). Team is monitoring the issue and tries to find a possible workaround.
- monitoring Aug 17, 2026, 04:35 PM UTC
We are seeing signs of recovery. The team is closely monitoring and will report any updates. In case if any pipe gets stuck provisioning, our team can assist with manual operation to make it happen.
- resolved Aug 17, 2026, 05:17 PM UTC
This issue has been resolved. New CDC pipes for Postgres are provisioning normally.
Minor August 14, 2026 Network connectivity issue in AWS us-east-1 22m
Started Aug 14, 2026, 07:25 PM UTC· resolved Aug 14, 2026, 07:47 PM UTC
- monitoring Aug 14, 2026, 07:25 PM UTC
We noticed a network issue between 18:10–18:37 UTC affecting a small subset of services on AWS in the us-east-1 region. During that period, you may have experienced connection timeouts to your services. The issue has been resolved, and our team continues to monitor the situation.
- resolved Aug 14, 2026, 07:47 PM UTC
This issue has been resolved. Connectivity has returned to normal.
Minor August 2, 2026 We are investigating an issue in Azure eastus2 region, impacting replicas in one specific Availability Zone 4h 49m eastus2
Started Aug 02, 2026, 02:44 PM UTC· resolved Aug 02, 2026, 07:34 PM UTC
- investigating Aug 02, 2026, 02:44 PM UTC
We are aware about service degradation in Azure eastus2 region, impacting only one Availability Zone. New service provisioning time might be delayed. Customers may see increased latency.
- identified Aug 02, 2026, 03:42 PM UTC
We are applying a change, unblocking the pending replicas. We already see sign of improvements for services that have the change applied.
- identified Aug 02, 2026, 04:16 PM UTC
We still see problematic compute nodes provided by CSP, so remediation may take more time. We working closely with Azure support.
- investigating Aug 02, 2026, 05:02 PM UTC
We are still working closely with CSP support to figure out the path forward. The Azure support confirmed there is an issue with some components provided by CSP, investigation ongoing.
- monitoring Aug 02, 2026, 07:05 PM UTC
The issue seems to be resolved on the Azure side. We are monitoring before we resolve the issue.
- resolved Aug 02, 2026, 07:34 PM UTC
The issue is now resolved. All services are back to normal.
Minor July 24, 2026 Monitoring and billing impact on customer services in ap-southeast-1 8h 20m ap-southeast-1, eu-west-1, ap-southeast-1, eu-west-1
Started Jul 24, 2026, 01:07 PM UTC· resolved Jul 24, 2026, 09:28 PM UTC
- investigating Jul 24, 2026, 01:07 PM UTC
Monitoring and billing is degraded in eu-west-1. Specifically: Monitoring dashboards will not contain the latest data Metric-based notification will not be sent Missing metrics in prometheus endpoints Billing metering is not currently updating Autoscaling recommendations are not being applied
- resolved Jul 24, 2026, 04:33 PM UTC
Issue is now resolved. Currently backfilling metrics for dashboards.
- investigating Jul 24, 2026, 05:13 PM UTC
We are investigating an issue impacting customer services in ap-southeast-1. Some services may experience degraded availability.
- monitoring Jul 24, 2026, 08:55 PM UTC
The issue with monitoring and billing in ap-southeast-1 is resolved. We are now backfilling the missing data.
- resolved Jul 24, 2026, 09:28 PM UTC
Backfill of data for ap-southeast-1 is complete.
Minor July 22, 2026 CDC ClickPipes stuck in maintenance state 2h 42m AWS ap-northeast-2, AWS eu-west-1, AWS us-east-2, AWS ap-southeast-2 and 3 more
Started Jul 22, 2026, 11:53 AM UTC· resolved Jul 22, 2026, 02:36 PM UTC
- investigating Jul 22, 2026, 11:53 AM UTC
As part of our weekly upgrade process, CDC ClickPipes in eu-central-1 became stuck in maintenance state. The team is working on a mitigation.
- identified Jul 22, 2026, 12:36 PM UTC
Services in eu-central-1 have recovered. We're in the process of manually recovering ~20 services in other regions.
- identified Jul 22, 2026, 01:05 PM UTC
Most services have fully recovered. Continuing to roll out the fix to remaining 4 services (all in eu-central-1, us-east-2).
- monitoring Jul 22, 2026, 01:39 PM UTC
All services have recovered; we will continue monitoring the affected nodes and consolidating our findings. Please reach out to our support team to request access to the RCA, when available.
- resolved Jul 22, 2026, 02:36 PM UTC
The CDC ClickPipes upgrade rollout remains on hold while we confirm we can safely proceed without triggering the underlying pod networking failure mode that triggered the incident.
Minor July 15, 2026 AWS eu-central-1 performance degradation 2h 25m
Started Jul 15, 2026, 11:33 PM UTC· resolved Jul 16, 2026, 01:59 AM UTC
- investigating Jul 15, 2026, 11:33 PM UTC
We are seeing degraded performance in AWS eu-central-1 starting around 4 pm PT. https://health.aws.amazon.com/health/status
- resolved Jul 16, 2026, 01:59 AM UTC
AWS has mitigated the disruption affecting the eu-central-1 availability zone. We will continue monitoring to ensure stability.
Minor July 8, 2026 Cloud console UI down 5m SQLConsole, Authorization, ClickHouse Cloud API
Started Jul 08, 2026, 07:30 PM UTC· resolved Jul 08, 2026, 07:36 PM UTC
- investigating Jul 08, 2026, 07:30 PM UTC
The backend services are not impacted but the cloud console UI is down.
- resolved Jul 08, 2026, 07:36 PM UTC
The Cloud Console is back up.
Minor July 6, 2026 Slow provisioning and operations in AWS us-east-1 region 2h 29m us-east-1, us-east-1
Started Jul 06, 2026, 12:34 PM UTC· resolved Jul 06, 2026, 03:03 PM UTC
- identified Jul 06, 2026, 12:34 PM UTC
We have identified an issue with provisioning of new instances and autoscaling operations in AWS us-east-1 region. Connection latencies for CH servers can be also affected due to slow provisioning of compute nodes. ClickHouse Cloud is working with AWS support team to fix the issue.
- identified Jul 06, 2026, 01:09 PM UTC
The issue is caused by AWS outage, please see https://health.aws.amazon.com/health/status
- resolved Jul 06, 2026, 03:03 PM UTC
The incident was resolved and we don't see any impact in us-east-1 region anymore. For details, please refer to the AWS Health status page: https://health.aws.amazon.com/health/status
Minor July 1, 2026 Issue with creating new ClickPipes in GCP regions 19m
Started Jul 01, 2026, 12:04 PM UTC· resolved Jul 01, 2026, 12:24 PM UTC
- investigating Jul 01, 2026, 12:04 PM UTC
ClickHouse Cloud team is investigating an issue with creating new ClickPipes in GCP. Provisioning of new pipes might be delayed or stuck.
- identified Jul 01, 2026, 12:17 PM UTC
We identified the cause of the issue and the team have applied a fix
- resolved Jul 01, 2026, 12:24 PM UTC
The fix was applied and we see the issue is not reproducing anymore.
Minor June 3, 2026 Prometheus metrics endpoint missing per-server metri 2d 6h asia-southeast1, ap-south-1, us-east-1, ap-southeast-2 and 38 more
Started Jun 03, 2026, 02:48 PM UTC· resolved Jun 05, 2026, 09:03 PM UTC
- resolved Jun 03, 2026, 02:48 PM UTC
The customer-facing Prometheus metrics endpoint missing all per-server metrics and is only returning Cloud-infra metrics
- resolved Jun 05, 2026, 09:02 PM UTC
-
- resolved Jun 05, 2026, 09:03 PM UTC
The customer-facing Prometheus metrics endpoint missing all per-server metrics and is only returning Cloud-infra metrics
Minor June 1, 2026 Connectivity issues in AWS eu-west-1 region 5h 7m eu-west-1, eu-west-1
Started Jun 01, 2026, 11:45 AM UTC· resolved Jun 01, 2026, 04:53 PM UTC
- investigating Jun 01, 2026, 11:45 AM UTC
Connectivity to services is affected.
- investigating Jun 01, 2026, 11:59 AM UTC
Impact is on eu-west-1 region. Incident name had a typo in the beginning.
- identified Jun 01, 2026, 12:42 PM UTC
The root cause of issue is identified
- monitoring Jun 01, 2026, 01:53 PM UTC
The root cause was identified and issue was fixed. Connectivity issues should not happen again.
- resolved Jun 01, 2026, 04:53 PM UTC
Issue is resolved.
Minor May 28, 2026 New service provisioning may fail in Azure 5d 2h germanywestcentral, eastus2, westus3
Started May 28, 2026, 06:26 PM UTC· resolved Jun 02, 2026, 09:19 PM UTC
- investigating May 28, 2026, 06:26 PM UTC
Due to extremely slow response time for some API calls to Azure infrastructure, new service provisioning may timeout before Cloud Control Plane or OpenAPI request gets response.
- identified May 29, 2026, 09:12 PM UTC
Azure confirmed the issue is related to an ongoing backend DNS zone migration. The issue is transient but we are working with Azure team to find a resolution to this issue.
- resolved Jun 02, 2026, 09:19 PM UTC
Service provisioning is working, but some users may intermittently see an error message stating: “This service name is already in use.” This error is transient. If you encounter it, please refresh the page -your service should still be provisioning and will become visible shortly. We are working with Microsoft Azure to fully resolve the underlying issue.
Minor May 27, 2026 ClickHouse Agents Login Issues 1h 22m ClickHouse Agents
Started May 27, 2026, 05:48 PM UTC· resolved May 27, 2026, 07:11 PM UTC
- investigating May 27, 2026, 05:48 PM UTC
Issues logging into ClickHouse Agents reported
- monitoring May 27, 2026, 06:03 PM UTC
Mitigation rolled out, monitoring.
- resolved May 27, 2026, 07:11 PM UTC
Some users may have been unable to log in to ClickHouse Agents due to an overly broad login rate limit. A configuration change was rolled out, access has been confirmed restored, and no customer data or ClickHouse services were impacted.