My service can reach external internet normally (e.g. https://www.google.com/generate_204 works),but consistently times out when calling https://api.telegram.org from inside the service.This affects both n8n Telegram nodes and plain HTTP requests.I have tested:Multiple redeploysDifferent regionsPlain HTTP requests (not SDK-specific)Google and other external endpoints work, but Telegram always times out.This started suddenly without changes on my side.Could you please check outbound connectivity / routing / egress from your infrastructure to api.telegram.org?

Outbound connectivity issue to api.telegram.org

finkus89

HOBBYOP

2 months ago

My service can reach external internet normally (e.g. https://www.google.com/generate_204 works),
but consistently times out when calling https://api.telegram.org from inside the service.

This affects both n8n Telegram nodes and plain HTTP requests.

I have tested:

Multiple redeploys
Different regions
Plain HTTP requests (not SDK-specific)

Google and other external endpoints work, but Telegram always times out.

This started suddenly without changes on my side.

Could you please check outbound connectivity / routing / egress from your infrastructure to api.telegram.org?

Solved

2 Replies

cherepinskiykostya-lgtm

PRO

2 months ago

man... https://station.railway.com/questions/bot-error-ef3e0945

angelo-railway

EMPLOYEE

2 months ago

I have responded in the megathread but the workaround is to use a proxy for now. Trying to work with TG to get a resolution here.

Status changed to Awaiting User Response Railway • 2 months ago

Railway

BOT

2 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 2 months ago