Outbound IP blocked by Spamhaus ZEN - need static/dedicated egress IP or clean IP
giuseppe439
PROOP

3 hours ago

Hi,

Our service adstore-app needs to reach a partner's REST API over HTTPS (443) at a

fixed destination IP. Outbound TCP connections from the container to that

destination consistently time out (confirmed via SSH into the running container,

both raw TCP connect and HTTPS requests, ~10-12s timeout), while the same

container reaches other HTTPS destinations (e.g. example.com) without any issue,

and the same partner API is reachable instantly (30-130ms) from our office

network.

The partner runs IP-based security filtering and confirmed that our outbound IP

observed from your platform, 152.55.184.65, is currently listed on Spamhaus ZEN.

Since this appears to be a shared/dynamic egress IP, we don't control it and

can't request delisting directly with Spamhaus (that typically has to come from

the network operator).

Could you help with either of these:

  1. Is it possible to move this service to a clean outbound IP?

  2. Does our plan support a static/dedicated outbound IP for this service? If so,

    how do we enable it?

We'd rather have a stable IP we can whitelist with our partner than deal with a

shared IP that may get relisted again in the future.

Awaiting User Response

1 Replies

Railway
BOT

2 hours ago

Your service does not currently have static outbound IPs enabled, so 152.55.184.65 is a dynamic egress address that can change on any redeploy. You can enable static IPs from the service's Settings tab under Networking (details at docs.railway.com/reference/static-outbound-ips), which will assign stable addresses your partner can allowlist. Those addresses are shared with other workloads, not dedicated. Dedicated outbound IPs do not exist on Railway, on any plan. We do not move a service off a specific egress address or pursue delisting with Spamhaus. If the addresses assigned after enabling static IPs also carry a listing, deploying the service to a different region is the one self-serve lever that changes the assigned pool, though reputation on those addresses is equally not guaranteed.


Status changed to Awaiting User Response Railway about 2 hours ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...