RPC Endpoint Checker

WHAT IT DOES RPC Endpoint Checker tests the performance and status of any JSON-RPC endpoint for EVM-compatible chains. Enter an RPC URL (e.g., https://eth.llamarpc.com), and the tool measures the latency, checks if the endpoint is online, and retrieves key network data including chain ID, latest block number, block timestamp, client version, and network version. The tool displays the latency in milliseconds, a performance badge (Fast, Medium, Slow, Very Slow), and a visual latency bar. You can also use the "Use wallet RPC" button to test the RPC endpoint your wallet is currently connected to. This is essential for developers choosing between RPC providers, debugging connection issues, monitoring endpoint performance, or comparing different RPC services. HOW TO USE Connect your wallet using the BGWallet bridge (MetaMask or any Web3 wallet). Enter the RPC endpoint URL in the input field — it must start with http:// or https://. Click "Check endpoint" to test the RPC. The tool sends a series of JSON-RPC requests to the endpoint and measures the round-trip time. Results display the endpoint URL, online status, latency in milliseconds, chain ID, latest block number, block timestamp, client version, network version, and a performance badge with a visual latency bar. You can also click "Use wallet RPC" to automatically populate the input with your wallet's current RPC endpoint and test it. TECHNICAL MECHANISM The tool uses ethers.js to interact with the RPC endpoint. It first creates a JsonRpcProvider instance with the provided URL. It then measures the latency by capturing the timestamp before and after making requests. The tool sends multiple requests sequentially: getNetwork() to retrieve the chain ID, getBlockNumber() to get the latest block, getBlock() to fetch the block timestamp, and sends raw JSON-RPC requests for web3_clientVersion and net_version to get client and network version information. The total latency is measured from the start of the first request to the completion of the last request. The performance is categorized based on the latency: Fast (1000ms). The tool handles errors gracefully, returning an error status with the error message and the measured latency up to the point of failure. All data is fetched directly from the RPC endpoint — no external APIs are used. WHAT IT CANNOT SEE The tool cannot detect all RPC endpoint issues (e.g., rate limiting, request limits, or data consistency issues) without extensive testing or sending a large volume of requests. It cannot compare performance across multiple endpoints simultaneously — endpoints are tested sequentially, so performance may vary based on network conditions and test order. It cannot determine endpoint reliability over time from a single check — reliability requires continuous monitoring. It cannot detect endpoint-specific quirks or compatibility issues with complex requests (e.g., eth_getLogs with large ranges, or eth_call with state overrides) — it only tests basic methods. It cannot verify endpoint authenticity or security (SSL certificate validity, TLS configuration, or man-in-the-middle attacks) — it only checks if the endpoint responds to requests. It cannot test endpoints that require authentication headers or API keys. The tool is read-only and does not sign any transactions. PLEASE NOTE This tool works exclusively with EVM-compatible JSON-RPC endpoints (Ethereum, BNB Chain, Polygon, Arbitrum, Optimism, Base, Avalanche C-Chain, Fantom, and others). Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported. Latency measurements may vary based on network conditions, geographic location, and endpoint load. A single check provides a snapshot of performance — not a comprehensive evaluation. The tool does not store any data — all reads happen live. The tool is provided as-is with no warranty or liability. Always verify RPC endpoints from trusted sources.