11 days ago
Worker service experienced multiple crashes between 03:29-03:34 UTC on August 10, 2026 due to connection timeouts with Redis and PostgreSQL.
ERRORS:
"[Redis client] connect ETIMEDOUT"
"Could not establish database connection within the configured timeout of 20,000 ms"
"Exiting process due to Redis connection error"
Period: 03:29-03:34 UTC (August 10, 2026)
Deployment ID: b69822bd-f231-4f42-ab67-6d5aeb980b0b
Region: us-west2
Were there any infrastructure issues, maintenance, or network degradations that affected Redis and PostgreSQL connectivity during this period?
Thanks.
7 Replies
11 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 11 days ago
11 days ago
checked status.railway.com, no incident logged for that window, august shows 100% uptime across the board. but the page only reports widespread impact, so a small localized blip wouldnt show there anyway.
also "us-west2" isnt one of railways region names (they use us-west/us-east/eu-west/southeast-asia), worth double checking thats really what your service shows.
worth checking if this lines up with a deploy/restart on your redis or postgres service around that time, that'd point to your own setup instead
0x5b62656e5d
Are there any errors in your Redis logs?
11 days ago
why do you keep flagging my comments i dont get it youre here to help which im allo trying to do the same
wats ur gain in doing this???
0x5b62656e5d
Are there any errors in your Redis logs?
11 days ago
Hi There.
No.
Just this message that`s been repeated over time.
1:M 05 Aug 2026 14:37:10.400 * Asynchronous AOF fsync is taking too long (disk is busy?). Writing the AOF buffer without waiting for fsync to complete, this may slow down Redis.
sales
Hi There. No. Just this message that`s been repeated over time. 1:M 05 Aug 2026 14:37:10.400 * Asynchronous AOF fsync is taking too long (disk is busy?). Writing the AOF buffer without waiting for fsync to complete, this may slow down Redis.
11 days ago
send a picture or screenshot
manuproject
checked status.railway.com, no incident logged for that window, august shows 100% uptime across the board. but the page only reports widespread impact, so a small localized blip wouldnt show there anyway. also "us-west2" isnt one of railways region names (they use us-west/us-east/eu-west/southeast-asia), worth double checking thats really what your service shows. worth checking if this lines up with a deploy/restart on your redis or postgres service around that time, that'd point to your own setup instead
11 days ago
Hello.
US WEST( California USA)