Satori incident

Issue Connecting to Snowflake

Notice Resolved View vendor source →

Satori experienced a notice incident on July 21, 2026 affecting Satori DAC AWS us-east-1 (N. Virginia) and Satori DAC AWS us-west-2 (Oregon) and 1 more component, lasting 1d 1h. The incident has been resolved; the full update timeline is below.

Started
Jul 21, 2026, 04:12 PM UTC
Resolved
Jul 22, 2026, 05:33 PM UTC
Duration
1d 1h
Detected by Pingoru
Jul 21, 2026, 04:12 PM UTC

Affected components

Satori DAC AWS us-east-1 (N. Virginia)Satori DAC AWS us-west-2 (Oregon)Satori DAC AWS eu-central-1 (Frankfurt)Satori DAC AWS eu-west-1 (Ireland)Satori DAC GCP eu-west2 (London)Satori DAC GCP us-east1 (S. Carolina)Satori DAC AWS ap-southeast-1 (Singapore)Satori DAC Azure eastus-2 (Virginia)Customer Hosted DAC

Update timeline

  1. investigating Jul 21, 2026, 04:12 PM UTC

    Our monitoring systems have detected a change in Snowflake that may impact the availability of the Satori-generated hostname for Snowflake.

  2. investigating Jul 22, 2026, 05:27 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jul 22, 2026, 05:28 PM UTC

    A fix has been deployed to Satori SaaS DACs and is available in v1.2629.3 and v1.2630.1.

  4. resolved Jul 22, 2026, 05:33 PM UTC

    This incident has been resolved.