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-27 04:41:23 UTC
| Metric | NodeReal | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 4 | 5 | 6 | 8 |
| Score | 86.6 | 84.0 | 77.9 | 58.5 |
| Status | Good | Good | Good | Degraded |
| Availability | 100.00% | 99.98% | 100.00% | 75.73% |
| p50 latency | 87.2 ms | 104.7 ms | 107.1 ms | 2024.4 ms |
| p95 latency | 99.9 ms | 121.4 ms | 195.2 ms | 6590.4 ms |
| p99 latency | 124.2 ms | 143.0 ms | 247.0 ms | 9196.2 ms |
| Correctness | 100.00% | 99.99% | 100.00% | 96.63% |
| Head lag | 0.34 blocks | 0.41 blocks | 0.46 blocks | 0.95 blocks |
| Rate limited | 0 | 295 | 6,116 | 6,576 |
| Unsupported | 0 | 0 | 81 | 0 |
| Samples | 37,748 | 38,157 | 8,776 | 7,892 |
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.6points
- Latency+2.5
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +2.6, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMerkle
+8.6points
- Latency+8.5
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +8.6, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+28.1points
- Latency+17.0
- Availability+9.7
- Head freshness+0.7
- Correctness+0.7
The parts add to +28.1, exactly — the score is a weighted sum, so it comes apart.