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.5 days observed · generated 2026-08-27 09:12:05 UTC
| Metric | PublicNode | Blast API | Merkle |
|---|---|---|---|
| Rank | 1 | 5 | 6 |
| Score | 99.4 | 85.3 | 78.7 |
| Status | Excellent | Good | Good |
| Availability | 99.97% | 99.98% | 99.98% |
| p50 latency | 18.3 ms | 104.5 ms | 106.4 ms |
| p95 latency | 33.5 ms | 122.0 ms | 196.1 ms |
| p99 latency | 70.1 ms | 145.0 ms | 243.1 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.42 blocks | 0.48 blocks |
| Rate limited | 0 | 1,097 | 15,770 |
| Unsupported | 0 | 0 | 193 |
| Samples | 98,827 | 97,521 | 22,684 |
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.1points
- Latency+14.2
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +14.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+20.7points
- Latency+20.8
- Head freshness−0.0
- Correctness−0.0
- Availability−0.0
The parts add to +20.7, exactly — the score is a weighted sum, so it comes apart.