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 22:53:46 UTC
| Metric | PublicNode | Blast API | Merkle |
|---|---|---|---|
| Rank | 2 | 5 | 6 |
| Score | 97.7 | 83.9 | 78.0 |
| Status | Excellent | Good | Good |
| Availability | 99.99% | 99.97% | 100.00% |
| p50 latency | 21.6 ms | 106.2 ms | 107.2 ms |
| p95 latency | 41.4 ms | 123.1 ms | 192.3 ms |
| p99 latency | 100.4 ms | 150.5 ms | 231.9 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.41 blocks | 0.53 blocks |
| Rate limited | 0 | 320 | 6,145 |
| Unsupported | 0 | 0 | 73 |
| Samples | 39,047 | 38,635 | 8,963 |
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
+19.7points
- Latency+19.7
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +19.7, exactly — the score is a weighted sum, so it comes apart.