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
7d window · 3.4 days observed · generated 2026-08-28 05:33:38 UTC
| Metric | NodeReal | Merkle | 1RPC |
|---|---|---|---|
| Rank | 4 | 6 | 8 |
| Score | 87.1 | 78.2 | 61.8 |
| Status | Good | Good | Degraded |
| Availability | 99.83% | 99.99% | 83.57% |
| p50 latency | 87.4 ms | 106.7 ms | 265.3 ms |
| p95 latency | 99.8 ms | 195.0 ms | 4975.4 ms |
| p99 latency | 124.6 ms | 244.5 ms | 8455.9 ms |
| Correctness | 99.99% | 100.00% | 97.38% |
| Head lag | 0.34 blocks | 0.49 blocks | 0.91 blocks |
| Rate limited | 0 | 21,052 | 22,479 |
| Unsupported | 0 | 256 | 0 |
| Samples | 128,850 | 30,448 | 27,513 |
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.
NodeRealvsMerkle
+8.9points
- Latency+8.8
- Head freshness+0.2
- Availability−0.1
- Correctness−0.0
The parts add to +8.9, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+25.3points
- Latency+17.6
- Availability+6.5
- Head freshness+0.7
- Correctness+0.5
The parts add to +25.3, exactly — the score is a weighted sum, so it comes apart.