Outbound IP sometimes resolves to AWS range instead of Railway Metal IP
eyelashsalon-hal
PROOP

a month ago

Project ID: bcf0dade-7b73-40f6-9b08-217a62b74fd5

Service: salon-absence-system

Region: US West (California, USA)

Questions:

1. Is this service currently running on Railway Metal?

The region dropdown shows "US West (California, USA)" without a "Metal (New)" tag.

2. Our outbound IP sometimes resolves to AWS ranges (e.g. 54.176.16.249, 54.219.173.227), which gets blocked by our target site's WAF.

When we get a Railway-owned IP (e.g. 162.220.232.59), everything works fine.

Is there a way to ensure outbound traffic always uses Railway's own IP range (162.220.232.0/23)?

3. Would enabling Static Outbound IP (Pro plan) guarantee a non-AWS IP address?

Environment: Docker-based service using Playwright.

Solved

1 Replies

a month ago

The Static Outbound IP feature on Pro plan would give your service a consistent outbound IP address.


Status changed to Awaiting User Response Railway about 1 month ago


Railway
BOT

a month 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 26 days ago


Loading...