Abuse/Threat Intelligence
danaboude
FREEOP

a month ago

Hi Railway Support,

I’m considering moving my production backend from Render to Railway.

I’m integrating with a payment gateway, and their security team requires the backend server’s public IP to have a clean reputation. They reported that the IP currently used by my Render backend appears in an abuse/threat-intelligence database with reports such as port scanning, brute force, phishing, or an exploited host.

Before subscribing to Railway, I’d like to confirm a few things:

If I deploy my backend on Railway, can I get a static outbound/public IP for my service?

Is this IP dedicated to my service, or can it be shared with other customers?

Can you confirm whether the assigned IP has a clean reputation and is not currently listed in common abuse/threat-intelligence databases?

If the IP is later reported or blocked because of activity from another customer, can Railway provide a replacement IP?

Most importantly, can you confirm that using Railway with a static outbound IP would be suitable for a payment gateway that requires IP allowlisting and a clean IP reputation?

I want to confirm this before purchasing a plan, because this is a production payment integration and I need to avoid the same IP reputation issue I’m currently experiencing with Render.

Thanks!

Solved

1 Replies

Railway
BOT

a month ago

Static Outbound IPs are available on the Pro plan and are designed for exactly this use case (third-party allowlisting). You enable them per service, and your service is assigned a stable set of three outbound IPv4 addresses that you provide to your payment gateway. However, there is no guarantee the assigned addresses are dedicated to your service - they may be shared with other customers, and dedicated (unshared) outbound IPs are not available on any plan. We do not guarantee IP reputation, do not pursue delisting if an address appears on a blocklist, and do not offer address replacements on request. A region change reassigns your service to that region's pool, but the same shared-IP caveats apply. You can read more at docs.railway.com/networking/static-outbound-ips.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

23 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 • 23 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...