Hello Railway Team,

I’ve deployed a Telegram bot (PropHub) on Railway, and I’m experiencing significant response delays when users interact with the bot on Telegram.

Issue details:

• Bot receives messages instantly (Telegram side is fine)

• Responses are delayed by several seconds to sometimes minutes

• This happens even for simple button interactions and lightweight API calls

• The issue is consistent, not a one-off spike

Current setup:

• Deployed on Railway (always-on service)

• Telegram Bot API webhook-based integration

• Node.js backend (lightweight request handling)

• No heavy background jobs running during interaction

• Database + external APIs are minimal and async

Why this is critical:
This is a production-facing conversational bot where UX depends heavily on real-time replies. Delayed responses severely impact user trust and usability.

What I’d like help with:

1. Whether this could be related to:

   • Cold starts / container sleep

   • CPU throttling or memory limits

   • Region or networking latency

2. Any recommended configuration changes to:

   • Keep the service warm

   • Reduce webhook response time

   • Improve Telegram webhook performance on Railway

3. Logs or metrics I can check on my end to diagnose this further

If needed, I can share:

• Project ID

• Deployment logs

• Sample timestamps showing message received vs response sent

Looking forward to your guidance on resolving this.

Thanks,
Mayur Sondagar
Developer – PropHub