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 14:56:35 UTC
| Metric | PublicNode | Blast API | MEV Blocker |
|---|---|---|---|
| Rank | 2 | 5 | 7 |
| Score | 95.5 | 78.4 | 69.5 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 99.99% | 99.91% |
| p50 latency | 24.7 ms | 108.3 ms | 123.9 ms |
| p95 latency | 48.9 ms | 126.2 ms | 214.9 ms |
| p99 latency | 118.6 ms | 153.5 ms | 237.4 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.50 blocks | 0.41 blocks | 0.39 blocks |
| Rate limited | 0 | 71 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 9,714 | 9,628 | 9,603 |
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
+17.1points
- Latency+17.2
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +17.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+26.0points
- Latency+26.1
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +26.0, exactly — the score is a weighted sum, so it comes apart.