We're sorry for the trouble. This matches an incident we're tracking, External network blocks affecting access to Railway: a third party has been sending scanning traffic with forged Railway source IPs, and some network providers and security services have blocked Railway IP addresses in response. The address your domain resolves to is in that range, so connections from a network that has applied such a block time out before reaching our edge. This is consistent with your test POST to another endpoint working from the same server.

We have not found a block on our edge for your client's server IP. We're working with providers to lift these blocks. In the meantime, your client can ask their hosting provider to review any blocks on Railway IP addresses and share the incident notice with them. We're still monitoring the incident.

Hello,

Since the evening of November 3, 2026, our website expressbac.com (IP 23.247.253.47) has been unable to reach our automation server hosted on Railway. Every form submission fails with this error:

cURL error 28: Connection timed out after 10001 milliseconds

Destination: primary-production-122e2.up.railway.app (69.46.46.47)

The same server reaches other external services without any issue. Railway has confirmed there is no block on their side. According to them, some hosting providers have blocked Railway IP addresses after a third party sent scanning traffic using forged Railway source IPs:

[LINK]

Could you check whether your firewall is blocking 69.46.46.47 or other Railway IP ranges, and lift that block for our account?

Thank you!

Your note works well for the hosting provider. One adjustment: rather than saying there is no block on our side in general, it is more accurate to say we found no block on our edge for 23.247.253.47.

For the [LINK] placeholder, use the incident link from our earlier reply so their network team can read the full notice about the forged scanning traffic and review their rules while keeping protections against unsolicited scans.

The block has to be lifted by whoever applied it on the network hosting your client's server, so the request is correctly addressed to that provider. We do not yet have an estimated time for all affected networks to remove their blocks, and the incident is still being worked on.