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 18:13:49 UTC
| Metric | NodeReal | BNB Chain | PublicNode | Blast API |
|---|---|---|---|---|
| Rank | 1 | 2 | 3 | 4 |
| Score | 97.2 | 95.6 | 86.1 | 76.3 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 100.00% | 99.99% | 99.98% | 99.99% |
| p50 latency | 18.7 ms | 18.3 ms | 30.2 ms | 110.9 ms |
| p95 latency | 27.3 ms | 25.2 ms | 56.7 ms | 129.6 ms |
| p99 latency | 71.3 ms | 43.3 ms | 172.4 ms | 158.1 ms |
| Correctness | 100.00% | 99.99% | 99.98% | 99.99% |
| Head lag | 1.84 blocks | 4.63 blocks | 4.01 blocks | 3.35 blocks |
| Rate limited | 0 | 163 | 0 | 108 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,356 | 17,074 | 8,531 | 8,382 |
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.6points
- Head freshness+2.3
- Latency−0.8
- Availability+0.0
- Correctness+0.0
The parts add to +1.6, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsPublicNode
+11.1points
- Latency+9.1
- Head freshness+1.9
- Availability+0.0
- Correctness+0.0
The parts add to +11.1, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsBlast API
+20.8points
- Latency+19.5
- Head freshness+1.4
- Availability+0.0
- Correctness+0.0
The parts add to +20.8, exactly — the score is a weighted sum, so it comes apart.