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 21:43:17 UTC
| Metric | Tenderly | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 1 | 8 | 9 |
| Score | 99.4 | 57.3 | 53.6 |
| Status | Excellent | Degraded | Degraded |
| Availability | 99.98% | 72.66% | 23.15% |
| p50 latency | 19.3 ms | 2024.4 ms | 15.2 ms |
| p95 latency | 33.2 ms | 6590.4 ms | 86.4 ms |
| p99 latency | 74.0 ms | 9196.2 ms | 250.3 ms |
| Correctness | 100.00% | 96.63% | 100.00% |
| Head lag | 0.48 blocks | 0.95 blocks | no cohort |
| Rate limited | 0 | 6,593 | 25 |
| Unsupported | 0 | 0 | 1,130 |
| Samples | 38,402 | 7,924 | 38,447 |
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.
Tenderlyvs1RPC
+42.1points
- Latency+30.0
- Availability+10.9
- Correctness+0.7
- Head freshness+0.5
The parts add to +42.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+45.8points
- Availability+29.7
- Head freshness*+9.4
- Latency+8.9
- Correctness−2.2
The parts add to +45.8, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.