outages.live
Live
ClickHouse CloudIncident · 2026-08-14 19:25 UTC

Network connectivity issue in AWS us-east-1

ResolvedOfficial update

This issue has been resolved. Connectivity has returned to normal.

The latest update from ClickHouse Cloud.

State

Resolved

Started

79 d ago

2026-08-14 19:25 UTC

Lasted

23 min

until 2026-08-14 19:47 UTC

Worst impact

Degraded

Timeline

2 updates
19:2519:3019:3619:4119:47
DegradedUpdate postedTimes in UTC

Monitoring

23 min 100%

Updates

Times in UTC

As posted by ClickHouse Cloud

Resolved2026-08-14 19:47 UTC

This issue has been resolved. Connectivity has returned to normal.

Monitoring2026-08-14 19:25 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.

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

69% 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

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

Resolvedresolved 9 d ago

ClickHouse Cloud·Google Cloud Outage

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

Resolvedresolved 12 d ago

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.

Resolvedresolved 20 d ago

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.

Resolvedresolved 38 d ago

ClickHouse Cloud·Some ClickPipes CDC pipes paused and can't be resumed

All stuck pipes were resumed. ClickHouse team will continue monitoring and identifying the root cause to prevent similar issues in future.

Resolvedresolved 38 d ago

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