Snowflake logo
COMMUNITY SUPPORT STATUS API

All Systems Operational

About This Site

Welcome to Snowflake's home for real-time and historical data on system performance.

AWS - US West (Oregon) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
AWS - GovCloud (US-West) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
AWS - US West (Commercial Gov - Oregon) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
AWS - Canada (Central) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
AWS - US East (Ohio) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
AWS - US East (N. Virginia) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
AWS - GovCloud (US-East) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
AWS GovCloud - DoD Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
AWS - South America (São Paulo) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
AWS - Europe (Ireland) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
AWS - Europe (London) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
AWS - Europe (Paris) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
AWS - Europe (Zürich) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
AWS - Europe (Frankfurt) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
AWS - Europe (Stockholm) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
AWS - Asia Pacific (Mumbai) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
AWS - Asia Pacific (Singapore) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
AWS - Asia Pacific (Jakarta) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
AWS - Asia Pacific (Seoul) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
AWS - Asia Pacific (Sydney) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
AWS - Asia Pacific (Osaka) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
AWS - Asia Pacific (Tokyo) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
Azure - West US 2 (Washington) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
Azure - South Central US (Texas) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
Azure - Central US (Iowa) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
Azure - Canada Central (Toronto) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
Azure - East US 2 (Virginia) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
Azure - US Gov (Virginia) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
Azure - Mexico (Central) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
Azure - North Europe (Ireland) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
Azure - UK South (London) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
Azure - West Europe (Netherlands) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
Azure - Switzerland North (Zürich) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
Azure - UAE North (Dubai) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
Azure - Central India (Pune) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
Azure - Southeast Asia (Singapore) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
Azure - Central Korea (Seoul) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
Azure - Japan East (Tokyo, Saitama) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
Azure - Australia East (New South Wales) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
GCP - US Central 1 (Iowa) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
GCP - US East 4 (N. Virginia) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
GCP - Europe West 2 (London) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
GCP - Europe West 4 (Eemshaven) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
GCP - Europe West 3 (Frankfurt) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
GCP - Middle East (Dammam) Operational
Snowflake Data Warehouse (Database) Operational
Snowpipe (Data Ingestion) Operational
Replication Operational
Snowsight Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Jun 12, 2025
GCP - US Central 1 (Iowa): INC0135537
Resolved - Current status: We've implemented the fix for this issue and 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.

Customer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features.

Incident start time: 02:22 UTC June 12, 2025
Incident end time: 06:10 UTC June 12, 2025

Preliminary root cause: A configuration issue with a set of core services in the region resulted in an inability to access or use the Snowflake service.

A root cause analysis (RCA) document will be published within seven business days.
Jun 12, 03:01 PDT
Monitoring - Current status: We've implemented the fix for this issue, 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 access or use Snowflake services and features.

Incident start time: 02:22 UTC June 12, 2025
Incident end time: 06:10 UTC June 12, 2025

Preliminary root cause: A configuration issue with a set of core services in the region resulted in an inability to access or use the Snowflake service.
Jun 12, 01:24 PDT
Update - Current status: The fix to the affected core services has been successfully rolled out. We are closely monitoring key metrics to ensure full recovery across all services. We will provide another update within 60 minutes.

Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features.

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.

Incident start time: 02:22 UTC June 12, 2025
Jun 12, 00:48 PDT
Update - Current status: We have rolled out a fix to the affected core services and are seeing signs of recovery. We are closely monitoring key metrics to ensure recovery persists. We'll provide another update within 60 minutes.

Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features.

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.

Incident start time: 02:22 UTC June 12, 2025
Jun 11, 23:41 PDT
Update - Current status: We're continuing to roll out a fix to the affected core services and monitoring key metrics to ensure a full recovery. We'll provide another update within 60 minutes.

Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features.

ETA: Our current estimate is that service will be restored within 1 hour. In the meantime, we recommend that affected customers using replication initiate their failover procedures.

Incident start time: 02:22 UTC June 12, 2025
Jun 11, 22:44 PDT
Identified - Current status: We've identified a configuration issue with a set of core services in the region, and we're developing and implementing a fix to restore service. We'll provide another update within 60 minutes.

Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features.

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.

Incident start time: 02:22 UTC June 12, 2025
Jun 11, 21:33 PDT
Update - Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another update within 60 minutes.

Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features.

Incident start time: 02:22 UTC June 12, 2025
Jun 11, 20:58 PDT
Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes.

Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features.

Incident start time: 02:22 UTC June 12, 2025
Jun 11, 19:56 PDT
Jun 11, 2025
INC0135370
Resolved - Current status: We've completed our effort to reprocess the backlog of account organization metadata and monitored the environment to validate that service is restored. If you experience additional issues or have questions, please open a support case via Snowflake Community.

Customer experience: A subset of customers hosted in the specified regions were unable to access Snowflake services and features, or were experiencing replication failures related to missing account organization metadata. This could have resulted in HTTP 404 errors or failures when attempting to use Snowflake services and features that rely on organization name metadata or the [orgname]-[account_name] URL format. Additionally, affected customers may have experienced failures when attempting to manage failover groups.

Workaround: For some impact scenarios, such as access via Snowsight or connectors, customers may have been able to work around this issue by switching from an account name format (e.g., [orgname]-[account_name]) to a region-based account locator format, such as [account_locator].[cloud_region_id]. Users could have reviewed the following documentation https://docs.snowflake.com/en/user-guide/admin-account-identifier#using-an-account-locator-as-an-identifier for more information on account identifier formats.

Incident start time: 19:42 UTC June 09, 2025
Incident end time: 19:18 UTC June 11, 2025

Preliminary root cause: We determined this issue was the result of a recent configuration change that impacted a system service responsible for replicating account metadata across U.S. regions supporting public sector workloads.

A root cause analysis (RCA) document will be published within seven business days.
Jun 11, 13:50 PDT
Update - Current status: We are continuing to reprocess the backlog of account organization metadata to fully resolve the issue. As this work progresses across different regions, customers may experience service recovery at different times. Based on the current progress, we are updating our estimated time for full recovery to 20:00 UTC on June 11, 2025.

Customer experience: A subset of customers hosted in the specified regions are unable to access Snowflake services and features, or are experiencing replication failures related to missing account organization metadata. This can result in HTTP 404 errors or failures when attempting to use Snowflake services and features that rely on organization name metadata or the [orgname]-[account_name] URL format. Additionally, affected customers may experience failures when attempting to manage failover groups.

Workaround: For some impact scenarios, such as access via Snowsight or connectors, customers may be able to work around this issue by switching from an account name format (e.g. [orgname]-[account_name]) to a region-based account locator format, such as [account_locator].[cloud_region_id]. Please see https://docs.snowflake.com/en/user-guide/admin-account-identifier#using-an-account-locator-as-an-identifier for more information on account identifier formats.

ETA: 20:00 UTC June 11, 2025

Incident start time: 19:42 UTC June 09, 2025
Jun 11, 01:18 PDT
Update - Current status: We are continuing to reprocess the backlog of account organization metadata to fully resolve the issue. As this completes across different regions, customers will experience service recovery at different times. We are continuing to investigate options to more quickly process the backlog, but based on the current progress, we expect this to complete by 08:00 UTC on June 11, 2025.

Customer experience: A subset of customers hosted in the specified regions are unable to access Snowflake services and features, or are experiencing replication failures related to missing account organization metadata. This can result in HTTP 404 errors or failures when attempting to use Snowflake services and features that rely on organization name metadata or the [orgname]-[account_name] URL format. Additionally, affected customers may experience failures when attempting to manage failover groups.

Workaround: For some impact scenarios, such as access via Snowsight or connectors, customers may be able to work around this issue by switching from an account name format (e.g. [orgname]-[account_name]) to a region-based account locator format, such as [account_locator].[cloud_region_id]. Please see https://docs.snowflake.com/en/user-guide/admin-account-identifier#using-an-account-locator-as-an-identifier for more information on account identifier formats.

ETA: 08:00 UTC June 11, 2025

Incident start time: 00:10 UTC June 10, 2025
Jun 10, 15:02 PDT
Update - Current status: We have taken action to revert the configuration update causing the issue; however, a backlog of account organization metadata must be reprocessed to fully resolve the impact, which may take several hours to complete. In parallel, we are investigating options to more quickly process the backlog, and we'll provide another update within 2 hours.

Customer experience: A subset of customers hosted in the specified regions are unable to access Snowflake services and features, or are experiencing replication failures related to missing account organization metadata. This can result in HTTP 404 errors or failures when attempting to use Snowflake services and features that rely on organization name metadata or the [orgname]-[account_name] URL format. Additionally, affected customers may experience failures when attempting to manage failover groups.

Workaround: For some impact scenarios, such as access via Snowsight or connectors, customers may be able to work around this issue by switching from an account name format (e.g. [orgname]-[account_name]) to a region-based account locator format, such as [account_locator].[cloud_region_id]. Please see https://docs.snowflake.com/en/user-guide/admin-account-identifier#using-an-account-locator-as-an-identifier for more information on account identifier formats.

ETA: An ETA is not yet available.

Incident start time: 00:10 UTC June 10, 2025
Jun 10, 13:05 PDT
Identified - Current status: We've identified a recent configuration update that impacted a system service that facilitates replication of account metadata across U.S. regions supporting public sector workloads. We're developing and implementing a fix to restore service. We'll provide another update within 2 hours.

Customer experience: A subset of customers hosted in the specified regions are unable to access Snowflake services and features, or are experiencing replication failures related to missing account organization metadata. This can result in HTTP 404 errors or failures when attempting to use Snowflake services and features that rely on organization name metadata or the [orgname]-[account_name] URL format. Additionally, affected customers may experience failures when attempting to manage failover groups.

Workaround: For some impact scenarios, such as access via Snowsight or connectors, you may be able to workaround this issue by switching the account format you are using from an account name format (e.g. [orgname]-[account_name]) to a regioned account locator format, such as [account_locator].[cloud_region_id]. Please see https://docs.snowflake.com/en/user-guide/admin-account-identifier#using-an-account-locator-as-an-identifier for more information on account identifier formats.

ETA: An ETA is not yet available.

Incident start time: 00:10 UTC June 10, 2025
Jun 10, 11:06 PDT
Jun 10, 2025
GCP - Europe West 2 (London): INC0135432
Resolved - Current status: We've implemented the fix for this issue and 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.

Customer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight.

Incident start time: 01:31 UTC June 11, 2025
Incident end time: 04:11 UTC June 11, 2025

Preliminary root cause: The preliminary investigation points to a degradation of the repository for deployment metadata, which impacted connectivity.

A root cause analysis (RCA) document will be published within seven business days.
Jun 10, 21:50 PDT
Monitoring - Current status: We've implemented the fix for this issue, 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 access or use Snowflake services and features using Snowsight.

Incident start time: 01:31 UTC June 11, 2025
Incident end time: 04:11 UTC June 11, 2025

Preliminary root cause: The preliminary investigation points to a degradation of the repository for deployment metadata, which impacted connectivity.
Jun 10, 21:24 PDT
Identified - Current status: We're continuing to develop and implement a fix to restore service. We'll provide another update within 60 minutes.

Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight.

ETA: An ETA is not yet available.

Incident start time: 01:31 UTC June 11, 2025
Jun 10, 21:05 PDT
Update - Current status: We're continuing to investigate the issue with Snowflake Data Cloud. Recent network policy changes are being reviewed. We'll provide another update within 60 minutes.

Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight.

Incident start time: 01:31 UTC June 11, 2025
Jun 10, 20:17 PDT
Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes.

Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight.

Incident start time: 01:31 UTC June 11, 2025
Jun 10, 19:19 PDT
Jun 9, 2025

No incidents reported.

Jun 8, 2025

No incidents reported.

Jun 7, 2025

No incidents reported.

Jun 6, 2025

No incidents reported.

Jun 5, 2025

No incidents reported.

Jun 4, 2025

No incidents reported.

Jun 3, 2025

No incidents reported.

Jun 2, 2025

No incidents reported.

Jun 1, 2025

No incidents reported.

May 31, 2025

No incidents reported.

May 30, 2025

No incidents reported.

May 29, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage