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
7d window · 2.6 days observed · generated 2026-08-27 10:13:51 UTC
| Metric | PublicNode | Blast API | Merkle |
|---|---|---|---|
| Rank | 1 | 5 | 6 |
| Score | 99.4 | 85.2 | 78.6 |
| Status | Excellent | Good | Good |
| Availability | 99.97% | 99.98% | 99.98% |
| p50 latency | 18.4 ms | 104.6 ms | 106.4 ms |
| p95 latency | 33.7 ms | 122.0 ms | 195.9 ms |
| p99 latency | 70.9 ms | 145.5 ms | 243.0 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.42 blocks | 0.48 blocks |
| Rate limited | 0 | 1,133 | 16,018 |
| Unsupported | 0 | 0 | 198 |
| Samples | 100,507 | 99,194 | 23,073 |
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.2points
- Latency+14.3
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +14.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+20.8points
- Latency+20.8
- Head freshness−0.0
- Correctness−0.0
- Availability−0.0
The parts add to +20.8, exactly — the score is a weighted sum, so it comes apart.