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
6h window · 6.0 hours observed · generated 2026-08-28 00:03:18 UTC
| Metric | NodeReal | Blast API | 1RPC |
|---|---|---|---|
| Rank | 4 | 5 | 9 |
| Score | 86.4 | 83.6 | 40.0 |
| Status | Good | Good | Poor |
| Availability | 99.96% | 99.96% | 28.00% |
| p50 latency | 87.1 ms | 105.8 ms | 4375.0 ms |
| p95 latency | 99.0 ms | 122.9 ms | 8458.8 ms |
| p99 latency | 117.4 ms | 150.6 ms | 8458.8 ms |
| Correctness | 99.96% | 100.00% | 100.00% |
| Head lag | 0.35 blocks | 0.42 blocks | 1.00 blocks |
| Rate limited | 0 | 19 | 1,399 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,042 | 8,181 | 1,627 |
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.8points
- Latency+2.7
- Head freshness+0.1
- Correctness−0.0
- Availability+0.0
The parts add to +2.8, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+46.4points
- Availability+28.8
- Latency+16.9
- Head freshness+0.8
- Correctness−0.0
The parts add to +46.4, exactly — the score is a weighted sum, so it comes apart.