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— showing the top 4 by score. Click to change.
Side by side
6h window · 6.0 hours observed · generated 2026-10-08 11:20:40 UTC
| Metric | NodeReal | BNB Chain | PublicNode | Blast API |
|---|---|---|---|---|
| Rank | 1 | 2 | 3 | 4 |
| Score | 96.3 | 95.7 | 79.6 | 66.6 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 100.00% | 100.00% | 99.99% | 100.00% |
| p50 latency | 19.0 ms | 18.1 ms | 27.0 ms | 104.8 ms |
| p95 latency | 28.2 ms | 25.4 ms | 59.3 ms | 127.9 ms |
| p99 latency | 58.9 ms | 40.7 ms | 161.3 ms | 150.6 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 1.74 blocks | 4.44 blocks | 4.04 blocks | 3.28 blocks |
| Rate limited | 0 | 171 | 0 | 101 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,526 | 17,432 | 8,734 | 8,666 |
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
+0.6points
- Head freshness+2.3
- Latency−1.7
- Availability+0.0
- Correctness+0.0
The parts add to +0.6, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsPublicNode
+16.7points
- Latency+14.7
- Head freshness+2.0
- Availability+0.0
- Correctness+0.0
The parts add to +16.7, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsBlast API
+29.7points
- Latency+28.3
- Head freshness+1.4
- Availability+0.0
- Correctness+0.0
The parts add to +29.7, exactly — the score is a weighted sum, so it comes apart.