Hello,

I'm frequently encountering an issue where my application works normally, but then suddenly starts returning a large number of 499 errors.

The strange part is that my server does not generate these errors at all. I've thoroughly checked my application logs, and there are no corresponding 499 responses being produced by my application. This strongly suggests that these status codes are originating somewhere within Railway's infrastructure, most likely at the proxy, load balancer, or networking layer.

The only thing that consistently resolves the issue is restarting/redeploying the service. Unfortunately, this has been happening much more frequently lately.

Could you please investigate whether there are any issues on Railway's side that could explain this behavior? If there are any infrastructure logs or diagnostics you can share, I'd appreciate it.

Please let me know if you need any additional information, such as deployment IDs, timestamps, request IDs, or service logs. I'd be happy to provide them.

Thank you for your assistance.