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
30d window · 2.9 days observed · generated 2026-08-27 17:51:03 UTC
| Metric | NodeReal | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 4 | 5 | 6 | 8 |
| Score | 87.6 | 84.8 | 78.4 | 62.4 |
| Status | Good | Good | Good | Degraded |
| Availability | 99.83% | 99.98% | 99.98% | 84.99% |
| p50 latency | 87.4 ms | 105.1 ms | 106.9 ms | 225.7 ms |
| p95 latency | 100.0 ms | 122.6 ms | 195.7 ms | 4391.3 ms |
| p99 latency | 126.0 ms | 147.5 ms | 243.1 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 97.48% |
| Head lag | 0.35 blocks | 0.42 blocks | 0.48 blocks | 0.91 blocks |
| Rate limited | 0 | 1,193 | 18,014 | 19,250 |
| Unsupported | 0 | 0 | 220 | 0 |
| Samples | 110,215 | 111,528 | 25,983 | 23,460 |
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.8
- Head freshness+0.1
- Availability−0.1
- Correctness+0.0
The parts add to +2.8, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMerkle
+9.2points
- Latency+9.1
- Head freshness+0.2
- Availability−0.1
- Correctness−0.0
The parts add to +9.2, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+25.2points
- Latency+18.1
- Availability+5.9
- Head freshness+0.7
- Correctness+0.5
The parts add to +25.2, exactly — the score is a weighted sum, so it comes apart.