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 16:22:04 UTC
| Metric | Tenderly | PublicNode | MEV Blocker |
|---|---|---|---|
| Rank | 1 | 2 | 7 |
| Score | 99.4 | 98.4 | 76.8 |
| Status | Excellent | Excellent | Good |
| Availability | 99.98% | 99.97% | 99.93% |
| p50 latency | 19.3 ms | 20.0 ms | 121.1 ms |
| p95 latency | 34.1 ms | 39.1 ms | 212.3 ms |
| p99 latency | 75.4 ms | 93.3 ms | 235.9 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.49 blocks | 0.40 blocks |
| Rate limited | 0 | 0 | 3 |
| Unsupported | 0 | 0 | 0 |
| Samples | 37,816 | 38,178 | 37,792 |
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
+1.0points
- Latency+1.0
- Availability+0.0
- Head freshness+0.0
- Correctness−0.0
The parts add to +1.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMEV Blocker
+22.6points
- Latency+22.7
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +22.6, exactly — the score is a weighted sum, so it comes apart.