Discord bot blocked daily by Cloudflare 1015 on shared egress IP (us-west2)
tobz379
HOBBYOP

5 hours ago

My Discord bot (discord.js v14, Hobby, us-west2, 1 replica, with a volume) has been blocked by Discord's Cloudflare almost daily since ~28 September.

  • Every Discord API request returns 429 with text/plain "error code: 1015" and no X-RateLimit headers, so it's a Cloudflare IP ban, not Discord rate limits.
  • Retry-After is ~23h. When the ban lifts, the bot reconnects fine, then the IP gets re-banned 7–20 minutes later while my bot is idle.
  • The same bot token returns HTTP 200 from my home IP.
  • No crashes or restarts, I log every request (nowhere near Cloudflare's invalid-request threshold), and all requests are authenticated.

So it looks like another service on my shared egress IP is triggering the ban.

Questions:

  1. Can my service be moved to a different egress IP without changing region?
  2. If I change region, does the volume migrate automatically, or do I need to back it up and restore it myself?
  3. The docs say static outbound IPs "may be shared with other customers". Is there any way to get an egress IP that's only mine?

Thanks!

Awaiting User Response

1 Replies

Railway
BOT

5 hours ago

Within the same region, the only control we offer over a service's outbound IP is Static Outbound IPs, which is available on the Pro plan. When enabled, it assigns permanent IPv4 addresses tied to your service's region, and you redeploy for outbound traffic to start using them.

Those addresses are not guaranteed to be dedicated and may be shared with other customers, so there is no option for an egress IP that is only yours.

If you change region, you don't need to back up and restore the volume yourself. The volume is migrated to the new region as part of the change, which can take a while depending on its size and causes downtime for the service while it runs. Changing region also changes the outbound IPs, as described in our regions docs.


Status changed to Awaiting User Response Railway • about 5 hours ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...