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
Side by side
24h window · 24 hours observed · generated 2026-08-27 04:42:43 UTC
| Metric | PublicNode | Tenderly | MEV Blocker |
|---|---|---|---|
| Rank | 1 | 2 | 7 |
| Score | 99.4 | 99.2 | 77.0 |
| Status | Excellent | Excellent | Good |
| Availability | 99.98% | 99.98% | 99.91% |
| p50 latency | 18.3 ms | 19.6 ms | 119.6 ms |
| p95 latency | 35.2 ms | 36.2 ms | 210.4 ms |
| p99 latency | 73.8 ms | 173.0 ms | 234.1 ms |
| Correctness | 100.00% | 99.99% | 99.99% |
| Head lag | 0.49 blocks | 0.50 blocks | 0.39 blocks |
| Rate limited | 0 | 0 | 2 |
| Unsupported | 0 | 0 | 0 |
| Samples | 38,714 | 38,393 | 38,340 |
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.2points
- Latency+0.2
- Head freshness+0.0
- Correctness+0.0
- Availability−0.0
The parts add to +0.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+22.4points
- Latency+22.5
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +22.4, exactly — the score is a weighted sum, so it comes apart.