Why Edge RPC

​

Fastest responses from 8+ edge regions

• Multi-region elastic cloud infrastructure serves requests from the closest location
• Tip-of-the-chain CDN stores and serves recent blockchain data to you faster
• Hedging mechanisms send parallel requests to multiple nodes for faster response times

​

Maximum resiliency and failover

• Automatic failover keeps requests flowing during provider outages
• Internal scoring mechanisms prioritize the historically most reliable nodes
• Multiplexing auto-merges identical requests to reduce redundant RPC calls

​

Automated data quality checks

• Cross-validate responses from multiple RPC nodes for accuracy
• Integrity mechanisms track block heights across all providers
• Enforce consensus checks to prevent stale/incorrect/partial data
• No more partial or missing eth_getLogs results in your indexer

​

Optimized for indexing

• Auto-split large eth_getLogs requests: breaks down large block ranges to avoid provider limits
• Archive node routing: requests for historical data automatically routed to archive nodes
• Block range enforcement: integrity checks verify complete data without gaps

​

Boosted for frontend

• Sub-50ms latency: edge locations serve requests from the nearest region
• Request deduplication: multiple users requesting the same data share a single upstream call
• Graceful degradation: automatic retries and failover keep your dApp online
• Real-time data: tip-of-chain caching serves latest blocks with minimal delay

​

Simple pricing

• $5 per million requests: straightforward, predictable costs
• All methods priced equally: no surprise charges for eth_getLogs or trace methods
• Volume discounts: tiered pricing for usage over 500M requests/month

---