outages.live
Live
ClickHouse CloudIncident ·

Provisioning and scaling operations may take longer in AWS ap-northeast-1 Tokyo

DegradedOfficial update
0

Provisioning and scaling operations may take longer than usual in the AWS ap-northeast-1 Tokyo region. ClickHouse Cloud has identified the issue. The issue is reported on the AWS status page.

State

Identified

Started

Ongoing for

1 h 44 min

Worst impact

Degraded

Timeline

1 update
16:0516:3116:5717:2317:49
DegradedUpdate postedTimes in UTC

Identified

1 h 44 min 100%

Updates

Times in UTC

As posted by ClickHouse Cloud

Identified

Scaling and provisioning operations may take longer than usual. Issue is reported on AWS status page

ClickHouse Cloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

16

Days with an incident

16

Median duration

50 min

This incident

2.1× the median

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

29 h 46 min
median 50 min
90 days agoToday

Other ClickHouse Cloud incidents

All incidents

ClickHouse Cloud·SQL Console database connection outage

ClickHouse Cloud reported a SQL Console database connection outage. The outage affected Dashboards, Query endpoints, Saved queries, and UDFs. ClickHouse Cloud resolved the incident after 50 minutes.

Resolved

ClickHouse Cloud·Degraded support ticket submission and response

``` 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 ```

Resolved

ClickHouse Cloud·Google Cloud Outage

The issue has been resolved. All services are fully operational.

Resolved

ClickHouse Cloud·Support case creation unavailable

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.

Resolved

ClickHouse Cloud·Streaming ClickPipes degradation in AWS eu-central-1 region

Remediation was applied and we don't see signs of degradation anymore. Team will continue monitoring and investigating the root cause.

Resolved

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.live/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.live/feed.xml?providers=clickhouse
Slack
/feed subscribe https://outages.live/feed.xml?providers=clickhouse

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane