The service itself has been performing well once properly configured, and I was especially impressed by the technical support experience. I initially ran into a difficult issue where full transaction subscriptions were delivering far below the expected throughput. After quite a bit of testing, Luiz Moraes from Chainstack Support helped identify the actual cause: the HTTP/2 flow-control window on the grpc-js client connection. After applying the recommended 16 MiB flow-control window, our full transaction stream improved to roughly 450–500 messages per second and started following the Solana chain head normally. What I appreciated most was that the support team did not just give generic troubleshooting suggestions. Luiz responded quickly, reviewed the technical details carefully, reproduced the behavior on their side, and eventually provided a specific configuration change that solved the problem.

Our RPC traffic is business-critical, so reliability matters more to us than having a long list of features. Since moving to Chainstack, the endpoints have been stable, performance has been consistent, and we haven’t had to spend much time dealing with infrastructure issues.

We started using Chainstack because we needed reliable Base infrastructure with Flashblocks support, and the setup was much easier than expected. We didn’t have to spend much time figuring out the infrastructure side; the endpoint was ready quickly, performance has been consistent, and the team was helpful whenever we had questions about the integration. It was also good to see them supporting newer Base features early, instead of only offering the standard RPC setup.