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— showing the top 4 by score. Click to change.
Side by side
24h window · 24 hours observed · generated 2026-10-08 17:35:28 UTC
| Metric | NodeReal | BNB Chain | PublicNode | Blast API |
|---|---|---|---|---|
| Rank | 1 | 2 | 3 | 4 |
| Score | 97.4 | 95.7 | 85.8 | 76.5 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 100.00% | 100.00% | 99.99% | 100.00% |
| p50 latency | 18.7 ms | 18.1 ms | 26.5 ms | 105.2 ms |
| p95 latency | 26.7 ms | 25.0 ms | 56.8 ms | 124.5 ms |
| p99 latency | 58.3 ms | 40.9 ms | 177.6 ms | 146.7 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 1.72 blocks | 4.56 blocks | 4.03 blocks | 3.30 blocks |
| Rate limited | 0 | 751 | 0 | 472 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 37,639 | 77,077 | 38,541 | 37,990 |
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
+11.6points
- Latency+9.6
- Head freshness+2.0
- Availability+0.0
- Correctness+0.0
The parts add to +11.6, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsBlast API
+20.9points
- Latency+19.5
- Head freshness+1.4
- Availability+0.0
- Correctness+0.0
The parts add to +20.9, exactly — the score is a weighted sum, so it comes apart.