ApiVault's server functions now run in Frankfurt alongside the database, which reduces query round-trip latency.

Three changes also stop a request from failing because the database host closed its connection:

Connection lifetimes: connections are replaced after 5 minutes, idle ones close after a minute, and the pool resets after a pause of more than 4 minutes.
Read retries: a read retries once on a fresh connection if the database closed an idle socket. Writes never retry automatically.
Status checks: the status page's database health check now uses its own connection instead of resetting the shared request pool.

Current service health is on the status page.