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 Ethereum
Side by side
24h window · 24 hours observed · generated 2026-08-29 02:49:53 UTC
| Metric | NodeReal | Blast API | 1RPC |
|---|---|---|---|
| Rank | 4 | 5 | 8 |
| Score | 86.0 | 83.6 | 60.9 |
| Status | Good | Good | Degraded |
| Availability | 100.00% | 99.98% | 80.50% |
| p50 latency | 87.2 ms | 105.0 ms | 647.0 ms |
| p95 latency | 100.0 ms | 121.2 ms | 4257.4 ms |
| p99 latency | 134.9 ms | 135.6 ms | 7627.6 ms |
| Correctness | 100.00% | 99.99% | 98.30% |
| Head lag | 0.35 blocks | 0.42 blocks | 0.85 blocks |
| Rate limited | 0 | 322 | 6,637 |
| Unsupported | 0 | 0 | 0 |
| Samples | 37,953 | 38,607 | 7,935 |
9 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
+2.4points
- Latency+2.4
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +2.4, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+25.2points
- Latency+16.5
- Availability+7.8
- Head freshness+0.6
- Correctness+0.3
The parts add to +25.2, exactly — the score is a weighted sum, so it comes apart.