3 months ago
Hello, since 04:00 UTC our project has been experiencing WebSocket degradation — event loss.
We haven't made any updates to the WebSocket or related code.
Could this be a networking issue on the Fastly/Railway side, or more likely something be happening on our end?
Has anyone experienced the same issue?
Thanks!
2 Replies
3 months ago
I localized the issue to the Redis Pub/Sub connection on the gateway side. At the time of the incident, live events were not reaching WebSocket clients, while Redis itself and the publisher side appeared healthy.
Were there any internal networking, or brief connectivity issues between the service and Redis around that time?
2 months ago
We do see a small number of dropped packets on the Redis connection (port 6379) between roughly 12:29 and 12:46 UTC, along with intermittent latency spikes on that same connection reaching up to 55ms in some windows (compared to the typical 0-3ms). We also see a persistent pattern of dropped packets on your Postgres connections throughout the observation window. The volumes are small and appear transient rather than sustained degradation. If you notice this recurring, let us know and we can dig deeper.
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 2 months ago