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.6 days observed · generated 2026-08-27 11:17:35 UTC
| Metric | Tenderly | Blast API | MEV Blocker | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 5 | 7 | 8 |
| Score | 95.5 | 85.2 | 77.8 | 62.5 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.96% | 99.98% | 99.89% | 85.27% |
| p50 latency | 19.8 ms | 104.7 ms | 118.7 ms | 225.7 ms |
| p95 latency | 57.0 ms | 122.1 ms | 209.4 ms | 4391.3 ms |
| p99 latency | 802.2 ms | 145.7 ms | 232.7 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 97.48% |
| Head lag | 0.50 blocks | 0.42 blocks | 0.40 blocks | 0.91 blocks |
| Rate limited | 0 | 1,134 | 3 | 17,420 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 101,466 | 100,917 | 101,290 | 21,361 |
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 Tenderly, the highest scorer of those selected.
TenderlyvsBlast API
+10.4points
- Latency+10.5
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +10.4, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMEV Blocker
+17.8points
- Latency+17.9
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +17.8, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+33.0points
- Latency+26.2
- Availability+5.9
- Correctness+0.5
- Head freshness+0.5
The parts add to +33.0, exactly — the score is a weighted sum, so it comes apart.