AWS - US East (N. Virginia): INC0129099
Incident
Report for Snowflake
Postmortem
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/INC0129024-INC0129099
Resolved
Current status: We've finished monitoring the environment and confirmed that all services are functioning properly. 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 intermittently unable to execute queries. The issue may have been more apparent when using connectors or when performing longer-running jobs.
Incident start time: 22:00 UTC March 19, 2025
Incident end time: 17:45 UTC March 20, 2025
Preliminary root cause: A network change implemented as part of the mitigation actions for recent incident INC0129024 introduced a configuration issue that generated an elevated number of request redirects for a subset of operations routed through the cloud services layer.
A root cause analysis (RCA) document will be published within seven business days.
Customer experience: Customers hosted in the specified regions may have been intermittently unable to execute queries. The issue may have been more apparent when using connectors or when performing longer-running jobs.
Incident start time: 22:00 UTC March 19, 2025
Incident end time: 17:45 UTC March 20, 2025
Preliminary root cause: A network change implemented as part of the mitigation actions for recent incident INC0129024 introduced a configuration issue that generated an elevated number of request redirects for a subset of operations routed through the cloud services layer.
A root cause analysis (RCA) document will be published within seven business days.
Monitoring
Current status: We've confirmed that correcting the network configuration has resolved the impact as expected. We'll continue to monitor the environment to ensure all services are functioning properly.
Customer experience: Customers hosted in the specified regions may have been intermittently unable to execute queries. The issue may have been more apparent when using connectors or when performing longer-running jobs.
Incident start time: 22:00 UTC March 19, 2025
Incident end time: 17:45 UTC March 20, 2025
Preliminary root cause: A network change implemented as part of the mitigation actions for recent incident INC0129024 introduced a configuration issue that generated an elevated number of request redirects for a subset of operations routed through the cloud services layer.
Customer experience: Customers hosted in the specified regions may have been intermittently unable to execute queries. The issue may have been more apparent when using connectors or when performing longer-running jobs.
Incident start time: 22:00 UTC March 19, 2025
Incident end time: 17:45 UTC March 20, 2025
Preliminary root cause: A network change implemented as part of the mitigation actions for recent incident INC0129024 introduced a configuration issue that generated an elevated number of request redirects for a subset of operations routed through the cloud services layer.
Identified
Current status: After correcting the identified network configuration issue, internal telemetry indicates the increase in request redirects affecting customer operations has subsided. We're monitoring the environment to ensure service is restored.
Customer experience: Customers hosted in the specified regions may be intermittently unable to execute queries. The issue may be more apparent when using connectors or when performing longer-running jobs.
Incident start time: 22:00 UTC March 19, 2025
Customer experience: Customers hosted in the specified regions may be intermittently unable to execute queries. The issue may be more apparent when using connectors or when performing longer-running jobs.
Incident start time: 22:00 UTC March 19, 2025
Update
Current status: We identified a network configuration issue that may be causing an increase in request redirects for some customer operations. We are currently working to correct the configuration as a potential mitigation.
Customer experience: Customers hosted in the specified regions may be intermittently unable to execute queries. The issue may be more apparent when using connectors or when performing longer-running jobs.
Incident start time: 22:00 UTC March 19, 2025
Customer experience: Customers hosted in the specified regions may be intermittently unable to execute queries. The issue may be more apparent when using connectors or when performing longer-running jobs.
Incident start time: 22:00 UTC March 19, 2025
Investigating
Current status: We're investigating an issue with Snowflake Data Cloud intermittently affecting a subset of customers using connectors. We're investigating reported HTTP 307 errors to identify a mitigation, and we'll provide an update within 60 minutes.
Customer experience: Customers hosted in the specified regions may be intermittently unable to execute queries when using connectors.
Incident start time: 22:00 UTC March 19, 2025
Customer experience: Customers hosted in the specified regions may be intermittently unable to execute queries when using connectors.
Incident start time: 22:00 UTC March 19, 2025
This incident affected: AWS - US East (N. Virginia) (Snowflake Data Warehouse (Database)).