Skip to content
Outbound TCP timeout to MIMIT from US and EU regions
fuelnearapp
OP

15 days ago

Outbound TCP timeout to Italian government server from both US and EU Railway regions

Hello Railway Community,

I’m experiencing a persistent outbound connectivity issue affecting my production application.

Since October 17, 2026, my Railway backend has been unable to establish a TCP connection to the Italian Ministry of Enterprises and Made in Italy (MIMIT), preventing daily fuel-price updates.

The application had been connecting successfully until October 16, with no corresponding application deployment or code changes.

Affected destination:

Troubleshooting performed:

Initially, the backend was hosted in us-west2. TCP connections to MIMIT consistently timed out.

I subsequently migrated the production environment to Amsterdam (europe-west4-drams3a), but the issue persists.

Latest test — November 5, 2026, 18:46 UTC:

  • DNS resolution: successful.
  • TCP connection to 81.126.92.6:443: timeout after 8 seconds.
  • TLS/HTTP: connection never established.
  • HTTPS connectivity to example.com: HTTP 200.
  • Observed outbound public IPv4: 152.55.185.171.

The MIMIT server is accessible from my residential Italian connection and returns HTTP 200.

I also noticed Railway’s recent incident regarding external networks blocking Railway IP addresses.

Could Railway staff help investigate whether:

  1. TCP SYN packets to 81.126.92.6:443 are leaving Railway’s network.
  2. The destination or an upstream network is filtering Railway outbound IP addresses.
  3. This issue may be related to the recently reported external network blocks.
  4. There is a recommended way to restore connectivity without migrating the application to another provider.

The application has been unable to refresh its official fuel-price dataset for approximately 20 days.

Any assistance would be greatly appreciated.

Thank you.

Solved

1 Reply

Railway
BOT

15 days ago

Your test results fit a block at the destination end, not a fault in our outbound path. DNS resolves, other outbound HTTPS works from the same service, and the TCP connection to that one address times out in the same way from both US and EU regions. A fault on our side would not follow your service from one region to another.

The incident you mentioned, "External network blocks affecting access to Railway", is still open with status Identified. A third party has been sending scanning traffic with forged Railway source addresses, and as a result some network operators and security vendors have blocked our IP addresses. Your failures started on October 17, which is before that incident was published, so we can't confirm whether the MIMIT block comes from the same cause. The connection timing out at the TCP stage is the same symptom, though.

To restore access, ask MIMIT's network administrators or hosting provider to review any blocks or reputation listings covering your outbound IP. The incident notice explains the spoofed traffic and how they can allow legitimate access while still blocking unsolicited scanning. A block put in place by the destination's network can only be lifted by that network.


Status changed to Awaiting User Response Railway • 15 days ago


Railway
BOT

8 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 8 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...