How Global Node GEN 2.0 upgrade made BNB Smart Chain RPC up to 40x faster

Summary: GEN 2.0 is a major update to Chainstack Global Nodes, as significant for RPC users as a hard fork is for the chain itself. On BNB Smart Chain mainnet it cuts the median time to first byte (TTFB) from 293 ms to 71 ms: 75.8% lower, or 4.1x faster. All 8 cities where the same probe measured both routes got faster, from 1.1x in Dubai to 41.0x in Singapore, and the BNB Smart Chain testnet improved in all 16 cities.
BNB Smart Chain apps such as DEX front ends, trading bots and wallets call the node constantly, and every call starts with the wait for the first byte of the response. The GEN 2.0 routing change shortens that wait. This post shows by how much, measured from 16 cities, for mainnet and the testnet.
What changed for BNB Smart Chain requests
GEN 2.0 removes the Cloudflare Workers edge layer that used to sit in front of every BNB Smart Chain node. Cloudflare DNS now resolves your hostname to the nearest healthy region, and the request goes directly to that region’s gateway and on to the node. Mainnet and testnet both run this way.

One update, every chain. GEN 2.0 is live across Global Nodes. The announcement covers how it works and where else it applies: Chainstack GEN 2.0 is live: faster Global Nodes.
How we measured BNB Smart Chain
We sent an RPC request to a Chainstack BNB Smart Chain endpoint from Globalping probes in 16 cities and recorded the time to first byte (TTFB). Each probe hit the pre-GEN 2.0 route (through Cloudflare) and the GEN 2.0 direct route in the same minute on Oct 29, 2026.
The headline covers the 8 cities where the same probe measured both routes. The other 8 (Cape Town, Melbourne, San José, Istanbul, Lisbon, London, New York and Amsterdam) used different probes for the two routes, so they appear in the full table with an asterisk and stay out of the headline.
BNB Smart Chain mainnet results: median TTFB fell from 293 ms to 71 ms
| Metric (8 cities) | Before GEN 2.0 | GEN 2.0 |
|---|---|---|
| Median TTFB | 293 ms | 71 ms |
| Mean TTFB | 442 ms | 96 ms |
| Reduction at the median | – | 75.8% |
| Faster at the median | – | 4.1x |
| Cities that improved | – | 8 of 8 |
| Range of improvement | – | 1.1x to 41.0x |

Full per-city results (BNB Smart Chain mainnet)
| City | Country | Before GEN 2.0 (ms) | GEN 2.0 (ms) | Saved (ms) | Faster (x) |
|---|---|---|---|---|---|
| Cape Town* | South Africa | 1345 | 191 | 1154 | 7.0 |
| São Paulo | Brazil | 834 | 122 | 712 | 6.8 |
| Buenos Aires | Argentina | 756 | 157 | 599 | 4.8 |
| New Delhi | India | 746 | 71 | 675 | 10.5 |
| Melbourne* | Australia | 686 | 175 | 511 | 3.9 |
| San José* | Costa Rica | 450 | 66 | 384 | 6.8 |
| Istanbul* | Turkey | 350 | 52 | 298 | 6.7 |
| Lisbon* | Portugal | 338 | 31 | 307 | 10.9 |
| Los Angeles | United States | 315 | 71 | 244 | 4.4 |
| Tokyo | Japan | 271 | 70 | 201 | 3.9 |
| Dubai | United Arab Emirates | 261 | 238 | 23 | 1.1 |
| Dallas | United States | 231 | 39 | 192 | 5.9 |
| Singapore | Singapore | 123 | 3 | 120 | 41.0 |
| New York* | United States | 114 | 7 | 107 | 16.3 |
| London* | United Kingdom | 102 | 3 | 99 | 34.0 |
| Amsterdam* | Netherlands | 65 | 15 | 50 | 4.3 |
Rows marked with an asterisk (*) used different probes for the two routes and are not in the headline numbers. Across all 16 cities the median goes from 326.5 ms to 68 ms.
Where BNB Smart Chain gains the most
- In milliseconds: São Paulo saves 712 ms (834 ms to 122 ms), New Delhi 675 ms (746 ms to 71 ms) and Buenos Aires 599 ms (756 ms to 157 ms).
- As a ratio: Singapore drops from 123 ms to 3 ms (41.0x), New Delhi is 10.5x faster and Dallas 5.9x.
- The smallest gain: Dubai improves only 1.1x, from 261 ms to 238 ms.
BNB Smart Chain testnet
The testnet got the same test from the same 16 cities, with the same probe on both routes.
| Network | Median before GEN 2.0 | Median with GEN 2.0 | Cities that improved |
|---|---|---|---|
| Testnet | 253.5 ms | 95 ms | 16 of 16 |
The testnet median is about 2.7x lower, less than mainnet’s 4.1x, but every city improved, from 1.4x in Dubai to 33.0x in London.
How does BNB Smart Chain compare today?
Compare ranks providers on p95 latency and success rate, measured from Germany, the US and Singapore. As of Nov 18, 2026 (last 7 days), Chainstack ranks #1 for BNB Smart Chain, but narrowly:
- Score 0.074 (lower is better), availability 99.99%.
- p50 / p95 / p99: 35 ms / 72 ms / 109 ms.
- p95 by probe region: Germany 87 ms, US 98 ms, Singapore 32 ms.

The next provider sits at 0.075, so this is a close race, and Germany is the one region where Chainstack does not lead (87 ms p95 against 53 ms for the best provider there). The live view is BNB Smart Chain on Compare. For a fixed window (Nov 5 to Nov 12, 2026, score 0.070), see the BNB Chain RPC provider benchmark: latency and uptime (November 2026).
How to read these numbers (and what they don’t prove)
- Eight cities, one run. Half of the 16 probes could not be compared between routes, so the headline rests on 8 cities from a single run on Oct 29, 2026. Read the median, not a single row.
- TTFB, not total call time. The clock stops at the first byte, so it leaves out the download of large responses (a wide
eth_getLogsrange, for example) and the time the node spends computing them. - A close race on BNB Smart Chain. In the Chainstack vs Alchemy RPC benchmark, BNB Smart Chain JSON-RPC is nearly a tie (50.8% to 49.2% of regional p95 comparisons), and Alchemy leads WebSocket newHeads.
- Chainstack against Chainstack. The A/B above compares two Chainstack routes with each other. For other providers, see Compare.
What this means for BNB Smart Chain builders
BNB Smart Chain apps call the node all the time: a DEX front end refreshing quotes, a trading bot reading pool state before it swaps, a wallet loading balances. Saving hundreds of milliseconds per call from far regions (São Paulo 712 ms, New Delhi 675 ms) adds up in each of them.
In short: GEN 2.0 is a major update, as significant for BNB Smart Chain RPC users as a hard fork is for the chain. Same endpoint, same API, and a median first byte of 71 ms instead of 293 ms.
No BNB Smart Chain endpoint yet? Deploy a Global Node in seconds on the free Developer plan and see BNB Smart Chain on Chainstack.
FAQ
No. The hostname and the API are unchanged, so existing code keeps working. GEN 2.0 covers BNB Smart Chain mainnet and testnet.
On BNB Smart Chain mainnet the median time to first byte fell from 293 ms to 71 ms, about 4.1x, in a same-minute test from 8 cities on Oct 29, 2026. The gain ranged from 1.1x to 41.0x.
Dubai went from 261 ms to 238 ms, the smallest gain of the 8 same-probe cities. The gain depends on the network path between the probe and the nearest region, and this path improved less than the others. The other 7 cities improved 3.9x or more.
On Compare, Chainstack ranks #1 on score for the last 7 days (0.074 as of Nov 18, 2026), but the next provider is at 0.075 and Germany is a region where Chainstack does not lead. Rankings change, so check the live page.
Germany, the US and Singapore. Compare queries the first paid plan of each provider every 1 to 3 minutes, and the score combines p95 latency per method with the success rate. Lower is better.
No. It is the median of one A/B test in 8 cities on Oct 29, 2026, and your result will differ with where your servers and users are.
Related reading
- Chainstack GEN 2.0 is live: faster Global Nodes
- BNB Smart Chain on Compare
- BNB Chain RPC provider benchmark: latency and uptime (November 2026)
- BNB Chain RPC provider scores for production DApps (November 2026)
- BNB Smart Chain RPC nodes and APIs
- Chainstack vs Alchemy RPC benchmark: 7 networks, November 2026