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
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 16:22:24 UTC
| Metric | Tenderly | PublicNode | Blast API | MEV Blocker |
|---|---|---|---|---|
| Rank | 1 | 2 | 5 | 7 |
| Score | 99.4 | 95.2 | 78.4 | 69.5 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.98% | 99.99% | 99.99% | 99.88% |
| p50 latency | 20.2 ms | 25.3 ms | 108.8 ms | 124.9 ms |
| p95 latency | 33.4 ms | 49.4 ms | 127.4 ms | 217.2 ms |
| p99 latency | 64.0 ms | 109.7 ms | 153.8 ms | 243.7 ms |
| Correctness | 99.99% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.49 blocks | 0.42 blocks | 0.40 blocks |
| Rate limited | 0 | 0 | 59 | 0 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,721 | 8,787 | 8,693 | 8,690 |
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.
TenderlyvsPublicNode
+4.2points
- Latency+4.2
- Availability−0.0
- Correctness−0.0
- Head freshness+0.0
The parts add to +4.2, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+21.0points
- Latency+21.1
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +21.0, exactly — the score is a weighted sum, so it comes apart.
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.