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.8 days observed · generated 2026-08-27 16:54:33 UTC
| Metric | PublicNode | Blast API | Merkle |
|---|---|---|---|
| Rank | 1 | 5 | 6 |
| Score | 99.4 | 84.9 | 78.5 |
| Status | Excellent | Good | Good |
| Availability | 99.98% | 99.98% | 99.98% |
| p50 latency | 19.1 ms | 105.0 ms | 106.7 ms |
| p95 latency | 35.1 ms | 122.5 ms | 195.7 ms |
| p99 latency | 74.9 ms | 147.3 ms | 243.4 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.42 blocks | 0.48 blocks |
| Rate limited | 0 | 1,193 | 17,776 |
| Unsupported | 0 | 0 | 219 |
| Samples | 111,426 | 110,003 | 25,631 |
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
+14.5points
- Latency+14.6
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +14.5, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+20.9points
- Latency+20.9
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +20.9, exactly — the score is a weighted sum, so it comes apart.