CompareNodes

We measure RPC performance from 30 locations on 6 continents in 3 clicks and 35 seconds.

Visit our directory for 210 web3 infra providers.

[CompareNodes @CompareNodes]

We apologize to our visitors because we don't have country and personnel information for @triport_io @sodaeio @ordofi and @FlashBlocktrade in our directory since we were not able to find their pages on LinkedIn.

Still, you can use our public RPC Inspector Pro to compare their performance with the other 200+ providers in our infrastructure directory for 500+ web3 protocols

https://t.co/nt6Dpp6qSk

https://t.co/lNGZSVIxXO

https://t.co/KrwmRxBxM3

https://t.co/cCARAdnczk

[GetBlock 🧊 @getblockio]

And a first look at how they perform.

@CompareNodes put GetBlock to the test across thousands of Ethereum events in Frankfurt and Virginia. The results are worth a look

https://t.co/IDxQ0LBBra

[CompareNodes @CompareNodes]

@ordofi pls get well soon

[GetBlock 🧊 @getblockio]

Within a month of launch, GetBlock Webhooks challenged the biggest name in our segment on the largest smart contract network.

In a test by @CompareNodes GetBlock delivered first:

→ in 86.2% of 5,692 events in Frankfurt
→ in 62% of 6,885 in Virginia

[Tatum @tatum_io]

Meet Access Logs, now in your Tatum Dashboard 🔎

Track API key traffic, response times, bandwidth and rate limits.

Zoom in on spikes, inspect requests and jump from failed requests to Error Logs.

[CompareNodes @CompareNodes]

Same goes for Selvage Labs and @BlockVectra :(

[CompareNodes @CompareNodes]

We apologize to our visitors because we don't have country and personnel information for @triport_io @sodaeio @ordofi and @FlashBlocktrade in our directory since we were not able to find their pages on LinkedIn.

Still, you can use our public RPC Inspector Pro to compare their performance with the other 200+ providers in our infrastructure directory for 500+ web3 protocols

https://t.co/nt6Dpp6qSk

https://t.co/lNGZSVIxXO

https://t.co/KrwmRxBxM3

https://t.co/cCARAdnczk

[CompareNodes @CompareNodes]

@arcdex2026 if you ever need more public endpoints for Arc, Robinhood, Solana, BSC etc. make sure to visit our directories for 500+ protocols

Arc with 34 public endpoints
https://t.co/mySSS9IsNN

Robinhood with 30 endpoints
https://t.co/1tEPBrWqrd

and all others in

https://t.co/BS0z67VlqL

[GetBlock 🧊 @getblockio]

🇸🇬 Singapore is home turf

@token2049 gets the full GetBlock leadership, Oct 5-8:

→ @GetVasily, CEO
→ @AlexAlekhinEth, Head of Product
→ Nikita Iugov, CTO, not on X as someone still has to do the actual work

First up: a talk with @Constantinefom father of GetBlock's AI brain @Ardor_Cerebrum

[CompareNodes @CompareNodes]

@apecoin @Alchemy @BoredApeYC @aloksahay @blockchainzilla @uttam_singhk @wonk1m Get the fastest 4 public endpoints for development on ApeChain mainnet from your location and hosted by @Calderaxyz @dRPCorg @TenderlyApp and @thirdweb

Try them in our library at

https://t.co/c60kt54zR9

[CompareNodes @CompareNodes]

Kudos to the @useSolami engineering team for a distinctive webhook feature: users can choose the geographic origin of deliveries among NYC, AMS, and FRA.

We found no equivalent documented option from @Helius , @Alchemy , @Quicknode , or @BlockdaemonHQ for their Solana Mainnet webhooks.

We wanted to determine whether this feature was useful or merely a gimmick so we created four Solami webhooks to filter TXs for the same address:

Solami FRA → AWS Frankfurt
Solami NYC → AWS Frankfurt
Solami FRA → AWS Virginia
Solami NYC → AWS Virginia

We compared API Gateway arrival timestamps for each transaction received through all four paths.
Across 2,824 transactions, Solami FRA → AWS Frankfurt arrived first every time, with a median lead of 71 ms over Solami NYC → AWS Frankfurt.

For deliveries into AWS Virginia, Solami NYC won 2,309 times, while Solami FRA won 463 times, and 52 arrivals were within 1 ms.

Solami NYC had a median advantage of 5 ms delivering into AWS Virginia, confirming that the selected origin can affect which delivery arrives first.

For the absolute earliest arrival in AWS Virginia, the best setup is to send from both Solami NYC and Solami FRA, then process your own events on the arrival of the first copy, and just ignore the duplicate.

Our conclusion: Solami origin selection is useful, giving developers meaningful control over latency, redundancy, and cost.

[Tatum @tatum_io]

Sol loves September 😻
Always closing in the green since 2021.

In 2026? 👉 +14.61%

Ship the monthly return, the heatmap, and the "up this month" number to your users, with this one call.

[DWELLIR 🛡️🛠️ @DwellirOfficial]

You can now pay us with stablecoins through @stripe .

It works on every paid plan, from Developer to Enterprise, plus Unlimited Nodes and dedicated node clusters.

Thanks to @b3nb3rke and the Stripe team.

[CompareNodes @CompareNodes]

@Calderaxyz Caldera public endpoint for Manta Pacific mainnet delivers comparable global p95 latencies to Manta's own public endpoint

https://t.co/hTmKQ6R4qA

[CompareNodes @CompareNodes]

After ~ 8.5h of webhook collection in AWS Virgina the Quicknode free account on Solana mainnet wins a narrow victory over Helius.

The difference in the count of deliveries is because Helius dispatched a wider range of events for the token account.

[CompareNodes @CompareNodes]

On Oct 1, we have new observations about Solami webhook performance on Solana mainnet.

Again we measured the arrivals into AWS Frankfurt and AWS Virginia but in a simultaneous comparison with both Alchemy and Helius.

Solami's deliveries into our APIGs were again arriving earlier than Alchemy and also earlier than Helius.

Separately comparing just Alchemy vs. Helius, we find that Alchemy did better in arrival "wins", but it seems that Alchemy has a bizarre "problem" with about 5% of arrivals being late by a long margin (observed).

Next up / currently underway is Solami vs. Helius vs. Quicknode comparison into AWS Frankfurt only, since Quicknode's free account serves just one wh at a time, so we will compare AWS Virginia in a later run.

[CompareNodes @CompareNodes]

Our conclusion after ~14.3h of processing is that Solami WH delivered msgs earlier than Alchemy to our receivers in AWS Frankfurt and AWS Virginia

[CompareNodes @CompareNodes]

If you consume Solana data in AWS and use webhooks, then we can recommend @useSolami.

As of Sept 30. ~15:30 UTC we have been running 4 webhooks for about 11h with identical subscriptions for raw transfers and address 5tzFkiKscXHK5ZXCGbXZxdw7gTjjD1mBwuoFbhUvuAi9

2 WHs for @useSolami vs. 2 WHs for @Alchemy
one pair delivering msgs to our collector in AWS Frankfurt and the other pair delivering to AWS Virginia.

In each case we get arrival tms in the APIG and then compare them by hashes.

Our results are that @useSolami WHs deliver msgs earlier than the same msgs are delivered by Alchemy's service.

E.g. in Frankfurt, Solami wins 4310 msgs to 1 win for Alchemy.

We will publish another analysis once we complete our target duration of ~12h.

Btw, Solami's WH setup gives us the choice of location so we used one FRA and one NYC WH, while for Alchemy we don't have a choice of location so we just created two WHs so that we can give them different targets for the locations of our receivers. Ofc, the results could be different for an address with more activity, but Alchemy did not accept the USDC address whereas it did work for Solami when we did a preliminary experiments.

[CompareNodes @CompareNodes]

In our web3 infrastructure directory with 211 providers, Solana is now supported by exactly 1 provider for each of the 99 Luftballons

https://t.co/4DuLYwi70S

[CompareNodes @CompareNodes]

correction:
7KJjY7rArbydeLBF7gQ5LdqXRKRYyPArT99NEctsHsgU is the address used in the run;

5tzFkiKscXHK5ZXCGbXZxdw7gTjjD1mBwuoFbhUvuAi9 was the address rejected by Alchemy.