Severe Connection Delays
ddotx
PROOP

7 months ago

I am writing to report a critical performance issue with my paid plan service. The problem of severe initial latency continues, making the service unreliable.

Latest Performance Data:

I have just captured a new network trace showing a total load time of 7.47 seconds. The breakdown clearly isolates the problem to your platform's connection handling:

  • Initial Connection: Took an unacceptable 6.81 seconds.

  • SSL Handshake: Accounted for 3.67 seconds of that connection time.

  • Waiting for Response (TTFB): Crucially, once the connection was finally made, my application's response time was excellent at ~332ms.

Conclusion:

This new data proves that my application code is performing perfectly. The entire 7-second delay is happening before my application even receives the request. An Initial Connection time of nearly 7 seconds for a paid, "always-on" service is a critical failure.

Please investigate this with high priority. What is causing a 6-7 second connection delay on your platform for a service in the asia-southeast1 region?

Thank you

Solved

7 Replies

Railway
BOT

7 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!


ddotx
PROOP

7 months ago

Is it a cold start?


brody
EMPLOYEE

7 months ago

Hey,

We don't have cold starts (unless you have serverless enabled and you don't).

So this is something else, and for help with that, could you please give us some timestamps in UTC so we can cross-reference your times to our internal metrics.

Best,
Brody


Status changed to Awaiting User Response Railway 7 months ago


ddotx
PROOP

7 months ago

Looks like it's back to normal now. I think that 'Railway – Elevated deployment latency' incident was the cause.


Status changed to Awaiting Railway Response Railway 7 months ago


brody
EMPLOYEE

7 months ago

That had nothing to do with connection latency, that was in regards to the time it took to start building new code.


Status changed to Awaiting User Response Railway 7 months ago


brody

That had nothing to do with connection latency, that was in regards to the time it took to start building new code.

ddotx
PROOP

7 months ago

Thank you. Let me monitor it for a couple of hours to confirm the issue is resolved.


Status changed to Awaiting Railway Response Railway 7 months ago


Circling back, how are we holding up here.


Status changed to Awaiting User Response Railway 7 months ago


Status changed to Solved ddotx 7 months ago


Loading...