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
6h window · 6.0 hours observed · generated 2026-08-27 21:22:26 UTC
| Metric | Tenderly | PublicNode | MEV Blocker |
|---|---|---|---|
| Rank | 1 | 2 | 7 |
| Score | 99.4 | 94.4 | 69.5 |
| Status | Excellent | Excellent | Degraded |
| Availability | 100.00% | 100.00% | 99.94% |
| p50 latency | 19.4 ms | 25.1 ms | 124.8 ms |
| p95 latency | 32.8 ms | 52.5 ms | 216.7 ms |
| p99 latency | 57.7 ms | 113.7 ms | 237.0 ms |
| Correctness | 100.00% | 100.00% | 99.98% |
| Head lag | 0.47 blocks | 0.47 blocks | 0.40 blocks |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,708 | 8,779 | 8,703 |
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
+5.1points
- Latency+5.1
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +5.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMEV 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.