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
24h window · 24 hours observed · generated 2026-10-08 19:50:50 UTC
| Metric | NodeReal | PublicNode | Blast API |
|---|---|---|---|
| Rank | 1 | 3 | 4 |
| Score | 97.3 | 86.0 | 76.4 |
| Status | Excellent | Good | Good |
| Availability | 99.94% | 99.99% | 99.99% |
| p50 latency | 18.7 ms | 26.8 ms | 105.3 ms |
| p95 latency | 26.9 ms | 56.3 ms | 125.6 ms |
| p99 latency | 58.1 ms | 180.6 ms | 150.5 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 1.72 blocks | 4.03 blocks | 3.30 blocks |
| Rate limited | 0 | 0 | 486 |
| Unsupported | 0 | 0 | 0 |
| Samples | 38,048 | 38,974 | 38,355 |
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.
NodeRealvsPublicNode
+11.3points
- Latency+9.3
- Head freshness+2.0
- Availability−0.0
- Correctness+0.0
The parts add to +11.3, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsBlast API
+20.9points
- Latency+19.5
- Head freshness+1.5
- Availability−0.0
- Correctness+0.0
The parts add to +20.9, exactly — the score is a weighted sum, so it comes apart.