Skip to content
Discord bot offline: Railway outbound connection receives Cloudflare 1015 / HTTP 429
galaxyisgaming
OP

24 days ago

My bot is marked Active in Railway, but cannot finish connecting to Discord and remains offline.

A diagnostic request made from the running container to https://discord.com/api/v10/gateway/bot returned:

HTTP status: 429

Response: Cloudflare Error 1015 — temporarily rate limited

Time: October 27, 2026, 23:08:44 UTC

Cloudflare Ray ID: a5155d4bda3005ea-IAD

Retry-After: 82617 seconds (approximately 23 hours)

Region: US East / Virginia

The locally configured bot token authenticates successfully outside Railway. The Railway Node process is running, but no BOT READY message appears.

Project ID: 66e90980-dc1b-47ee-9935-2b1be396bac3

Service ID: 1d7a295c-f8b8-4929-8fac-dbc4756ee4f1

Deployment ID: 2ac979da-d088-4331-a00a-7c39ad81534a

Could you investigate whether this is an outbound-IP restriction affecting this service, whether the IP is shared, and advise on the supported resolution? I need to preserve the existing PostgreSQL database and stored trainer data.

I found this similar report and Railway’s response. My service currently has the same Cloudflare 1015 symptoms in US East/Virginia. Can you confirm whether its outbound IP is affected by a shared-egress restriction and recommend a supported resolution? Before changing regions, please confirm the impact on my bot service, any attached volume, and its connection to the separate PostgreSQL service.

Solved$10 Bounty

Pinned Solution

Since Railway doesn't have dedicated IPs, it's possible that you may have been affected by a different service.

You can try deploying your service in a different region temporarily.

2 Replies

Status changed to Awaiting Railway Response Railway • 24 days ago


Railway
BOT

24 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • 24 days ago


Since Railway doesn't have dedicated IPs, it's possible that you may have been affected by a different service.

You can try deploying your service in a different region temporarily.


0x5b62656e5d

Since Railway doesn't have dedicated IPs, it's possible that you may have been affected by a different service. You can try deploying your service in a different region temporarily.

galaxyisgaming
OP

24 days ago

moving regions worked thanks!


Status changed to Solved 0x5b62656e5d • 24 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...