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:29:17 UTC
| Metric | NodeReal | BNB Chain | PublicNode | Blast API |
|---|---|---|---|---|
| Rank | 1 | 2 | 3 | 4 |
| Score | 97.3 | 95.5 | 86.2 | 76.3 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.75% | 99.72% | 99.97% | 99.98% |
| p50 latency | 18.8 ms | 18.3 ms | 30.5 ms | 111.0 ms |
| p95 latency | 26.8 ms | 25.2 ms | 56.9 ms | 131.7 ms |
| p99 latency | 69.0 ms | 43.3 ms | 217.9 ms | 166.4 ms |
| Correctness | 100.00% | 99.99% | 99.98% | 99.99% |
| Head lag | 1.77 blocks | 4.57 blocks | 3.93 blocks | 3.34 blocks |
| Rate limited | 0 | 172 | 0 | 116 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,768 | 17,893 | 8,962 | 8,807 |
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.8points
- Head freshness+2.4
- Latency−0.6
- Availability+0.0
- Correctness+0.0
The parts add to +1.8, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsPublicNode
+11.1points
- Latency+9.3
- Head freshness+1.9
- Availability−0.1
- Correctness+0.0
The parts add to +11.1, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsBlast API
+21.0points
- Latency+19.7
- Head freshness+1.4
- Availability−0.1
- Correctness+0.0
The parts add to +21.0, exactly — the score is a weighted sum, so it comes apart.