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:55:27 UTC
| Metric | NodeReal | PublicNode | 1RPC |
|---|---|---|---|
| Rank | 1 | 3 | 5 |
| Score | 97.2 | 86.0 | 27.3 |
| Status | Excellent | Good | Poor |
| Availability | 100.00% | 99.98% | 7.96% |
| p50 latency | 18.8 ms | 30.3 ms | 1438.6 ms |
| p95 latency | 27.2 ms | 57.0 ms | 7334.3 ms |
| p99 latency | 69.9 ms | 198.3 ms | 8983.2 ms |
| Correctness | 100.00% | 99.98% | 100.00% |
| Head lag | 1.83 blocks | 4.00 blocks | 7.01 blocks |
| Rate limited | 0 | 0 | 1,045 |
| Unsupported | 0 | 0 | 0 |
| Samples | 9,464 | 9,669 | 4,627 |
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.1points
- Latency+9.2
- Head freshness+1.9
- Availability+0.0
- Correctness+0.0
The parts add to +11.1, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+69.8points
- Availability+36.8
- Latency+29.2
- Head freshness+3.8
- Correctness+0.0
The parts add to +69.8, exactly — the score is a weighted sum, so it comes apart.