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 08:51:37 UTC
| Metric | PublicNode | Blast API | Merkle |
|---|---|---|---|
| Rank | 1 | 5 | 6 |
| Score | 99.4 | 78.0 | 70.0 |
| Status | Excellent | Good | Degraded |
| Availability | 99.99% | 99.99% | 100.00% |
| p50 latency | 18.5 ms | 104.4 ms | 105.0 ms |
| p95 latency | 30.7 ms | 119.3 ms | 193.7 ms |
| p99 latency | 64.2 ms | 146.3 ms | 251.0 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.42 blocks | 0.61 blocks |
| Rate limited | 0 | 110 | 1,492 |
| Unsupported | 0 | 0 | 17 |
| Samples | 9,562 | 9,481 | 2,149 |
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
+21.4points
- Latency+21.5
- Head freshness−0.1
- Correctness+0.0
- Availability+0.0
The parts add to +21.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+29.4points
- Latency+29.3
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +29.4, exactly — the score is a weighted sum, so it comes apart.