Satori incident

Issue Connecting to Snowflake

Critical Resolved View vendor source →

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

Started
Apr 01, 2026, 04:40 AM UTC
Resolved
Apr 01, 2026, 08:21 AM UTC
Duration
3h 40m
Detected by Pingoru
Apr 01, 2026, 04:40 AM 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 Azure eastus-2 (Virginia)

Update timeline

  1. investigating Apr 01, 2026, 04:40 AM UTC

    Our monitoring systems have detected an issue connecting to Snowfalke via the Satori proxy in some regions.

  2. identified Apr 01, 2026, 05:06 AM UTC

    We have identified the root cause of the issue and are preparing a fix. Customers using customer-hosted DACs will receive a notification to upgrade their DACs shortly.

  3. monitoring Apr 01, 2026, 07:42 AM UTC

    A fix has been implemented for Satori SaaS customers with no reported impact on customer Snowflake accounts. Customers with customer-hosted DACs should deploy release v.1.2614.3 immediately to mitigate the issue.

  4. resolved Apr 01, 2026, 08:21 AM UTC

    The issue has been resolved for Satori SaaS customers and customers who have upgraded to v1.2614.3 or v1.2613.4.