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
30d window · 2.7 days observed · generated 2026-08-27 13:58:38 UTC
| Metric | Tenderly | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 2 | 5 | 9 |
| Score | 96.0 | 85.0 | 54.8 |
| Status | Excellent | Good | Degraded |
| Availability | 99.96% | 99.98% | 23.11% |
| p50 latency | 19.8 ms | 104.8 ms | 15.1 ms |
| p95 latency | 54.1 ms | 122.2 ms | 87.5 ms |
| p99 latency | 778.0 ms | 146.2 ms | 250.7 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.50 blocks | 0.42 blocks | no cohort |
| Rate limited | 0 | 1,154 | 96 |
| Unsupported | 0 | 0 | 3,110 |
| Samples | 105,826 | 105,258 | 105,645 |
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
+11.0points
- Latency+11.1
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +11.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+41.2points
- Availability+29.7
- Head freshness*+9.4
- Latency+4.3
- Correctness−2.2
The parts add to +41.2, 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.