Static IPs
Is there any updates for static IPs? I would love to use Railway for a Discord bot so everything is in the same ecosystem but because shared IPs exist I can get temporarily restricted if requests to Discord's API are shared. that's an issue another developer had, there was another bot that used the same IP and he got temporarily restricted because the other bot on another project was sending malformed requests.
If there's a risk of that and I can't assign a static IP then I can't use Railway for hosting the bot or proxy which is super upsetting for me.
Solution:Jump to solution
https://feedback.railway.app/feature-requests/p/staticdedicated-ips no near-term plans to do it yet, but on the radar
Static/Dedicated IPs | Feature Requests | Railway
Dedicated IPs for deployments
10 Replies
Project ID:
N/AN/A
hey @Ray could we have your input on this?
Solution
https://feedback.railway.app/feature-requests/p/staticdedicated-ips no near-term plans to do it yet, but on the radar
Static/Dedicated IPs | Feature Requests | Railway
Dedicated IPs for deployments
Discord's APICould you elaborate on this? I was under the impression that Discord doesn't do any IP-based rate limiting
IP addresses that make too many invalid HTTP requests are automatically and temporarily restricted from accessing the Discord API. Currently, this limit is 10,000 per 10 minutes. An invalid request is one that results in 401, 403, or 429 statuses. — Discord APII should've clarified it was CloudFlare specific. It can activate due to a variety of reasons. Rate limit exceeding and them continuing to send, if I recall this is one of them. Another is just malformed requests. yeah, so from the looks of it Railway wouldn't be a good options then unless I deployed a proxy to another service and used that API Proxy on Railway...which is just not ideal cost wise.
are the odds of someone sending 10k invalid requests high?
It's already happened to another developer and we assume as Railway becomes more and more popular it could happen more often. I find Railway extremely useful and love using it thus far and want to continue using it as much as I can and even share it with other devs.
From conversations it looks like status code 429 is a common factor. If you have even 16 failed requests a minute, which could be logical if you don't handle rate limits properly, then someone could trigger than CF ban for up to an hour (or more so I heard) on the entire IP. That's just the documented triggers, there could be others.
Not counting someone who put in their bot token and reset it that's making Discord requests with an invalid token, or when bots try to request access to resources they don't have permission too.
Not for the most part, if it's coded semi-carefully these shouldn't happen; but we can't control other devs and if Railway uses IP ranges for a region the longer and more popular the service becomes the more risky it is for Discord bots to be hosted on the platform without a proxy like Nirn sitting on another service with a dedicated IP.
ill just throw in my two cents here, static ips are very likely to be pro only, so in that regard, you could buy a proxy with a static ip for cheaper than a pro plan
I really really appreciate your transparency here. I'll mark this as resolved in the meantime though!