Private network timeout from API/Worker to Redis after May 20 incident
uzanenis
HOBBYOP

a month ago

Subject: Private network timeout from app services to Redis after May 20 incident

Hi Railway team,

We’re seeing a persistent private networking issue in our production Railway project after the May 19/20 incident.

Project: cookmark-backend

Environment: production

Region/edge seen: europe-west4-drams3a

Affected services:

API service

Worker service

Redis service/database via private DNS: redis.railway.internal:6379

Current failure:

redis-ping-failed

dial tcp 10.218.190.169:6379: i/o timeout

Example timestamp:

2026-05-20T13:14:55Z

Public API requests return Railway edge 502 because the API process cannot reach Redis during startup:

Application failed to respond

What we’ve verified:

API and worker both use Railway private DNS for Redis: redis.railway.internal:6379.

The private DNS resolves to 10.218.190.169:6379.

TCP connections to that private Redis IP time out.

Redis appears healthy/online from the Railway dashboard.

API, worker, and Redis are in the same region, so this does not look like a cross-region routing issue.

This started after the May 19/20 Railway incident and a container restart.

Redeploying/restarting API and worker did not restore connectivity.

Can you please investigate private network routing/connectivity between the API/worker services and Redis? This looks infrastructure-side rather than an application-level Redis auth/config issue, since the failure is a TCP timeout before Redis auth/protocol.

Solved

1 Replies

Railway
BOT

a month ago

We experienced a major service disruption on May 19/20 that affected private networking. Your logs confirm persistent Redis ping failures. We can see your Redis service's last deployment was back in early March, and platform networking changes can leave database services unreachable even though they appear healthy in the dashboard. The fix is to redeploy the Redis service itself (not just the API/worker). You can trigger a redeploy from the Redis service's deployments tab using the three-dot menu on the latest deployment.


Status changed to Awaiting User Response Railway about 1 month ago


Railway
BOT

a month 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 about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...