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
6h window · 6.0 hours observed · generated 2026-10-08 20:37:10 UTC
| Metric | NodeReal | BNB Chain | PublicNode | Blast API |
|---|---|---|---|---|
| Rank | 1 | 2 | 3 | 4 |
| Score | 97.3 | 95.6 | 86.9 | 76.3 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.75% | 99.72% | 99.96% | 99.96% |
| p50 latency | 18.8 ms | 18.2 ms | 29.8 ms | 110.2 ms |
| p95 latency | 27.2 ms | 25.4 ms | 54.2 ms | 132.2 ms |
| p99 latency | 62.0 ms | 42.3 ms | 217.5 ms | 166.4 ms |
| Correctness | 100.00% | 99.99% | 99.98% | 99.99% |
| Head lag | 1.74 blocks | 4.55 blocks | 3.95 blocks | 3.36 blocks |
| Rate limited | 0 | 175 | 0 | 129 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,974 | 18,310 | 9,186 | 8,944 |
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.7points
- Head freshness+2.4
- Latency−0.7
- Availability+0.0
- Correctness+0.0
The parts add to +1.7, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsPublicNode
+10.4points
- Latency+8.6
- Head freshness+1.9
- Availability−0.1
- Correctness+0.0
The parts add to +10.4, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsBlast API
+21.0points
- Latency+19.6
- Head freshness+1.5
- Availability−0.1
- Correctness+0.0
The parts add to +21.0, exactly — the score is a weighted sum, so it comes apart.