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
- 1RPC
- Cloudflare
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 03:15:19 UTC
| Metric | PublicNode | Blast API | MEV Blocker | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 5 | 7 | 8 |
| Score | 99.1 | 84.2 | 77.2 | 58.7 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.99% | 99.99% | 99.95% | 76.33% |
| p50 latency | 17.2 ms | 103.4 ms | 117.8 ms | 2024.4 ms |
| p95 latency | 34.2 ms | 117.3 ms | 209.1 ms | 6590.4 ms |
| p99 latency | 84.8 ms | 145.0 ms | 228.9 ms | 9196.2 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 96.63% |
| Head lag | 0.48 blocks | 0.41 blocks | 0.39 blocks | 0.95 blocks |
| Rate limited | 0 | 71 | 2 | 1,438 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,579 | 8,457 | 8,494 | 2,008 |
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.
PublicNodevsBlast API
+14.9points
- Latency+15.0
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +14.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+21.9points
- Latency+22.0
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+40.4points
- Latency+29.7
- Availability+9.5
- Correctness+0.7
- Head freshness+0.5
The parts add to +40.4, exactly — the score is a weighted sum, so it comes apart.