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
- Cloudflare
- 1RPC
Side by side
24h window · 24 hours observed · generated 2026-08-27 00:09:54 UTC
| Metric | PublicNode | Blast API | 1RPC |
|---|---|---|---|
| Rank | 1 | 5 | 9 |
| Score | 99.4 | 84.1 | 41.6 |
| Status | Excellent | Good | Poor |
| Availability | 99.98% | 99.98% | 34.55% |
| p50 latency | 18.4 ms | 104.4 ms | 5059.2 ms |
| p95 latency | 35.0 ms | 121.1 ms | 9539.0 ms |
| p99 latency | 73.6 ms | 140.7 ms | 9539.0 ms |
| Correctness | 100.00% | 99.99% | 95.00% |
| Head lag | 0.49 blocks | 0.42 blocks | 1.00 blocks |
| Rate limited | 0 | 400 | 6,420 |
| Unsupported | 0 | 0 | 0 |
| Samples | 37,819 | 37,312 | 7,400 |
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.3points
- Latency+15.4
- Head freshness−0.1
- Correctness+0.0
- Availability−0.0
The parts add to +15.3, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+57.8points
- Latency+30.0
- Availability+26.2
- Correctness+1.0
- Head freshness+0.6
The parts add to +57.8, exactly — the score is a weighted sum, so it comes apart.