Introducing a reimagined Standard mode designed to deliver unseen performance & reliability with its all-new globally distributed and geo-load-balanced architecture helping businesses & developers give their customers the best user experience ever.
Build limitlessly with an ever-expanding portfolio of blockchains
It’s a promise we take very seriously.
Averaged across all users over the last 30 days
Never be short on resources when you need more. We don’t throttle your throughput irrespective of traffic volumes. Need to handle a massive influx? Go for it.
All our plans include class-leading monthly request volumes with no limits on the number or type of requests your DApp can make every day. Daily request limits? Who needs that?
The fastest transaction propagation on the planet. Warp Transactions help you supercharge your trading by tunneling your transactions through the ultra high-speed bloXroute network and making them available instantly for validators to include in the next block.
Especially when it gets tough.
Meticulously redesigned from the ground up, the intelligent, globally load-balanced architecture delivers greater than 99.99% uptime and worry-free, uninterrupted service.
Geo-load-balanced and distributed worldwide, Global Elastic Nodes automatically route requests to the nearest geo-located servers for the fastest service seamlessly.
Guarantee consistently great performance & experience for all your users with the lowest latency and fastest response times. Even when they travel to the other side of the globe.
The adaptive and persistent fault-tolerance system monitors network-health in realtime and automatically reroutes your traffic to the most performant nodes in under 1 second.
The all new Standard mode helps you deploy nodes in under 1 second, powered by our completely reimagined globally distributed load-balancer service. And all this without having you click on anything other than “Next”.
From Tokyo to Oregon, pin-point and deploy your node in a location nearest to the region your dApp needs to service.
Build on the Chainstack Cloud with its best-in-class security & uptime, or choose a managed cloud service from AWS, GCP, Azure, or Virtuozzo.
No method-specific fees. To make your monthly infra spending predictable, every API call to your node is billed at a flat rate in Request Units, or RU irrespective of the type of request or the computational resources it requires.
A new standard in our Elastic Nodes infrastructure offering, Global Elastic Nodes are powered by a globally distributed load-balancing architecture that provides the lowest latency and fastest response times by routing traffic to the nearest, most performant nodes across multiple locations worldwide.
When you deploy new Elastic Nodes from within the Chainstack Console, the default node configuration is set to Standard. This deploys a Global Elastic Node without you having to go through Advanced parameters. All it takes is for you to click “Next”.
Global Elastic Nodes take less than 1 second to be deployed and become ready for use instantly thereafter.
Global Elastic Nodes are being launched for Ethereum, BNB Smart Chain, and Polygon in the first phase of rollout. This will be followed by support for 15+ new protocols being launched in the coming weeks, eventually becoming available across our entire line-up of protocol offerings.
At the time of launch, only Full node requests will be available on Global Elastic Nodes. Support for Archive nodes is scheduled to be added in the coming weeks, shortly thereafter.
No. Usage of Global Elastic Nodes does not require any additional fees and is billed at the same flat rate of 1 RU (Request Unit) for Full node requests, and 2 RUs per Archive node request.
Our global load-balancing architecture swiftly re-routes operations in less than 1 second if a node is down or stressed enough to cause a lag of more than 40 blocks.
Once a node recovers, HTTP connections will return to it instantaneously. WebSocket connections will remain on the switched node for the duration of the ongoing session and will auto-connect to the original node, once available, in the next session.