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
24h window · 24 hours observed · generated 2026-08-27 03:56:38 UTC
| Metric | Tenderly | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 2 | 7 | 9 |
| Score | 99.1 | 77.0 | 52.3 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 99.90% | 23.12% |
| p50 latency | 19.7 ms | 119.5 ms | 16.1 ms |
| p95 latency | 36.4 ms | 210.6 ms | 93.1 ms |
| p99 latency | 189.8 ms | 234.2 ms | 246.6 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.39 blocks | no cohort |
| Rate limited | 0 | 2 | 45 |
| Unsupported | 0 | 0 | 1,144 |
| Samples | 38,787 | 38,732 | 38,731 |
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
+22.1points
- Latency+22.2
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +22.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+46.8points
- Availability+29.7
- Latency+9.9
- Head freshness*+9.4
- Correctness−2.2
The parts add to +46.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.