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
1h window · 60 minutes observed · generated 2026-10-08 17:47:45 UTC
| Metric | NodeReal | PublicNode | Blast API |
|---|---|---|---|
| Rank | 1 | 3 | 4 |
| Score | 97.9 | 81.0 | 67.1 |
| Status | Excellent | Good | Degraded |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 17.9 ms | 30.4 ms | 111.2 ms |
| p95 latency | 25.1 ms | 55.1 ms | 129.8 ms |
| p99 latency | 54.0 ms | 195.9 ms | 154.5 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 1.69 blocks | 3.75 blocks | 2.76 blocks |
| Rate limited | 0 | 0 | 19 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,598 | 1,613 | 1,613 |
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
+17.0points
- Latency+15.1
- Head freshness+1.8
- Availability+0.0
- Correctness+0.0
The parts add to +17.0, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsBlast API
+30.9points
- Latency+29.8
- Head freshness+1.0
- Availability+0.0
- Correctness+0.0
The parts add to +30.9, exactly — the score is a weighted sum, so it comes apart.