Changes / Snowflake / INC20000030
Snowflake: Critical incident: INC20000030
Summary
A critical Snowflake outage affected Snowsight in Azure - East US 2 (Virginia), potentially causing page not found errors and login failures. It started at 2026-06-08 15:23 UTC and was resolved at 2026-06-08 16:40 UTC, lasting 1 h 16 min. The service self-recovered; Snowflake later linked a completed RCA on Snowflake Community.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: INC20000030
Before: not present
After: critical
Before: not present
After: postmortem
Before: not present
After: 2026-06-08 15:23 UTC
Before: not present
After: 2026-06-08 16:40 UTC
Before: not present
After: Applications, Azure - East US 2 (Virginia) - Applications
Before: not present
After: Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes.
Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight.
Before: not present
After: Current status: During our investigation, the service self-recovered. 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 access or use Snowflake services and features using Snowsight. Customers may have experienced page not found errors or general login failures.
Workaround: There are currently no available workarounds for this issue.
Incident start time: 14:58 UTC June 08, 2026
Before: not present
After: Current status: We've monitored the environment and confirmed 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 access or use Snowflake services and features using Snowsight. Customers may have experienced page not found errors or general login failures.
Incident start time: 14:58 UTC June 08, 2026
Incident end time: 15:20 UTC June 08, 2026
Preliminary root cause: An internal system degradation occurred within backend database infrastructure that supports Snowsight in the affected region, causing Snowsight request failures. The issue was detected by system health monitoring, and automated recovery systems performed scaling and targeted infrastructure restart operations that helped to restore service. We’re continuing to investigate to confirm the underlying root cause details and the contributing factors.
A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.
Before: not present
After: 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/INC20000030](https://community.snowflake.com/s/article/INC20000030)
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: INC20000030 (this change) A critical Snowflake outage affected Snowsight in Azure - East US 2 (Virginia), potentially causing page not found errors and login failures. It started at 2026-06-08 15:23 UTC and was resolved at 2026-06-08 16:40 UTC, lasting 1 h 16 min. The service self-recovered; Snowflake later linked a completed RCA on Snowflake Community. | Major incident |
All Snowflake changes → · Snowflake profile · Markdown · JSON