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 14:15:39 UTC
| Metric | Tenderly | PublicNode | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 1 | 2 | 5 | 6 |
| Score | 99.4 | 95.7 | 78.6 | 70.4 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.94% | 99.98% | 99.99% | 100.00% |
| p50 latency | 20.2 ms | 24.5 ms | 108.1 ms | 108.1 ms |
| p95 latency | 34.3 ms | 48.2 ms | 125.8 ms | 197.2 ms |
| p99 latency | 77.7 ms | 124.1 ms | 153.3 ms | 231.3 ms |
| Correctness | 100.00% | 99.99% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.49 blocks | 0.41 blocks | 0.47 blocks |
| Rate limited | 0 | 0 | 58 | 1,346 |
| Unsupported | 0 | 0 | 0 | 16 |
| Samples | 8,538 | 8,595 | 8,519 | 1,995 |
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
+3.7points
- Latency+3.7
- Availability−0.0
- Head freshness+0.0
- Correctness+0.0
The parts add to +3.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+20.8points
- Latency+20.9
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +20.8, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+29.0points
- Latency+29.0
- Availability−0.0
- Head freshness−0.0
- Correctness+0.0
The parts add to +29.0, exactly — the score is a weighted sum, so it comes apart.