CompareNodes

Independent metrics about @SpectrumNodes RPC performance are now available at comparenodes.com/providers/spec… Spectrum users can validate performance made by Spectrum and their competitors. Spectrum serves #WebSockets for numerous protocols incl. #Ethereum mainnet: using our free public #RPC Inspector Pro, anyone can compare the speed of newHeads notifications between Spectrum and any other wss provider like @Dwellir, @OnFinality, @zan_team , @NOWNodes etc. RPC Inspector Pro collects data from 31 locations on 6 continents to show you which provider is first to “see” each block notification in each location. The results look like this output for Alchemy wss vs. Chainsstack on Ethereum mainnet comparenodes.com/global-rpc-per…

If you are addicted to data about #Solana blocks then you should indulge in this safe-for-work video about Solana block propagation around the world. We used our RPC Inspector Pro and Alchemy gRPC to capture arrival timestamps from 31 locations on 6 continents for finalized blocks. This video shows two minutes of blocks from 421,991,948 to 421,992,275. Each “pop” is the location that was first to observe a new block. The lines streak out from that 1st location to every other subsequent location, in the order of their arrivals. The size of each location dot is proportional to the count of 1st-to-block “wins” in that location. RPC Inspector Pro is free and public: anyone can use gRPC or WebSockets endpoints to capture and visualize propagation for networks in the EVM / SVM / CosmosBFT / Substrate ecosystems, or Sui checkpoints as well. See the Solana mainnet results for this run comparenodes.com/global-rpc-per… Use our visualizer to view additional stats comparenodes.com/visualize/inde…

Independent tools for @BoltRPC performance are now available at comparenodes.com/providers/bolt… BoltRPC users can validate performance claims made by BoltRPC and their competitors. BoltRPC serves #WebSockets for #Ethereum mainnet: using our free public RPC Inspector Pro, anyone can compare the speed of newHeads notifications between BoltRPC and any other wss provider like @DwellirOfficial , @SpectrumNodes , @Alchemy , @Quicknode etc. RPC Inspector Pro collects data from 31 locations on 6 continents to determine which provider is first to “see” each block notification in each location. The results look like this output for Alchemy wss vs. @ChainstackHQ on Ethereum mainnet comparenodes.com/global-rpc-per…

@NoodeAPI and @node_101 | let us know when your RPC service is running and we will add you to our free directory with 215 web3 infra providers for data and APIs, incl. 135 providers for Ethereum comparenodes.com/protocols/ethe…

About a week ago we reported that @getblockio WebSocket in Europe deliver notifications about newHeads on Optimism mainnet more quickly than @Alchemy . Earlier today we checked in on their websockets for #Arbitrum mainnet too. This time we brought our global "blockchain camera" to capture the visual approximation about block notifications arriving into each of the 8 locations: Frankfurt, Paris, London, Ireland, Milan, Zurich, Stockholm and Zaragoza. Below is the video we made from our public & free propagation visualizer. Blocks are in the range of 464,847,856 to 464,847,994 abbreviated as ..856 to ..994. In the video, GetBlock is "green" while Alchemy is "red": whichever websocket is first to see a new block number in that location, it adds to the green/red totals for that that location. If GetBlock is first to see a new number overall, the pop label in that location is green "A"... or the red "B"... in case of Alchemy. And if you look closely, you will see a lot of green "As" because GetBlock was 1st overall for every number in this range, for this group of locations. Also, GetBlock "won" all 8 locations on total block-location counts too, which is why all the locations are green and none are red. Lastly, Paris and Frankfurt are larger in size because new blocks were observed there most often. Ofc, we collected all our telemetry from AWS locations which could have positive or negative effect on either set of websockets. Likewise, this situation could be temporary and we recommend that #RPC buyers run multiple rounds of performance tests with our public RPC Inspector Pro at @CompareNodes. #blockchain #infrastructure #performance

Fresh off the @Alchemy #gRPC stream, here is our visualization for slot/block propagation across the globe on #Solana mainnet from 420,897,055 to 420,897,145

If you get global Bitcoin #RPC from @ChainstackHQ or @zan_team then go ahead and ignore @Alchemy's release for #Bitcoin mainnet because Chainstack and ZAN already deliver great service to you Details in comparenodes.com/global-rpc-per… comparenodes.com/global-rpc-per…

Find our logo and win a prize 🔎 👇

#BSC mainnet is the 7th and final EVM protocol in our $49/mo global RPC showdown with @DwellirOfficial vs. @ChainstackHQ via JSON-RPC and WebSocket from 31 locations. Chainstack wins 42 to 3 across JSON-RPC and WebSocket; but, we did observe 2 timeouts during JSON-RPC runs and in one round Chainstack's eth_getLogs was missing ~3% of the blocks which were already announced by the same endpoint via eth_getBlockByNumber; hence a dip in block availability; Otherwise, both Chainstack and Dwellir delivered 100% blockNumber consistency and availability; Lastly, Dwellir had 4 timeouts in WebSocket and Chainstack 1 lost WebSocket. Btw, the results for Polygon mainnet are in x.com/CompareNodes/s…

The results are in for #Polygon mainnet in our $49/mo global RPC showdown with @DwellirOfficial vs. @ChainstackHQ via JSON-RPC and WebSocket from 31 locations. Chainstack appears to dominate JSON-RPC for the overall result of 29 to 16 while Dwellir's was well ahead in WebSocket newHeads; Both achieved perfect 100% blockNumber consistency and 100% block availability; and Chainstack had 3 timeouts; Dwellir did win the entire WebSocket and did so with 115 connection problems, out of possible 465! Btw, earlier results for #Tempo mainnet are in x.com/CompareNodes/s…

@venumdev vs. Helius RPC from Frankfurt and Singapore comparenodes.com/global-rpc-per…

Upgraded the public analytics page: - read + write latency per tier (RPC, API) - live RPS - request volume, 24h + all-time - SSE stream open TTFB venum.dev/analytics

@FluxRPC Compare Flux RPC Yellowstone gRPC with any other gRPC block propagation remotely from 30 locations; or, compare gRPC against websocket, also on blocks comparenodes.com/performance-in…

And our dev plan is now only $15 for the first month. The includes Yellowstone gRPC!

@datanodes_net Use our global RPC Inspector Pro to measure Nodefleet performance remotely from 32 locations: EVM, Substrate, Tendermint etc. comparenodes.com/providers/node…

One endpoint. One API key. +35 networks curl -s rpc.datanodes.nodefleet.net \ -H "x-api-key: KEY" \ -H "x-chain: eth-mainnet" \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","method":"eth_blockNumber","id":1}' Learn more at → datanodes.nodefleet.net

@Alchemy @world_chain_ @worldnetwork Devs on World Chain should use Alchemy's public endpoint because it serves a pretty low latency, globally comparenodes.com/global-rpc-per…

18M+ verified humans. 160+ countries. Millions of transactions every day. @world_chain_ runs proof of human infrastructure at a scale for global use.🧵

1/ A thread on RPC client diversity across 1000+ EVM chains and the providers that run them (hint: see who is behind). At RouteMesh, we have thousands of nodes in our system and screen them rigorously for performance, but also understand metadata such as what client they run.

Finally it is time for @tempo in our $49/mo global RPC showdown with @DwellirOfficial vs. @ChainstackHQ via JSON-RPC and WebSocket from 31 locations. Chainstack appears to do better with 37 to 8 measures incl. a sweep in JSON-RPC; Dwellir did better than Chainstack on WebSocket newHeads propagation; although Chainstack did win 7 runs for WebSocket, we observed many long lags in Bangkok, Seoul, Kuala Lumpur etc. Both achieved perfect 100% blockNumber consistency; block availability was mainly affected by empty blocks for both; Btw, results for #HyperEVM mainnet are in x.com/CompareNodes/s…

#HyperEVM mainnet is the 4th network in our $49/mo global RPC showdown with @DwellirOfficial vs. @ChainstackHQ for JSON-RPC and WebSocket from 31 locations. Chainstack appears to do better with 35 to 10 measures incl. a sweep in JSON-RPC, very much due to Dwellir's slower showing from Sydney and Melbourne which increased their p95; Dwellir did better than Chainstack on WebSocket newHeads propagation (not weighted into percentiles); Both achieved perfect 100% blockNumber consistency; block availability was mainly affected by empty blocks for both; and Dwellir did have 23 to 2 fails & timeouts; During the runs for WebSockets, we observed 4 problems for Chainstack and 1 for Dwellir (out of a total of 465 total connections for each). Btw, the results for Arbitrum mainnet are in x.com/CompareNodes/s…

Next up in our $49/mo global RPC showdown is #Arbitrum One mainnet with @DwellirOfficial vs. @ChainstackHQ for JSON-RPC and WebSocket from 31 locations. Based on 30 runs over the course of 5 consecutive days, it appears to us that Chainstack achieves a perfect win with 45 to 0 possible major performance metrics for HTTPS and WSS; Both Dwellir and Chainstack had perfect 100% blockNumber consistency and 0 fails across 15 JSON-RPC runs; block availability dipped under 100% for both but only due to “empty” blocks; During the runs with WebSocket, we observed 1 timeout for Dwellir from São Paulo during warmup; while Chainstack had a total of 6 broken / premature connections out of the 465 (31 locations * 15 rounds). Btw, results for Base mainnet are in x.com/CompareNodes/s…