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 22:53:39 UTC
| Metric | PublicNode | dRPC | Blast API | MEV Blocker |
|---|---|---|---|---|
| Rank | 2 | 3 | 5 | 7 |
| Score | 95.5 | 88.7 | 78.3 | 69.5 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 100.00% | 99.99% | 99.92% | 99.94% |
| p50 latency | 23.7 ms | 34.1 ms | 107.4 ms | 123.9 ms |
| p95 latency | 46.7 ms | 69.5 ms | 125.1 ms | 216.4 ms |
| p99 latency | 103.3 ms | 190.9 ms | 152.7 ms | 238.5 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 99.98% |
| Head lag | 0.47 blocks | 0.35 blocks | 0.41 blocks | 0.39 blocks |
| Rate limited | 0 | 19 | 44 | 0 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 9,629 | 9,405 | 9,539 | 9,535 |
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 PublicNode, the highest scorer of those selected.
PublicNodevsdRPC
+6.8points
- Latency+7.0
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +6.8, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+17.2points
- Latency+17.3
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +17.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+26.0points
- Latency+26.1
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +26.0, exactly — the score is a weighted sum, so it comes apart.