We've built a service which is hosted on your platform called uupsie.com.

It's a Service Status page SaaS platform - e.g. https://status.aatcorp.net/

We've noticed from the metrics whilst testing the service that every so often we see connections hanging and they are hitting the monitor 10s timeout and failing.

We thought maybe it was our checking code, however, I've since noticed errors from the workers which are reporting internal railway connection problems:

Illuminate\Broadcasting\BroadcastException: Pusher error: cURL error 28: Failed to connect to uupsie-ws.railway.internal port 8080 after 10001 ms: Timeout was reached (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://uupsie-ws.railway.internal:8080/apps/219368/events?auth_key=REDACTED&auth_timestamp=1776880741&auth_version=1.0&body_md5=660b7bb1d7f491919e4f57426e6351da&auth_signature=REDACTED. in /app/vendor/laravel/framework/src/Illuminate/Broadcasting/Broadcasters/PusherBroadcaster.php:171

This is an example, where one of our applications is talking to the websocket service (reverb) and is experiencing the same issue, however, this time we were able to rule out any Cloudflare or external issues and the problem is seeming to occur from within the railway network.

I'm working if the Railway network is seeing this as spam or ddos or something and as such is blocking connections intermittently. But this error was an internal connection, not external, which makes it weird.

I can confirm that the service was operational and reciving connections at that time, and the issue is not isolated to this one service.

We are seeing the same problem when talking to customer on-premise infrastructure endpoints, Digitalocean and others.

Could you please assist as we are a bit stuck now as we can't see the internals of the outbound traffic within railway.

Thanks,

Nick