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:24:56 UTC
| Metric | NodeReal | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 4 | 5 | 6 | 8 |
| Score | 86.4 | 83.7 | 78.0 | 59.4 |
| Status | Good | Good | Good | Degraded |
| Availability | 99.97% | 99.96% | 100.00% | 77.43% |
| p50 latency | 87.1 ms | 105.6 ms | 106.7 ms | 1291.3 ms |
| p95 latency | 99.0 ms | 122.6 ms | 189.8 ms | 7517.0 ms |
| p99 latency | 117.0 ms | 150.3 ms | 278.7 ms | 9776.0 ms |
| Correctness | 99.97% | 100.00% | 100.00% | 97.48% |
| Head lag | 0.35 blocks | 0.41 blocks | 0.52 blocks | 0.91 blocks |
| Rate limited | 0 | 19 | 1,426 | 1,415 |
| Unsupported | 0 | 0 | 16 | 0 |
| Samples | 8,615 | 8,762 | 2,106 | 1,971 |
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.
NodeRealvsMerkle
+8.4points
- Latency+8.2
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +8.4, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+27.0points
- Latency+16.9
- Availability+9.0
- Head freshness+0.6
- Correctness+0.5
The parts add to +27.0, exactly — the score is a weighted sum, so it comes apart.