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 19:27:47 UTC
| Metric | NodeReal | PublicNode | Blast API |
|---|---|---|---|
| Rank | 1 | 3 | 4 |
| Score | 97.3 | 86.2 | 76.3 |
| Status | Excellent | Good | Good |
| Availability | 99.75% | 99.97% | 99.98% |
| p50 latency | 18.8 ms | 30.5 ms | 111.0 ms |
| p95 latency | 26.7 ms | 56.9 ms | 131.6 ms |
| p99 latency | 68.9 ms | 216.0 ms | 166.7 ms |
| Correctness | 100.00% | 99.98% | 99.99% |
| Head lag | 1.77 blocks | 3.93 blocks | 3.35 blocks |
| Rate limited | 0 | 0 | 112 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,726 | 8,921 | 8,770 |
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.1
- Correctness+0.0
The parts add to +11.2, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsBlast API
+21.1points
- Latency+19.7
- Head freshness+1.4
- Availability−0.1
- Correctness+0.0
The parts add to +21.1, exactly — the score is a weighted sum, so it comes apart.