Dear Railway Team,

I am experiencing a critical issue with my service deployed on your platform. The observed behavior is as follows:

• The service disconnects approximately every 2 minutes.
• It then recovers automatically without triggering a new deploy or container restart.
• This is not caused by a server crash or process termination.
• During these interruptions, active connections (especially WebSockets) are dropped.

I have verified that:

• The application code is not throwing fatal errors or exceptions.
• There are no cron jobs, serverless configurations, or any visible auto-sleep/downtime settings enabled.
• I configured a /health endpoint to help keep the service alive, but it did not resolve the issue.

Additionally:

• There is an initial spike in vCPU usage when the service starts.
• After that, resource usage stabilizes, but the disconnection pattern continues consistently.
• The issue appears to follow a predictable and recurring interval.

This behavior directly impacts my application, which relies on persistent real-time connections (WebSockets) for:

• Bot command execution
• Real-time event processing and storage

For this reason, it is essential that the service remains continuously active without interruptions.

I would appreciate your assistance in clarifying:

1. Whether there are any internal mechanisms that could be causing these periodic disconnections.
2. If there are platform-level timeouts, limits, or networking policies affecting persistent connections.
3. Recommended configurations or best practices to ensure high availability for real-time applications on Railway.

Please let me know if you need any additional information to help diagnose the issue.

Thank you for your time and support.

Sincerely,

TheFabi8A