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-27 16:52:13 UTC
| Metric | PublicNode | dRPC | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 3 | 5 | 8 |
| Score | 98.3 | 90.9 | 83.9 | 57.8 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.97% | 99.93% | 99.99% | 73.97% |
| p50 latency | 20.1 ms | 33.8 ms | 106.0 ms | 2024.4 ms |
| p95 latency | 39.4 ms | 71.1 ms | 122.4 ms | 6590.4 ms |
| p99 latency | 94.6 ms | 173.4 ms | 149.5 ms | 9196.2 ms |
| Correctness | 100.00% | 99.99% | 100.00% | 96.63% |
| Head lag | 0.49 blocks | 0.37 blocks | 0.42 blocks | 0.95 blocks |
| Rate limited | 0 | 144 | 370 | 6,634 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 38,995 | 38,036 | 38,440 | 7,961 |
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
+7.4points
- Latency+7.6
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +7.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+14.4points
- Latency+14.5
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +14.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+40.5points
- Latency+28.9
- Availability+10.4
- Correctness+0.7
- Head freshness+0.5
The parts add to +40.5, exactly — the score is a weighted sum, so it comes apart.