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
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 20:03:00 UTC
| Metric | Tenderly | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 1 | 7 | 8 |
| Score | 99.4 | 69.5 | 46.6 |
| Status | Excellent | Degraded | Poor |
| Availability | 99.99% | 99.96% | 23.14% |
| p50 latency | 19.7 ms | 125.1 ms | 17.6 ms |
| p95 latency | 33.1 ms | 217.1 ms | 103.4 ms |
| p99 latency | 59.0 ms | 238.4 ms | 277.2 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.39 blocks | no cohort |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 241 |
| Samples | 8,172 | 8,162 | 8,168 |
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.
TenderlyvsMEV Blocker
+29.9points
- Latency+30.0
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +29.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+52.8points
- Availability+29.7
- Latency+15.9
- Head freshness*+9.4
- Correctness−2.2
The parts add to +52.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.