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-27 13:33:12 UTC
| Metric | PublicNode | Blast API | Merkle |
|---|---|---|---|
| Rank | 2 | 5 | 6 |
| Score | 96.5 | 78.6 | 70.2 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 100.00% | 100.00% |
| p50 latency | 23.6 ms | 107.7 ms | 108.7 ms |
| p95 latency | 45.6 ms | 124.9 ms | 200.3 ms |
| p99 latency | 125.1 ms | 153.6 ms | 230.9 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.41 blocks | 0.49 blocks |
| Rate limited | 0 | 78 | 1,409 |
| Unsupported | 0 | 0 | 17 |
| Samples | 9,080 | 8,998 | 2,104 |
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 PublicNode, the highest scorer of those selected.
PublicNodevsBlast API
+17.8points
- Latency+17.9
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +17.8, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+26.3points
- Latency+26.3
- Availability−0.0
- Head freshness−0.0
- Correctness−0.0
The parts add to +26.3, exactly — the score is a weighted sum, so it comes apart.