# RouteMesh > RouteMesh is a blockchain RPC routing and aggregation service. Website: https://routeme.sh | Documentation: https://routeme.sh/docs ## Summary - **RPC Aggregator**: Routes blockchain requests across 15+ RPC providers (Alchemy, QuickNode, Ankr, Chainstack, etc.) through a single endpoint - **Chain Coverage**: Supports 1000+ blockchain networks - more than any single provider - **Automatic Failover**: If a node fails, requests automatically retry with the next best node from a different provider - **Routing Strategies**: Economy (cost-optimized) or Performance (latency-optimized), set per API key - **Pricing**: Per-request pricing with no compute units, no minimum commitments, no hidden fees - **Reliability**: Multiple load balancers (Cloudflare + AWS), data quality checks, and 15+ provider fallback inventory ## What is RouteMesh? RouteMesh is an RPC aggregation layer that routes blockchain requests across multiple RPC providers. Instead of connecting directly to a single provider, applications connect to RouteMesh, which then intelligently routes each request to the optimal node from its network of 15+ providers and 1000+ supported chains. RouteMesh provides access to all RPC providers through a single endpoint, with per-request pricing, no hidden fees or minimum commitments, and automatic retries and failovers built-in. ## Aggregation vs Single Provider When using a single RPC provider directly: - You are limited to that provider's node inventory and geographic distribution - If their nodes fail or lag, your requests fail - You must manage your own fallback logic to other providers - Each provider has different pricing models (compute units, rate limits, etc.) - Chain support is limited to what that provider offers - You need separate subscriptions and billing for each provider When using an aggregator like RouteMesh: - Access to the combined node inventory of 15+ providers globally - Automatic failover to other providers when nodes fail - Geo-routing selects the closest/fastest node from all available providers - Unified per-request pricing across all chains and methods - 1000+ chains supported through a single integration - Single bill, single endpoint, single API key ## How RPC Aggregation Works When you send a request to RouteMesh: 1. The request hits RouteMesh's load balancer (geo-distributed across Cloudflare and AWS) 2. RouteMesh selects the optimal node based on your routing strategy (economy or performance) 3. If the request fails, RouteMesh automatically retries with the next best node from a different provider 4. This continues until the request succeeds or all available nodes are exhausted 5. You receive a uniform response format regardless of which underlying provider served the request This aggregation model provides access to the combined node inventory of all integrated providers through a single endpoint. ## RouteMesh Capabilities **Scale** - 15+ integrated RPC providers (Alchemy, QuickNode, Ankr, Chainstack, and others) - 1000+ supported blockchain networks - Thousands of nodes across all providers globally **Routing Strategies** Strategies are set at the API key level, allowing different strategies for different use cases: - **Economy**: Optimizes for lowest cost while maintaining reliability. Uses cheapest available provider and falls back until request succeeds. Best for indexing, backend services, and batch processing. - **Performance**: Optimizes for lowest latency regardless of cost. Best for user-facing applications and real-time dApps. Both strategies include automatic failovers and retries. **Reliability Features** - Automatic failover across providers when nodes fail - Auto-retries with the next best node until request succeeds - Multiple load balancers (Cloudflare primary at `lb.routeme.sh`, AWS backup at `lb2.routeme.sh`) - Traffic migrates to healthy pools in under 15 seconds - Health checks every 15 seconds on all infrastructure - Bare metal instances with Google Cloud backup infrastructure - Average incident response time of 10 minutes - Requests only fail if all providers and nodes are exhausted **Data Quality System** RouteMesh monitors data quality across all nodes to ensure accurate blockchain data: - Replay checks: Every nth request is executed asynchronously against multiple nodes and results are compared for consistency - Lag checks: Every nth request on a chain includes a block number check to detect how far from the chain tip a node is - Staging arena: Nodes that fail checks are quarantined and must prove themselves before serving real traffic again - Checks run hourly minimum per chain even during low traffic periods **Pricing Model** - Per-request pricing (no compute units) - No minimum commitments or hidden fees - Prices determined algorithmically and updated monthly - Pricing varies by chain, method, and routing strategy - Popular chains with more node supply have lower pricing - Committed use discounts available for high-volume usage **Problems RouteMesh Addresses** - Managing multiple provider subscriptions - Inconsistent pricing across providers - Unreliable responses and failed requests - Manual fallback management - Arbitrary pricing structures with overage costs - No single provider supporting all chains - Varying latencies across geographic locations - Multiple bills from different providers ## Single Endpoint for All Chains RouteMesh uses a consistent URL pattern: ``` POST https://rpc.routeme.sh/rpc/{chain_id}/{api_key} ``` The same endpoint structure works for any of the 1000+ supported chains. ## Network Support Levels - **Full Support**: Multiple providers available with scaling capacity - **Lite Support**: Single provider available (can be upgraded upon request) Adding support for a new chain typically takes less than one day. ## Published Metrics RouteMesh publishes real-time performance data publicly: - P50 and P95 latency metrics per route (chain + method combination) - Metrics available for both economy and performance strategies - Geographic latency data by region - Pricing transparency at https://routeme.sh/pricing ## Global Routing RouteMesh maintains geo-location-based routing tables optimized for each region. Nodes that are optimal from Europe differ from those optimal for US East (for latency). RouteMesh offers: - Global load balancing with automatic failover for production reliability - Direct regional endpoints for handling burst traffic - Latency by region viewable at https://routeme.sh/latencies ## Documentation Comprehensive documentation is available at https://routeme.sh/docs covering: - Getting started and API integration - How RouteMesh routing works - Network support and chain coverage - Pricing model details - Routing strategy selection - Data quality mechanisms - Redundancy architecture --- ## Website Structure **Main Pages** - `/` - Homepage - `/chains` - All supported blockchain networks - `/pricing` - Current pricing by chain and method - `/providers` - Integrated RPC providers - `/compare` - Provider comparison - `/latencies` - Latency by region and regional latencies - `/blog` - Blog posts and updates - `/case-studies` - Customer case studies **Dynamic Pages** - `/chain/evm/{chainSlug}` - Individual chain pages (e.g., `/chain/evm/1-ethereum`) - `/routes/evm/{chainSlug}/{method}` - Route detail pages (e.g., `/routes/evm/1-ethereum/eth_call`) - `/providers/{providerName}` - Provider detail pages (e.g., `/providers/alchemy`) - `/blog/{uid}` - Individual blog posts - `/case-studies/{uid}` - Individual case studies **Authentication** - `/auth/login` - Sign in - `/auth/signup` - Create account **Dashboard (requires authentication)** - `/app/consumer/*` - Consumer dashboard - `/app/provider/*` - Provider dashboard - `/settings/*` - Account settings --- ## Dynamic Content The following sections are automatically generated and updated daily: ## Chains Total chains tracked: 100 - Ethereum Mainnet (Chain ID: 1) URL: https://routeme.sh/chain/evm/1-ethereum-mainnet - Base (Chain ID: 8453) URL: https://routeme.sh/chain/evm/8453-base - Arbitrum One (Chain ID: 42161) URL: https://routeme.sh/chain/evm/42161-arbitrum-one - BNB Smart Chain Mainnet (Chain ID: 56) URL: https://routeme.sh/chain/evm/56-bnb-smart-chain-mainnet - Polygon Mainnet (Chain ID: 137) URL: https://routeme.sh/chain/evm/137-polygon-mainnet - OP Mainnet (Chain ID: 10) URL: https://routeme.sh/chain/evm/10-op-mainnet - Cronos Mainnet (Chain ID: 25) URL: https://routeme.sh/chain/evm/25-cronos-mainnet - World Chain (Chain ID: 480) URL: https://routeme.sh/chain/evm/480-world-chain - ApeChain (Chain ID: 33139) URL: https://routeme.sh/chain/evm/33139-apechain - Gnosis (Chain ID: 100) URL: https://routeme.sh/chain/evm/100-gnosis - Linea (Chain ID: 59144) URL: https://routeme.sh/chain/evm/59144-linea - XDC Network (Chain ID: 50) URL: https://routeme.sh/chain/evm/50-xdc-network - Lisk (Chain ID: 1135) URL: https://routeme.sh/chain/evm/1135-lisk - Monad (Chain ID: 143) URL: https://routeme.sh/chain/evm/143-monad - Abstract (Chain ID: 2741) URL: https://routeme.sh/chain/evm/2741-abstract - Berachain (Chain ID: 80094) URL: https://routeme.sh/chain/evm/80094-berachain - Plasma Mainnet (Chain ID: 9745) URL: https://routeme.sh/chain/evm/9745-plasma-mainnet - Avalanche C-Chain (Chain ID: 43114) URL: https://routeme.sh/chain/evm/43114-avalanche-c-chain - Celo Mainnet (Chain ID: 42220) URL: https://routeme.sh/chain/evm/42220-celo-mainnet - Mantle (Chain ID: 5000) URL: https://routeme.sh/chain/evm/5000-mantle - BOB (Chain ID: 60808) URL: https://routeme.sh/chain/evm/60808-bob - Moonbeam (Chain ID: 1284) URL: https://routeme.sh/chain/evm/1284-moonbeam - Unichain (Chain ID: 130) URL: https://routeme.sh/chain/evm/130-unichain - HyperEVM (Chain ID: 999) URL: https://routeme.sh/chain/evm/999-hyperevm - Ethereum Hoodi (Chain ID: 560048) URL: https://routeme.sh/chain/evm/560048-ethereum-hoodi - katana (Chain ID: 747474) URL: https://routeme.sh/chain/evm/747474-katana - Sei Network (Chain ID: 1329) URL: https://routeme.sh/chain/evm/1329-sei-network - Ink (Chain ID: 57073) URL: https://routeme.sh/chain/evm/57073-ink - Sonic Mainnet (Chain ID: 146) URL: https://routeme.sh/chain/evm/146-sonic-mainnet - Soneium (Chain ID: 1868) URL: https://routeme.sh/chain/evm/1868-soneium - Plume Mainnet (Chain ID: 98866) URL: https://routeme.sh/chain/evm/98866-plume-mainnet - zkSync Mainnet (Chain ID: 324) URL: https://routeme.sh/chain/evm/324-zksync-mainnet - Scroll (Chain ID: 534352) URL: https://routeme.sh/chain/evm/534352-scroll - Metis Andromeda Mainnet (Chain ID: 1088) URL: https://routeme.sh/chain/evm/1088-metis-andromeda-mainnet - Stable Mainnet (Chain ID: 988) URL: https://routeme.sh/chain/evm/988-stable-mainnet - Immutable zkEVM (Chain ID: 13371) URL: https://routeme.sh/chain/evm/13371-immutable-zkevm - Lens (Chain ID: 232) URL: https://routeme.sh/chain/evm/232-lens - Hemi (Chain ID: 43111) URL: https://routeme.sh/chain/evm/43111-hemi - Taiko (Chain ID: 167000) URL: https://routeme.sh/chain/evm/167000-taiko - Ronin (Chain ID: 2020) URL: https://routeme.sh/chain/evm/2020-ronin - Tempo Mainnet (Chain ID: 4217) URL: https://routeme.sh/chain/evm/4217-tempo-mainnet - Etherlink Mainnet (Chain ID: 42793) URL: https://routeme.sh/chain/evm/42793-etherlink-mainnet - Flare Mainnet (Chain ID: 14) URL: https://routeme.sh/chain/evm/14-flare-mainnet - MegaETH (Chain ID: 4326) URL: https://routeme.sh/chain/evm/4326-megaeth - Swellchain (Chain ID: 1923) URL: https://routeme.sh/chain/evm/1923-swellchain - Corn (Chain ID: 21000000) URL: https://routeme.sh/chain/evm/21000000-corn - Mode (Chain ID: 34443) URL: https://routeme.sh/chain/evm/34443-mode - Fraxtal (Chain ID: 252) URL: https://routeme.sh/chain/evm/252-fraxtal - Flow EVM Mainnet (Chain ID: 747) URL: https://routeme.sh/chain/evm/747-flow-evm-mainnet - Rootstock Mainnet (Chain ID: 30) URL: https://routeme.sh/chain/evm/30-rootstock-mainnet - Gravity Alpha Mainnet (Chain ID: 1625) URL: https://routeme.sh/chain/evm/1625-gravity-alpha-mainnet - Blast (Chain ID: 81457) URL: https://routeme.sh/chain/evm/81457-blast - opBNB Mainnet (Chain ID: 204) URL: https://routeme.sh/chain/evm/204-opbnb-mainnet - Boba Network (Chain ID: 288) URL: https://routeme.sh/chain/evm/288-boba-network - OP Sepolia Testnet (Chain ID: 11155420) URL: https://routeme.sh/chain/evm/11155420-op-sepolia-testnet - Superposition (Chain ID: 55244) URL: https://routeme.sh/chain/evm/55244-superposition - Telos EVM Mainnet (Chain ID: 40) URL: https://routeme.sh/chain/evm/40-telos-evm-mainnet - Kaia Mainnet (Chain ID: 8217) URL: https://routeme.sh/chain/evm/8217-kaia-mainnet - Fuse Mainnet (Chain ID: 122) URL: https://routeme.sh/chain/evm/122-fuse-mainnet - Sophon (Chain ID: 50104) URL: https://routeme.sh/chain/evm/50104-sophon - Morph (Chain ID: 2818) URL: https://routeme.sh/chain/evm/2818-morph - Plasma Testnet (Chain ID: 9746) URL: https://routeme.sh/chain/evm/9746-plasma-testnet - Xai Mainnet (Chain ID: 660279) URL: https://routeme.sh/chain/evm/660279-xai-mainnet - Zircuit Mainnet (Chain ID: 48900) URL: https://routeme.sh/chain/evm/48900-zircuit-mainnet - Matchain (Chain ID: 698) URL: https://routeme.sh/chain/evm/698-matchain - X Layer Mainnet (Chain ID: 196) URL: https://routeme.sh/chain/evm/196-x-layer-mainnet - Cyber Mainnet (Chain ID: 7560) URL: https://routeme.sh/chain/evm/7560-cyber-mainnet - Amoy (Chain ID: 80002) URL: https://routeme.sh/chain/evm/80002-amoy - Base Sepolia Testnet (Chain ID: 84532) URL: https://routeme.sh/chain/evm/84532-base-sepolia-testnet - Arbitrum Sepolia (Chain ID: 421614) URL: https://routeme.sh/chain/evm/421614-arbitrum-sepolia - Somnia Testnet (Chain ID: 50312) URL: https://routeme.sh/chain/evm/50312-somnia-testnet - Manta Pacific Mainnet (Chain ID: 169) URL: https://routeme.sh/chain/evm/169-manta-pacific-mainnet - Astar (Chain ID: 592) URL: https://routeme.sh/chain/evm/592-astar - Ethereum Sepolia (Chain ID: 11155111) URL: https://routeme.sh/chain/evm/11155111-ethereum-sepolia - Core Blockchain Mainnet (Chain ID: 1116) URL: https://routeme.sh/chain/evm/1116-core-blockchain-mainnet - XRPL EVM (Chain ID: 1440000) URL: https://routeme.sh/chain/evm/1440000-xrpl-evm - SagaEVM (Chain ID: 5464) URL: https://routeme.sh/chain/evm/5464-sagaevm - Redbelly Network Mainnet (Chain ID: 151) URL: https://routeme.sh/chain/evm/151-redbelly-network-mainnet - Nibiru cataclysm-1 (Chain ID: 6900) URL: https://routeme.sh/chain/evm/6900-nibiru-cataclysm-1 - Botanix Mainnet (Chain ID: 3637) URL: https://routeme.sh/chain/evm/3637-botanix-mainnet - Mezo (Chain ID: 31612) URL: https://routeme.sh/chain/evm/31612-mezo - Filecoin - Mainnet (Chain ID: 314) URL: https://routeme.sh/chain/evm/314-filecoin-mainnet - Fantom Opera (Chain ID: 250) URL: https://routeme.sh/chain/evm/250-fantom-opera - SKALE Europa Hub (Chain ID: 2046399126) URL: https://routeme.sh/chain/evm/2046399126-skale-europa-hub - ThunderCore Mainnet (Chain ID: 108) URL: https://routeme.sh/chain/evm/108-thundercore-mainnet - Hedera Mainnet (Chain ID: 295) URL: https://routeme.sh/chain/evm/295-hedera-mainnet - Arc Testnet (Chain ID: 5042002) URL: https://routeme.sh/chain/evm/5042002-arc-testnet - Zilliqa 2 (Chain ID: 32769) URL: https://routeme.sh/chain/evm/32769-zilliqa-2 - Hyperliquid EVM Testnet (Chain ID: 998) URL: https://routeme.sh/chain/evm/998-hyperliquid-evm-testnet - Tenet (Chain ID: 1559) URL: https://routeme.sh/chain/evm/1559-tenet - Arbitrum Nova (Chain ID: 42170) URL: https://routeme.sh/chain/evm/42170-arbitrum-nova - Viction (Chain ID: 88) URL: https://routeme.sh/chain/evm/88-viction - Somnia Mainnet (Chain ID: 5031) URL: https://routeme.sh/chain/evm/5031-somnia-mainnet - BitTorrent Chain Mainnet (Chain ID: 199) URL: https://routeme.sh/chain/evm/199-bittorrent-chain-mainnet - Chiliz Chain (Chain ID: 88888) URL: https://routeme.sh/chain/evm/88888-chiliz-chain - Polygon zkEVM (Chain ID: 1101) URL: https://routeme.sh/chain/evm/1101-polygon-zkevm - WEMIX3.0 Mainnet (Chain ID: 1111) URL: https://routeme.sh/chain/evm/1111-wemix3-0-mainnet - Tempo Testnet (Chain ID: 42431) URL: https://routeme.sh/chain/evm/42431-tempo-testnet - Zora (Chain ID: 7777777) URL: https://routeme.sh/chain/evm/7777777-zora - Wanchain (Chain ID: 888) URL: https://routeme.sh/chain/evm/888-wanchain ## Providers Total providers: 6 - alchemy URL: https://routeme.sh/providers/alchemy - ankr URL: https://routeme.sh/providers/ankr - chainstack URL: https://routeme.sh/providers/chainstack - drpc URL: https://routeme.sh/providers/drpc - grove URL: https://routeme.sh/providers/grove - quicknode URL: https://routeme.sh/providers/quicknode ## Blog Posts Total blog posts: 10 ### Research (4) - [object Object] URL: https://routeme.sh/blog/rpc-client-research-v2 Published: 2026-05-12 - [object Object] URL: https://routeme.sh/blog/how-reliable-is-your-node-hr Published: 2026-04-17 - [object Object] URL: https://routeme.sh/blog/mapping-the-rpc-landscape-mr Published: 2026-04-17 - [object Object] URL: https://routeme.sh/blog/rpc-data-quality-update Published: 2026-04-17 ### Provider (1) - [object Object] URL: https://routeme.sh/blog/boar-network-joins Published: 2026-04-30 ### Product (4) - [object Object] URL: https://routeme.sh/blog/routemesh-added-to-raycast-official-mcp-registry-v2 Published: 2026-03-11 - [object Object] URL: https://routeme.sh/blog/organization-support-added Published: 2026-01-28 - [object Object] URL: https://routeme.sh/blog/sentinel-launch Published: 2026-01-21 - [object Object] URL: https://routeme.sh/blog/intro Published: 2025-09-05 ### New Chain (1) - [object Object] URL: https://routeme.sh/blog/routemesh-push-donut-testnet Published: 2025-12-11 ## Case Studies Total case studies: 5 - Gamma URL: https://routeme.sh/case-studies/gamma Published: 2025-10-23 - Li.Fi URL: https://routeme.sh/case-studies/lifi Published: 2025-10-23 - Salt URL: https://routeme.sh/case-studies/salt Published: 2025-10-23 - vaults.fyi URL: https://routeme.sh/case-studies/vaults-fyi Published: 2025-10-23 - DAMM Capital URL: https://routeme.sh/case-studies/damm-capital Published: 2025-10-23