# Snowflake: Major incident: INC20000082

**Summary:** Snowflake reported a major PrivateLink connectivity outage in Azure - East US 2 (Virginia), potentially causing connection errors or timeouts. It started at 2026-07-10 14:30 UTC and resolved at 2026-07-10 16:28 UTC (1 h 57 min). Telemetry indicated connectivity had recovered around 14:33 UTC, mitigating impact for most customers. _(machine-written, sol)_
- Kind: Major incident · Label: outage (model (Jev))
- Changed: 2026-07-10 14:30 UTC · Detected: 2026-10-17 18:22 UTC
- [Source: https://stspg.io/5b2zd3fp243d](https://stspg.io/5b2zd3fp243d)
- [Company: Snowflake](https://rewindex.com/company/snowflake.md)
- Versions: before (none: first archived) → after incident\_version:164/kw59fjhlv3jq@e05af759de97
- Change 1 of 1 for this incident

## What changed

**1. Added: Title**

```diff
+ INC20000082
```

**2. Added: Impact**

```diff
+ major
```

**3. Added: Status**

```diff
+ postmortem
```

**4. Added: Start time**

```diff
+ 2026-07-10 14:30 UTC
```

**5. Added: Resolved time**

```diff
+ 2026-07-10 16:28 UTC
```

**6. Added: Affected components**

```diff
+ Applications, Azure - East US 2 (Virginia) - Applications, Azure - East US 2 (Virginia) - Security and Privacy Features, Security and Privacy Features
```

**7. Added: Update** (investigating) · 2026-07-10 14:30 UTC

```diff
+ Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour. Customer experience: Customers hosted in the specified regions may be unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Users may encounter connection errors or timeouts. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. This may require DNS configuration changes for PrivateLink functionality.
```

**8. Added: Update** (identified) · 2026-07-10 15:13 UTC

```diff
+ Current status: Our telemetry indicates the PrivateLink connectivity health has recovered on July 10, 2026, at approximately 14:33 UTC, mitigating the impact for a majority of customers. We're continuing to investigate to isolate and address the source of the issue. Customer experience: Customers hosted in the specified regions may be unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Users may encounter connection errors or timeouts. ETA: An ETA is not yet available. We'll provide one as soon as possible. Incident start time: 13:26 UTC July 10, 2026
```

**9. Added: Update** (monitoring) · 2026-07-10 15:58 UTC

```diff
+ Current status: We've confirmed PrivateLink connectivity health has recovered, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified regions may have been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Users may have encountered connection errors or timeouts. Additionally, all customers using public connectivity may have been unable to access Snowsight between July 10, 2026, at 13:26 and 13:40 UTC. Incident start time: 13:26 UTC July 10, 2026 Incident end time: 14:33 UTC July 10, 2026 Preliminary root cause: Our preliminary root cause analysis identified that the load balancing infrastructure responsible for managing connections to Snowsight temporarily entered a degraded state, preventing requests from being processed successfully. We've engaged the associated Cloud Service Provider to investigate and troubleshoot this issue further.
```

**10. Added: Update** (resolved) · 2026-07-10 16:28 UTC

```diff
+ Current status: We've monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Users may have encountered connection errors or timeouts. Additionally, all customers using public connectivity may have been unable to access Snowsight between July 10, 2026, at 13:26 and 13:40 UTC. Incident start time: 13:26 UTC July 10, 2026 Incident end time: 14:33 UTC July 10, 2026 Preliminary root cause: Our preliminary root cause analysis identified that the load balancing infrastructure responsible for managing connections to Snowsight temporarily entered a degraded state, preventing requests from being processed successfully. We've engaged the associated Cloud Service Provider to investigate and troubleshoot this issue further. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.
```

**11. Added: Update** (postmortem) · 2026-07-18 01:03 UTC

```diff
+ Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC20000082](https://community.snowflake.com/s/article/INC20000082)
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2026-07-10 14:30 UTC | Major incident: INC20000082 (this change) | outage |

All Snowflake changes: [timeline](https://rewindex.com/company/snowflake/changes.md)
_Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._


---
Canonical: https://rewindex.com/change/i96d7766abaa926 · Markdown: https://rewindex.com/change/i96d7766abaa926.md · JSON: https://rewindex.com/api/v1/changes/i96d7766abaa926 · Generated 2026-10-18T01:54:28.599Z