Hello Railway team,

My production service in the sfo region is experiencing outbound TCP connection timeouts to two endpoints of an external provider.

Diagnostic findings:

• Both endpoints time out on TCP port 443 from the Railway container.
• The same endpoints resolve to the same IP addresses and connect successfully from my local computer.
• A control connection to example.com:443 succeeds from the container in approximately 0.02 seconds.
• The failure reproduces with Python's standard socket library, before TLS or authentication.
• No proxy environment variables were found.
• Restarting the existing deployment did not resolve the issue.
• The web application remains online and responds with HTTP 200.
• The application worked two days ago, with no recent code changes or new deployments.

We have not established whether the cause is destination-side filtering, routing, or another network issue.

For confidentiality, I am omitting the provider's identity, destination domains/IPs, and project identifiers from this message.

Could a Railway team member provide a private channel where I can share those details and request a targeted connectivity investigation? Please confirm how to provide them without making them visible to the community.

Thank you.