Skip to content
OutageDeck

Incident detail

An issue with unidling ClickHouse instances in Azure regions

Resolved incidentMinor

Timeline window

to

Get alerted the next time ClickHouse Cloud breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow ClickHouse Cloud alerts work

Timeline

Incident updates

Every update ClickHouse Cloud posted, oldest to newest, exactly as it appeared on their official status page.

  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.

Keep exploring

More from ClickHouse Cloud

Neighboring incidents on ClickHouse Cloud's timeline and the rest of their record on OutageDeck.

← Older incident

Newly created instances in AWS us-east-1 are stuck provisioning or have wrong configuration

Newer incident →

Full outage on AWS me-central-1 region

All ClickHouse Cloud incidentsClickHouse Cloud live status