an hour ago
Hi Railway team,
Since yesterday our custom domain nexus.qualityheating.nl (CNAME to wy6gvf3v.up.railway.app) is blocked for visitors on for example KPN business connections (“Extra Veilig Internet”, which uses Fortinet FortiGuard).
The cause is the shared edge IP the domain resolves to:
IP: 69.46.46.74
FortiGuard IP Reputation: added as “Malicious Websites” on Nov 03, 2026 @ 18:37 MST
Our hostname and up.railway.app itself are rated clean (Business / Information Technology)
So the block is caused by another tenant on the same edge IP, not by our service. This is a production app for a client and their users can’t reach it.
Could you:
Request delisting of 69.46.46.74 with FortiGuard, or
Move our service/custom domain to a different edge IP?
Also: does Railway offer a dedicated inbound IP for custom domains? The static IP feature on Pro only covers outbound traffic, so it doesn’t help here.
Thanks,
Randy
1 Replies
an hour ago
69.46.46.74 is one of our shared edge addresses, used by many services at once. We can't assign a custom domain to a specific edge IP, exclude it from one, or offer a dedicated inbound IP. Redeploying or changing regions doesn't change the edge IP your domain gets. As you noted, static IPs on Pro apply to outbound traffic only.
FortiGuard's IP rating is a filter on the visitor's network. We can't lift it from our side. FortiGuard does accept reclassification requests through its own web filter lookup, and anyone can submit one, including you or your client.
The fix that doesn't depend on any rating is to put a proxy or CDN in front of the domain. Your visitors then connect to that provider's IPs, and the provider forwards traffic to us.
Status changed to Awaiting User Response Railway • about 1 hour ago