Same here. Any updates from Railway's team?

We're aware that Telegram bots deployed on Railway are currently experiencing connectivity issues due to Telegram blocking our IP range.

We've immediately escalated this to the Telegram team and are actively working toward a resolution. In the meantime, if you need to restore service urgently, you may want to explore temporary routing options (like using a proxy or alternative deployment) while we work this out on our end.

We'll update you as soon as we have more information from Telegram.

Hi, I have similar problem. The Telegram Trigger is not working. It works for me if the workload is not published and if I execute the workflow, the Telegram Trigger is firing on a message in the Telegram Bot. However, once I publish the workflow, it stops working. Is it the same problem or a different one?

Hi there, this is likely the same issue other users are facing due to Telegram blocking our IP range. This is why your bot works fine when running locally or in test mode but fails once it's live on Railway.

We've escalated this directly to Telegram and are working on a resolution. In the meantime, you can route your Telegram API requests through a proxy service to get around the block.

We'll share updates as soon as we hear back from Telegram.

Best,
The Railway Team

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!

🛠️ The ticket Outbound connection issues in EU region has been marked as triage.

Just a quick follow up - sharing this workaround that a user posted that has been helpful to other users (while we sort this out in case it helps you) https://station.railway.com/questions/bot-error-ef3e0945#nrsa

We're really very sorry for the inconvenience

Update: the Railway team is still trying to get in contact with the TG team. You can use the above workaround or use the one-click deploy that uses CF Workers to set up a proxy to allow you to proxy requests to get around the connection issue.

https://railway.com/deploy/tg-cloudflare-worker-proxy-workaround?referralCode=N8f7Nb&utm_medium=integration&utm_source=template&utm_campaign=generic

Hi - we never heard back from Telegram, but as far as we can see our addresses are no longer blocked. It is possible you could see infrequent occasional impacts due to rate limiting. Please let us know if you are still encountering the issue.

Still not working please fix this

Can you make your own thread on this? Would love to investigate!