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
- PublicNode
- Tenderly
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 08:05:16 UTC
| Metric | PublicNode | Tenderly | Blast API | MEV Blocker |
|---|---|---|---|---|
| Rank | 1 | 2 | 5 | 7 |
| Score | 99.4 | 98.6 | 77.9 | 69.5 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.99% | 99.99% | 99.99% | 99.91% |
| p50 latency | 18.0 ms | 18.4 ms | 104.1 ms | 119.0 ms |
| p95 latency | 29.3 ms | 31.9 ms | 118.6 ms | 207.5 ms |
| p99 latency | 56.7 ms | 71.4 ms | 145.2 ms | 225.8 ms |
| Correctness | 100.00% | 100.00% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.48 blocks | 0.42 blocks | 0.42 blocks |
| Rate limited | 0 | 0 | 90 | 0 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,303 | 8,234 | 8,228 | 8,225 |
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.
PublicNodevsTenderly
+0.8points
- Latency+0.8
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +0.8, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+21.5points
- Latency+21.6
- Head freshness−0.1
- Correctness+0.0
- Availability+0.0
The parts add to +21.5, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV 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.