2 months ago
We're experiencing persistent ETIMEDOUT errors on outbound connections from our n8n deployment in EU West (Amsterdam) region, even after the "Issues with networking on a subset of hosts" incident was marked as Resolved at 1:04 PM (March 15).
Symptoms:
- ETIMEDOUT to our external PostgreSQL (148.251.47.30:5432, Hetzner Germany)
- ETIMEDOUT to Telegram Bot API (149.154.166.110:443)
- Pattern: ~1 in 6 requests times out, rest succeed normally
- Two completely different destinations, same error — points to outbound networking issue on Railway side
What we've tried:
- Restart — no effect
- Full redeploy — no effect
- Verified our server is healthy (CPU idle 98%, PG has 6/100 connections, no errors in logs, ping from other sources works fine)
The issue started around 06:00-07:00 UTC today, well before the incident was officially posted at 12:27 PM. It persists after the incident was marked resolved.
Project region: EU West (Metal / Amsterdam)
Is anyone else still experiencing outbound networking issues after the resolved incident?
3 Replies
2 months ago
Still with outbound network issues, partially solved.
2 months ago
Concerned that the incident is marked Resolved while multiple users are still affected. Is the team still actively working on this?
2 months ago
This incident is resolved, can you share any logs/evidence if you're still running into this?
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 • about 2 months ago