Skip to content
OutageDeck

Incident detail

An issue with unidling ClickHouse instances in Azure regions

Resolved incidentMinor

Timeline window

to

Outage alerts

Get alerted the next time ClickHouse Cloud breaks

Free email alerts for up to 5 providers — no card, live in about a minute. Paid plans add Slack, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow ClickHouse Cloud alerts work

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

  1. Identified

    We have spotted an issue where idled ClickHouse instances in Azure regions can't be woken up. Team is already working on a fix. We expect the fix to be rolled out soon.

  2. Monitoring

    A fix is deployed. Services waking up now (from idle or starting from stopped) will start as normal. Services that are currently stuck in waking will come up soon.

  3. Monitoring

    Azure region westus3 is fully operational again. All services previously stuck in waking up have started.

  4. Monitoring

    Azure eastus2 is fully operational again (all services stuck in waking started).

  5. Resolved

    All services stuck in waking in all azure regions are started now.