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
30d window · 30.0 days observed · generated 2026-10-08 19:51:04 UTC
| Metric | NodeReal | Blast API | 1RPC |
|---|---|---|---|
| Rank | 1 | 4 | 5 |
| Score | 96.8 | 76.8 | 34.8 |
| Status | Excellent | Good | Poor |
| Availability | 99.96% | 99.71% | 37.62% |
| p50 latency | 19.4 ms | 104.5 ms | 833.5 ms |
| p95 latency | 33.2 ms | 124.3 ms | 6722.4 ms |
| p99 latency | 72.3 ms | 391.7 ms | 9354.0 ms |
| Correctness | 100.00% | 99.99% | 98.79% |
| Head lag | 1.70 blocks | 3.31 blocks | 2671.14 blocks |
| Rate limited | 0 | 15,899 | 192,835 |
| Unsupported | 0 | 0 | 6 |
| Samples | 1,140,921 | 1,145,638 | 250,051 |
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.
NodeRealvsBlast API
+20.0points
- Latency+18.4
- Head freshness+1.5
- Availability+0.1
- Correctness+0.0
The parts add to +20.0, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+62.0points
- Latency+28.7
- Availability+24.9
- Head freshness+8.1
- Correctness+0.2
The parts add to +62.0, exactly — the score is a weighted sum, so it comes apart.