Hey,

A 502 Bad Gateway on Telegram API calls can come from either Telegram itself (transient errors happen sometimes) or from something in your own infra (proxy, hosting).

A few things to check:

Test directly from your server: curl https://api.telegram.org/bot/getMe — if that also returns 502, it's a network/connectivity issue, not your bot's code.

Are you using a webhook or long polling? If webhook, check getWebhookInfo to see the last error Telegram recorded.

If you have a proxy in front (nginx, Cloudflare, etc.), check its logs too, not just your app's — a 502 there usually means your bot didn't respond in time.

Add retry with backoff, since Telegram occasionally has brief 502 blips.

Also worth checking Telegram's status/outage channels to see if others are reporting issues right now.

A 502 here can come from either Telegram itself or from the Railway service that’s receiving the webhook.

I’d first test the Telegram API directly from the Railway app:

curl -i "https://api.telegram.org/bot${BOT_TOKEN}/getMe"

If that returns 200, then the bot token and Railway -> Telegram connectivity are probably fine.

Next, check the webhook status:

curl -s "https://api.telegram.org/bot${BOT_TOKEN}/getWebhookInfo"

The useful fields are:

• url
• pending_update_count
• last_error_message

If Telegram is getting a 502 when calling your webhook, then I’d check the Railway service config next. Make sure the app is listening on 0.0.0.0 and on Railway’s $PORT, and that the public domain is pointing to the correct port.

If getMe returns 502 from Railway but works on your local machine, that would point more toward a network/connectivity issue.

Also, are you using webhook or long polling, and what framework/runtime is the bot using?

Don’t share the bot token publicly.