Issue
Segment syncs to the Snowflake destination fail with the error message "timed out trying to connect" across multiple or all sources simultaneously.
Product
Segment
Environment
Segment Console
Cause
This error indicates a network-level boundary or latency blip is preventing Segment's loaders from connecting to your data warehouse. This can be caused by:
Transient Network Latency: Momentary jitter or network path latency during the connection handshake process.
Snowflake Network Policy Updates: Account-level or user-level network policies silently dropping traffic from Segment's IP addresses.
Cloud Firewall/VPC Routing Changes: Security groups, routing tables, or firewall rule updates blocking the public inbound traffic path to your Snowflake instance.
Resolution
Follow these steps to diagnose and resolve the connection timeout:
Log in to the Segment Console, navigate to your Snowflake destination, and go to Settings > Connection.
Attempt to re-authenticate the connection. If the issue was caused by a transient network blip, re-authentication will succeed and unblock subsequent syncs.
If re-authentication fails, check your Snowflake account and user configurations. Run the following command in Snowflake to see if any active network restrictions were recently modified:
SHOW PARAMETERS LIKE 'NETWORK_POLICY';Verify that Segment's regional public outbound IP addresses have not been stripped from your firewall or network policy configurations. For the US region, ensure that
52.25.130.38/32and34.223.203.0/28are explicitly allowlisted.Check Snowflake's login history to pinpoint the failure layer. Query the
INFORMATION_SCHEMA.LOGIN_HISTORY()table for the Segment loader user over the last 24 hours.If failed login records exist with network error codes, a specific Snowflake policy is rejecting the traffic.
If zero login records exist from Segment during the failure window, the traffic is being blocked at a network firewall or routing layer before reaching the database engine.