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:27:44 UTC
| Metric | NodeReal | PublicNode | Blast API |
|---|---|---|---|
| Rank | 1 | 3 | 4 |
| Score | 97.2 | 86.0 | 76.3 |
| Status | Excellent | Good | Good |
| Availability | 100.00% | 99.98% | 99.99% |
| p50 latency | 18.7 ms | 30.2 ms | 110.8 ms |
| p95 latency | 27.2 ms | 57.2 ms | 129.5 ms |
| p99 latency | 71.9 ms | 203.1 ms | 157.8 ms |
| Correctness | 100.00% | 99.98% | 99.99% |
| Head lag | 1.83 blocks | 4.00 blocks | 3.36 blocks |
| Rate limited | 0 | 0 | 112 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,726 | 8,912 | 8,762 |
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.2points
- Latency+9.3
- Head freshness+1.9
- Availability+0.0
- Correctness+0.0
The parts add to +11.2, 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.