Providers
Compare RPC providers on measured data
The top 4 on the chosen chain are compared by default. Pick your own — up to 4 — and the selection moves into the URL, so a comparison can be sent to someone else and they will see exactly what you saw.
Providers on BSC
Side by side
7d window · 7.0 days observed · generated 2026-10-08 19:52:04 UTC
| Metric | NodeReal | BNB Chain | PublicNode | Blast API |
|---|---|---|---|---|
| Rank | 1 | 2 | 3 | 4 |
| Score | 97.5 | 95.7 | 88.8 | 76.8 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.99% | 99.99% | 99.96% | 99.99% |
| p50 latency | 18.8 ms | 17.9 ms | 22.9 ms | 103.3 ms |
| p95 latency | 27.9 ms | 26.4 ms | 45.8 ms | 119.5 ms |
| p99 latency | 63.6 ms | 43.7 ms | 143.9 ms | 143.7 ms |
| Correctness | 100.00% | 100.00% | 99.98% | 100.00% |
| Head lag | 1.71 blocks | 4.52 blocks | 4.11 blocks | 3.25 blocks |
| Rate limited | 0 | 5,242 | 0 | 3,592 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 261,376 | 535,381 | 267,670 | 263,379 |
5 providers scored against each other.
Where the gap comes from
Two scores side by side say one is higher. This says why: the score is a weighted sum, so it comes apart, and each component’s share of the difference adds back to the difference exactly. Compared against NodeReal, the highest scorer of those selected.
NodeRealvsBNB Chain
+1.8points
- Head freshness+2.4
- Latency−0.6
- Availability+0.0
- Correctness+0.0
The parts add to +1.8, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsPublicNode
+8.7points
- Latency+6.6
- Head freshness+2.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.7, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsBlast API
+20.7points
- Latency+19.3
- Head freshness+1.4
- Availability−0.0
- Correctness+0.0
The parts add to +20.7, exactly — the score is a weighted sum, so it comes apart.