14 days ago
Hello Railway Technical Support,
We need to confirm our application's outbound network configuration to comply with Shopify's mandatory public-app IP allowlist requirement by November 20, 2026.
Environment
- Workspace plan: Hobby
- Application service:
inventory-watcher-app - Environment: production
- Region:
asia-southeast1-eqsg3a(Singapore) - Runtime: Node.js, making server-side Shopify Admin GraphQL requests
Verified Shopify evidence
A successful GraphQL request was observed from Google LLC ASN AS396982.
Shopify's 30-day simulation using the observed request IP reported 0 of 44,150 requests would be blocked.
However, Shopify Support correctly explained that this historical result does not establish coverage of future dynamic Railway outbound addresses.
Please clarify:
- Does Railway Hobby use dynamic public outbound IP addresses for this service?
- Which provider ASN(s) and source countries can its outgoing requests use, including failover or infrastructure changes?
- Can those ASNs change without notice?
- Are static outbound IPs available on Hobby, or is Pro required?
- What is Railway's recommended approach for configuring Shopify's IP/ASN allowlist safely without changing the current deployment?
We need a reliable, documented network restriction before enabling Shopify enforcement.
This is an information-only request. Please do not modify or redeploy the service.
Thank you,
Qneolabs
3 Replies
14 days ago
Without Static Outbound IPs, a service's outbound address isn't a fixed one you can allowlist. The address Shopify saw in its 30-day check isn't guaranteed to stay the same, so it shouldn't be the basis for enforcement.
Static Outbound IPs are only available on the Pro plan, not Hobby. On Pro, you turn them on per service with the Enable Static IPs toggle in the Networking section of the service's settings. The service gets three IPv4 addresses for the region it's deployed in, and outbound traffic from all replicas is spread across them.
Turning them on only takes effect after a redeploy, so it can't be set up without changing the current deployment. Your service would also get new addresses if you moved it to another region. The addresses aren't guaranteed to be dedicated to you and may be shared with other customers.
For an allowlist you can rely on, use the specific static IPs assigned to the service rather than a provider ASN or a single address you've seen before. Full details are in Static Outbound IPs.
Status changed to Awaiting User Response Railway • 14 days ago
Railway
Without Static Outbound IPs, a service's outbound address isn't a fixed one you can allowlist. The address Shopify saw in its 30-day check isn't guaranteed to stay the same, so it shouldn't be the basis for enforcement. Static Outbound IPs are only available on the Pro plan, not Hobby. On Pro, you turn them on per service with the **Enable Static IPs** toggle in the Networking section of the service's settings. The service gets three IPv4 addresses for the region it's deployed in, and outbound traffic from all replicas is spread across them. Turning them on only takes effect after a redeploy, so it can't be set up without changing the current deployment. Your service would also get new addresses if you moved it to another region. The addresses aren't guaranteed to be dedicated to you and may be shared with other customers. For an allowlist you can rely on, use the specific static IPs assigned to the service rather than a provider ASN or a single address you've seen before. Full details are in [Static Outbound IPs](https://docs.railway.com/networking/static-outbound-ips).
14 days ago
Thank you. The Pro/static-IP requirements are clear.
Our remaining question concerns the existing Hobby deployment, without upgrading or redeploying.
Can Railway confirm the possible outbound ASN(s) and source countries for inventory-watcher-app in Singapore, including whether these can change during failover?
Shopify supports ASN/country allowlists for dynamic IP hosting. Is there an authoritative, supported way to determine a complete and reliable policy for Railway Hobby?
If Railway cannot provide that guarantee, please confirm explicitly so we can evaluate Pro/static IPs as a separate infrastructure decision.
We would appreciate clarification from a Railway network specialist. Please do not modify the service.
Status changed to Awaiting Railway Response Railway • 14 days ago
14 days ago
We can't give you a guaranteed list of outbound ASNs or source countries for a Hobby service's dynamic egress. That holds for inventory-watcher-app in Singapore, including during failover or infrastructure changes. An ASN or country policy built from addresses you have seen so far, such as AS396982, isn't something we can confirm will cover all of its future outbound traffic.
To answer your question directly, we don't offer a supported way to get a complete, reliable allowlist for Hobby's dynamic outbound traffic. The supported option for a fixed allowlist is Static Outbound IPs on Pro. Each service gets its own set of addresses for its region, and those addresses only change if you move the service to a different region.
Status changed to Awaiting User Response Railway • 14 days ago
7 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 • 7 days ago