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
- PublicNode
- Tenderly
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
30d window · 2.7 days observed · generated 2026-08-27 12:30:04 UTC
| Metric | PublicNode | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 5 | 6 | 8 |
| Score | 99.4 | 85.1 | 78.5 | 62.5 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.97% | 99.98% | 99.98% | 85.16% |
| p50 latency | 18.6 ms | 104.7 ms | 106.5 ms | 225.7 ms |
| p95 latency | 34.0 ms | 122.1 ms | 196.4 ms | 4391.3 ms |
| p99 latency | 72.2 ms | 146.0 ms | 243.4 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 97.48% |
| Head lag | 0.49 blocks | 0.42 blocks | 0.48 blocks | 0.91 blocks |
| Rate limited | 0 | 1,154 | 16,628 | 17,754 |
| Unsupported | 0 | 0 | 201 | 0 |
| Samples | 104,226 | 102,877 | 23,946 | 21,746 |
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.3points
- Latency+14.4
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +14.3, 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.
PublicNodevs1RPC
+36.9points
- Latency+30.0
- Availability+5.9
- Correctness+0.5
- Head freshness+0.5
The parts add to +36.9, exactly — the score is a weighted sum, so it comes apart.