ApiVault's server functions now run in Frankfurt alongside the database to reduce query round-trip latency.

Three changes also address requests that fail after a connection has been idle:

• Connection lifetimes: connections are replaced after 5 minutes, idle connections close after 60 seconds, and the pool resets after a pause longer than 4 minutes.
• Read retries: a read retries once on a fresh connection if the database closed an idle socket. Writes are not retried automatically, avoiding duplicate write attempts.
• Status checks: database health checks use a dedicated connection instead of resetting the shared request pool.

Check real-time health on the status page, or review error resolutions in troubleshooting.