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
- Tenderly
- PublicNode
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
24h window · 24 hours observed · generated 2026-08-28 07:45:20 UTC
| Metric | PublicNode | dRPC | NodeReal | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 3 | 4 | 8 |
| Score | 97.7 | 91.4 | 86.5 | 59.0 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.98% | 99.97% | 99.90% | 76.74% |
| p50 latency | 22.4 ms | 33.2 ms | 87.5 ms | 1326.0 ms |
| p95 latency | 41.1 ms | 68.5 ms | 100.2 ms | 7406.7 ms |
| p99 latency | 95.2 ms | 188.7 ms | 136.1 ms | 9776.0 ms |
| Correctness | 99.98% | 99.99% | 99.99% | 96.96% |
| Head lag | 0.48 blocks | 0.36 blocks | 0.34 blocks | 0.94 blocks |
| Rate limited | 0 | 86 | 0 | 6,600 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 38,834 | 37,878 | 37,823 | 7,913 |
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.
PublicNodevsdRPC
+6.4points
- Latency+6.5
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +6.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsNodeReal
+11.2points
- Latency+11.3
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +11.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+38.7points
- Latency+28.3
- Availability+9.3
- Correctness+0.6
- Head freshness+0.5
The parts add to +38.7, exactly — the score is a weighted sum, so it comes apart.