For context. my API doesn't spam request the Discord API only sending a few requests per second.

Did you provide an authorization header?

Yes always

My code has been working for a few months with no changes it was just today the error was shown

Answer to your original question, no. An IP rate limit would only happen if you haven't supplied the authorization header as outbound IP addresses are shared.

The other answer would be making too many invalid requests, causing Discord to temporarily rate limit you.

I'd try logging the request header and body, as they may provide some useful debugging information.

Well it has to be linked to railway

My first HTTP request doesn't contain an auth header it's only the next request after the access token that uses my bot token

The response also wasn't

{

"message": "The resource is being rate limited.",

"retry_after": 1336.57,

"global": false

}

which is provided in the developer docs relating to the discord bot token

Well, again, as mentioned above, this rate limiting is not IP-based as it seems like you have provided a valid authorization header.

All bots can make up to 50 requests per second to our API. If no authorization header is provided, then the limit is applied to the IP address.

There is no authorization header?

It's not even related to the bot

So it uses the IP address

Nevermind I misread, sorry.

Well, then yes, this is an IP based ban. Railway cannot do anything about this.

I am asking is this possible for the cause?

Well it's possible someone that's using Railway to call Discord API that also happens to share the same outbound IP address as your container.

Do outbound IPS rotate?

I think so? I wouldn't exactly say "rotate" but outbound IPs may change over time.