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
30d window · 2.4 days observed · generated 2026-08-27 06:34:12 UTC
| Metric | PublicNode | Blast API | Merkle |
|---|---|---|---|
| Rank | 1 | 5 | 6 |
| Score | 99.4 | 85.5 | 78.8 |
| Status | Excellent | Good | Good |
| Availability | 99.97% | 99.98% | 99.98% |
| p50 latency | 18.2 ms | 104.4 ms | 106.5 ms |
| p95 latency | 33.5 ms | 122.0 ms | 195.6 ms |
| p99 latency | 69.6 ms | 144.3 ms | 244.4 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.42 blocks | 0.47 blocks |
| Rate limited | 0 | 1,046 | 15,088 |
| Unsupported | 0 | 0 | 183 |
| Samples | 94,538 | 93,261 | 21,689 |
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
+13.9points
- Latency+14.0
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +13.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+20.6points
- Latency+20.6
- Head freshness−0.0
- Correctness−0.0
- Availability−0.0
The parts add to +20.6, exactly — the score is a weighted sum, so it comes apart.