Matt
Static IPs
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.
15 replies
Static IPs
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.
15 replies
Static IPs
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.
15 replies