Skip to content
Snowflake · Data and observabilityJun 8, 2026, 15:23 UTC

INC20000030

CriticalDatabaseUpdated 15h ago
Jun 8, 15:23 UTCJun 8, 16:40 UTC
Duration
1h 17m
Impact
Critical
Root cause
Database
Snowflake, 90 days
22 incidents
Affected
ApplicationsAzure - East US 2 (Virginia) - Applications
Status page

Final update

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)

Timeline

  1. Postmortem · Jun 16, 02:07 UTC
    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)
  2. Resolved · Jun 8, 16:40 UTC
    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.
  3. Monitoring · Jun 8, 15:42 UTC
    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
  4. Investigating · Jun 8, 15:23 UTC
    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.

More from Snowflake

Full history
StartedIncidentDuration
Sep 1404:48 UTCINC200002171h 21m
Sep 1107:18 UTCINC200002136h 1m
Sep 921:53 UTCINC200002111h 58m
Sep 407:34 UTCINC200001992h 36m
Sep 109:58 UTCINC200001903h 52m
Aug 3117:20 UTCINC200001882h 24m

Also caused by database

All
StartedIncidentDuration
Sep 1309:16 UTCIncident with several GitHub ServicesGitHub1h 29m
Aug 2616:17 UTCIssues performance is degraded in the USSentry4h 19m
Aug 1216:16 UTCIncident with Pull Requests and IssuesGitHub25m
Aug 818:57 UTCAccount Registration, Droplets, and Related ServicesDigitalOcean6h 3m
Jul 2817:41 UTCEvent ingestion and retrieval delays for some North America customersHubSpot2h
Jul 2419:37 UTCIncident with Pull RequestsGitHub46m

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.