Graph-Node Deployment and Database Connectivity Issues

A recent change in pruning behavior unintentionally triggered a spike in postgres_fdw connections, exhausting available database connections. All systems have returned to normal operation and monitoring remains in place.

We are continuing to investigate this issue.

We’re currently investigating recurring issues with graph-node deployments and database connectivity affecting multiple subgraphs. Users may experience failures with symptoms including "database unavailable" and "pruning failed: could not connect to server 'shard_primary'" errors, as well as delays in deploying to the studio.