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 21:59:28 UTC
| Metric | Tenderly | PublicNode | Blast API | MEV Blocker |
|---|---|---|---|---|
| Rank | 1 | 2 | 5 | 7 |
| Score | 99.4 | 94.9 | 78.4 | 69.5 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 100.00% | 100.00% | 99.93% | 99.95% |
| p50 latency | 19.3 ms | 24.6 ms | 108.3 ms | 124.5 ms |
| p95 latency | 32.8 ms | 50.1 ms | 126.3 ms | 216.6 ms |
| p99 latency | 57.9 ms | 111.4 ms | 153.5 ms | 238.6 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 99.98% |
| Head lag | 0.47 blocks | 0.47 blocks | 0.41 blocks | 0.39 blocks |
| Rate limited | 0 | 0 | 65 | 0 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 9,703 | 9,789 | 9,704 | 9,698 |
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.5points
- Latency+4.5
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +4.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+21.1points
- Latency+21.1
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.1, 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.