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
24h window · 24 hours observed · generated 2026-08-27 09:10:37 UTC
| Metric | PublicNode | Blast API | Merkle |
|---|---|---|---|
| Rank | 2 | 5 | 6 |
| Score | 99.3 | 83.8 | 77.8 |
| Status | Excellent | Good | Good |
| Availability | 99.98% | 99.99% | 100.00% |
| p50 latency | 18.5 ms | 105.2 ms | 107.2 ms |
| p95 latency | 35.5 ms | 122.4 ms | 195.0 ms |
| p99 latency | 74.7 ms | 146.1 ms | 239.8 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.48 blocks | 0.42 blocks | 0.51 blocks |
| Rate limited | 0 | 347 | 5,992 |
| Unsupported | 0 | 0 | 74 |
| Samples | 37,847 | 37,314 | 8,573 |
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
+15.5points
- Latency+15.6
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +15.5, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.5points
- Latency+21.5
- Head freshness+0.0
- Availability−0.0
- Correctness+0.0
The parts add to +21.5, exactly — the score is a weighted sum, so it comes apart.