BNB Chain RPC Provider Benchmark: Latency & Uptime (September 2026)

By Chainstack Labs Research Team · Research Note No. 047 · September 2026 edition · Published Sep 28, 2026 · Last updated Sep 28, 2026 · Node Infrastructure

Data source: live Grafana compare dashboards, refreshed every 3 minutes, 7-day rolling window across DE, US, and SG.

---

Abstract

BNB Chain carries some of the highest raw transaction throughput of any chain in this report series, which puts unusual pressure on an RPC provider’s ability to hold latency steady under load rather than just post a good median. This report ranks four providers — Chainstack, Quicknode, Alchemy, and dRPC — on BNB Chain RPC latency and uptime, using a composite score that weights response time against success rate independently in three regions (Frankfurt, US, Singapore) and then averages the result. Chainstack ranks first with a score of 0.091 and the lowest global P95 (93ms) in the set, though notably not the lowest P50 or P99 — Alchemy’s P50 is faster (29ms vs. 35ms) and its P99 is markedly lower (214ms vs. 390ms), a split result explored in Section 5. The standout finding this round is dRPC’s regional pattern: unlike Ethereum and Hyperliquid, where the weakest region in this series has consistently been Asia-Pacific, dRPC on BNB Chain is weakest in Frankfurt (559ms P95) and the US (689ms P95), and comparatively strong in Singapore (145ms) — the reverse geography of every other outlier in this series to date. For how RPC method choice compounds regional latency, see our companion report, RPC Method Latency Across Chains.

Keywords: BNB Chain RPC provider, BNB Chain RPC latency, RPC benchmark, regional latency, availability, composite scoring, tail latency, provider comparison

---

Contents

1. Introduction
2. Methodology and scoring
3. Providers and regions
4. Results
5. Regional variance and outliers
6. Interpretation notes and known confounders
7. Conclusion
8. Appendix A: measurement parameters

---

1. Introduction

BNB Chain’s block times and transaction volume are tuned for throughput, which means an RPC provider serving it has to hold up under a request pattern that is denser and more bursty than a comparable window on Ethereum or a newer chain like Arc. A provider that looks fine on a quiet chain can behave differently once request volume rises, which is part of why this report treats the full P50/P95/P99 spread — not just the headline score — as the more informative read for BNB Chain specifically. This report ranks four RPC providers — Chainstack, Quicknode, Alchemy, and dRPC — on that basis, publishing the regional detail behind the composite ranking rather than only the final number.

This edition also surfaces a pattern not seen elsewhere in this series so far: a provider whose weakest regions are Europe and North America rather than Asia-Pacific, which is worth reading in full before assuming the regional weak points identified in earlier editions (Ethereum, Hyperliquid) generalize across chains or providers.

2. Methodology and scoring

Each provider is evaluated on speed (response time) and reliability (success rate) independently in each monitored region, then combined as:

Score = ResponseTime / SuccessRate³, averaged across regions. Lower is better.

Cubing the success-rate term makes reliability the dominant factor once availability drops meaningfully below 100% — a provider that is fast but flaky is penalized far more than the raw percentage-point gap in its availability figure would suggest. This round also illustrates a subtler point about the formula: Quicknode posts the only 100.00% availability in the set but does not post the lowest score, because the formula still weights response time directly — perfect reliability narrows the gap to a faster-but-less-reliable competitor, it does not override it. Per-method p95 latencies are combined with equal weights to produce the response-time term, and regional scores are averaged arithmetically rather than weighted by traffic share, so a slow region cannot be diluted by two fast ones. Scores are read directly from the underlying Grafana compare dashboards, which update every 3 minutes, rather than recomputed downstream from a static export.

3. Providers and regions

Four providers offering public BNB Chain RPC endpoints were included: Chainstack, Quicknode, Alchemy, and dRPC. Each was measured concurrently from three regions — Frankfurt (DE), a US test node, and Singapore (SG) — against the same BNB Chain RPC methods, over a rolling 7-day window refreshed every 3 minutes. All figures reflect each provider’s standard shared endpoint, not a dedicated tier. Chainstack’s BNB Chain node deployment options include dedicated tiers that were out of scope for this round.

4. Results

Table 1. Composite score, availability, and global percentile latency by provider, 7-day window. Chainstack posts the lowest composite score (0.091) and the lowest global P95 (93ms), but not the lowest P50 or P99 — Alchemy is faster at the median and markedly tighter at the tail. dRPC’s score is more than four times Chainstack’s, driven by a P99 that crosses the two-second mark.

Provider	Score	Availability	P50	P95	P99
Chainstack	0.091	99.97%	35ms	93ms	390ms
Quicknode	0.122	100.00%	52ms	121ms	268ms
Alchemy	0.124	99.99%	29ms	122ms	214ms
dRPC	0.419	99.87%	38ms	464ms	2,220ms

Table 2. P95 latency by region, milliseconds. dRPC’s weakest regions are DE and US, not SG — the opposite geography from every other provider outlier reported in this series so far.

Provider	DE	US	SG
Chainstack	89ms	148ms	41ms
Quicknode	147ms	107ms	109ms
Alchemy	88ms	143ms	135ms
dRPC	559ms	689ms	145ms

5. Regional variance and outliers

Table 1’s median and tail columns disagree on ranking in a way not seen in earlier editions of this series: Alchemy’s P50 (29ms) is the fastest in the set, beating Chainstack’s (35ms), and its P99 (214ms) is also the tightest, beating Chainstack’s (390ms) by a wide margin — yet Chainstack still posts the lower composite score, because the score is built on P95, not P50 or P99, and Chainstack’s P95 (93ms) is lower than Alchemy’s (122ms). This is a useful reminder that a “best P50” or “best P99” claim and a “best composite score” claim are answering different questions, and a provider can legitimately win on more than one of them without winning on all three.

The more striking pattern is dRPC’s regional shape. Every prior regional outlier in this series — Alchemy on Arc, dRPC’s own US result on Ethereum, the DE-to-Tokyo gap on Hyperliquid — has had Asia-Pacific as the weak region. On BNB Chain, dRPC inverts that: Singapore (145ms) is its best region, while Frankfurt (559ms) and the US (689ms) are both severely degraded, with the US figure alone accounting for most of its 2,220ms global P99. This is not consistent with a simple “this provider is weak in APAC” story and more likely reflects a footprint or routing issue specific to dRPC’s EU/US infrastructure for BNB Chain rather than a general regional pattern.

Quicknode’s regional spread is the flattest of the four (107–147ms across all three regions), which is consistent with its 100.00% availability but does not fully compensate for a P95 above both Chainstack’s and Alchemy’s in every region.

6. Interpretation notes and known confounders

Shared-endpoint tier only. All figures reflect each provider’s standard shared RPC endpoint. Dedicated infrastructure in the affected regions would be the direct mitigation for dRPC’s DE and US results, and this comparison does not test whether that gap persists on a paid dedicated tier.

High throughput can widen the median-to-tail gap. BNB Chain’s transaction volume means a provider’s P99 is a more meaningful signal of how it behaves under real load than on a quieter chain — this is part of why Chainstack’s P95 lead does not carry through to P99 against Alchemy, and readers optimizing for tail-latency-sensitive workloads (liquidations, MEV-adjacent bots) should weight Table 1’s P99 column, not only the composite score.

Method mix is not disclosed. The P95 figures combine multiple RPC methods with equal weights. As our RPC Method Latency Across Chains benchmark shows, method choice can move latency by an order of magnitude on its own; a workload concentrated in one heavy method may see different relative rankings than this blended figure suggests.

Single measurement window. Figures reflect one rolling 7-day window. Whether dRPC’s DE/US pattern is a persistent regional issue or a transient incident inside this window is not something a single snapshot can distinguish; a follow-up edition of this report will show whether it recurs or whether the more typical APAC-weak pattern reasserts itself.

7. Conclusion

On BNB Chain, the composite ranking and the per-percentile ranking tell slightly different stories: Chainstack wins the score that matters most for consistency (P95 across regions), Alchemy wins on raw median and tail speed, and Quicknode wins on availability without winning on speed. dRPC is the clear outlier of the round, but in a geography that breaks the pattern this series has otherwise established — its weak point here is Europe and North America, not Asia-Pacific. Teams choosing an RPC provider for BNB Chain should decide which percentile matters for their workload (P50 for interactive UX, P95 for the composite ranking used here, P99 for tail-sensitive systems) before picking a winner from this table, since no single provider leads on all three this round.

Appendix A: measurement parameters

Parameter	Value
Chain	BNB Chain
Providers	Chainstack, Quicknode, Alchemy, dRPC (shared endpoint tier)
Regions	DE (Frankfurt), US, SG (Singapore)
Measurement window	Rolling 7 days, refreshed every 3 minutes
Score formula	ResponseTime / SuccessRate³, averaged across regions
Latency basis	Per-method P95, equal-weighted
Source	Live Grafana compare dashboards