​Hello Railway Support Team,

​I am writing to report a persistent platform-level networking issue with my healing-studio deployments and to request a refund or credit compensation for the resources wasted due to this error.

​According to the automated diagnosis on my dashboard, my application starts correctly and binds to 0.0.0.0:8080, but your proxy fails to reach the container. The diagnosis explicitly states: "Contact Railway support, as this appears to be a platform-level networking issue."

​Because of this platform-side proxy failure, I have had over 20 consecutive failed deployments, which has unnecessarily consumed my account resources and proxy fees.

​Could you please help resolve the networking issue on this node and credit back the charges incurred from these failed healthcheck timeouts? I have attached a screenshot of the automated diagnosis for your reference.

​Thank you.