Hi Railway Support Team,

I am reaching out regarding a critical performance degradation of my Postgres instance in the EU West (Amsterdam) region. Despite having a 50GB Volume and optimized configuration, the database is experiencing severe I/O bottlenecks that are paralyzing my production environment (n8n).

Technical Evidence of Infrastructure Issues:

1. Extreme 'Extend' Wait Events: Our pg_stat_activity monitoring shows that simple INSERT operations on the execution_metadata table are frequently stuck in an 'extend' wait state for over 4 minutes (260+ seconds). This indicates a massive delay in the storage layer when the database attempts to allocate new blocks.
2. Abnormal Checkpoint Durations: Logs indicate that a relatively small checkpoint (writing only ~48MB of buffers) took 263.4 seconds to complete. This I/O throughput is far below expected performance levels for an SSD-backed volume.
3. High WALWrite Latency: We observed COMMIT operations and WALWrite events taking upwards of 1 second, even after setting synchronous_commit = off.

Environment Details:

• Service: Postgres
• Region: EU West (Amsterdam)
• Volume Size: 50GB (range-volume)
• Current Config: We have already tuned shared_buffers (8GB), max_connections (300), and adjusted checkpoint intervals, but the underlying I/O latency persists.

Impact: My n8n Primary and Worker instances are constantly failing with "Database connection timed out" because the database becomes unresponsive during these I/O spikes.

Could you please investigate the health of the underlying storage node or the physical host where this instance is located? It appears to be a "noisy neighbor" issue or a degradation of the EBS/Volume performance in this specific zone.