Live

Slow provisioning times of services in GCP europe-west4 region

Issue was resolved. Services are provisioning successfully.

The latest update from ClickHouse Cloud.

State

Resolved

Started

70 d ago

2026-08-23 10:14 UTC

Lasted

32 min

until 2026-08-23 10:47 UTC

Worst impact

Degraded

Timeline

2 updates
10:1410:2210:3010:3810:47
DegradedUpdate postedTimes in UTC

Investigating

32 min 100%

Updates

Times in UTC

As posted by ClickHouse Cloud

Resolved2026-08-23 10:47 UTC

Issue was resolved. Services are provisioning successfully.

Investigating2026-08-23 10:14 UTC

It may take longer time to provision a new service.

ClickHouse Cloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

14

Days with an incident

14

Median duration

1 h 14 min

This incident

56% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

29 h 46 min
median 1 h 14 min
90 days agoToday

Other ClickHouse Cloud incidents

All incidents

Follow ClickHouse Cloud

Your coding agent knows when ClickHouse Cloud is down, and tells you when a failure is theirs, not yours. You can also get ClickHouse Cloud incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "clickhouse" and tell me if ClickHouse Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=clickhouse
Slack
/feed subscribe https://outages.cc/feed.xml?providers=clickhouse

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane