The Best Public RPC Endpoint on Optimism Mainnet?

The goal of our analysis is to determine the best public endpoint on Optimism mainnet for each continent as well as the best overall, globally. According to our infrastructure directory for Optimism, there are at least 17 public endpoints for the mainnet on January 19, 2024 (list).

We are using our own (rpc) Performance Inspector which is a public web application. RPC providers change/expand their infrastructure and locations all the time which is why it might be useful for you to repeat test steps at your convenience here.

Please note that this performance comparison is not benchmarking. It would not make sense to use flood, chainbench (by Chainstack), k6 or another stress test / benchmarking tool for at least these reasons:

  • The endpoints are being used by the public and suffocating them with requests might degrade the experience for other unsuspecting users;
  • In most cases, the providers limit inbound traffic to public endpoints based on IP address and we would probably hit http429 errors very quickly.

Our Methodology

  • We believe in WAGMI to mean the entire world which is why we send simultaneous RPC requests from 27 locations on 6 continents. Our “probes” are in AWS and not “in” your laptop browser.
  • For this analysis we configured the inspector to use the eth_blockNumber method and you can choose to use eth_getBalance instead.
  • Another setting for our runs was the limit to “not more than 1 request per region per second” whereas the alternative is to let each probe run as fast as it gets the previous response.
  • You can create an account with other providers like Infura, Alchemy, QuickNode and use their private endpoints to perform a similar analysis. We omitted providers without public endpoints but you can include them. We don’t record endpoints and our results contain just the domain names of the URLs which were included in the runs.
  • Since there were 17 providers and our inspector form accepts two at a time, we did 9 runs and combined their results for complete rankings. Although each run is for 2 providers, their computations are independent as each utilizes a separate instance of our RPC probe. See this Google Sheet or view “raw” individual results on the bottom of the page.
  • Each pair of providers was run for 30 seconds and should have been measured for 30 requests from each region for a total of 810 measures. Requests are dispatched sequentially, one at a time. Latency duration is the sum of timings of milliseconds from the moment the request is sent until a success response gets back to us. Btw, we do a warmup request in each region which is omitted from the results.
  • Additional info is in the FAQ on the bottom of the RPC Performance Inspector control form.

Eliminated Endpoints

  • POKT Network endpoint errored out twice in a row from Frankfurt and Singapore.
  • OnFinality is the only provider to have triggered http429 and did so from each of the 27 regions.
  • DRPC had almost 4% of errors like “Error (500) on request no.1: {"error":{"message":"Unable to perform request","code":19}}”. You can read the error responses in the results pages (we capture up to 4 errors from each location for debugging purposes).

The Top 14 Public Endpoints on Optimism Mainnet

Overall / Global Ranking

(27 AWS regions on January 19, 2024)

NoProviderAvg (ms)Failed429SuccessDuration (ms)
1Nodies73.190081059,283
2thirdweb78.760081063,795
3Tenderly89.540081072,524
4Ankr100.560081081,452
5BlockPI Network113.750081092,140
6Blast API135.1300810109,457
7Gateway.fm136.0600810110,212
8LlamaNodes143.9500810116,598
91RPC156.6200810126,859
10Allnodes157.2900810127,406
11Optimism Foundation189.4900810153,487
12BlockEden.xyz354.5100810287,150
13Etherspot413.5800810334,998
14OMNIA Protocol533.0210809431,216

Slow or Fast?

Why is some endpoint slower or faster than another? In short, we don’t know from the “outside” because we don’t have access to the host information such as the server/cluster cores, memory, networking etc. In our experience these are the most important factors:

  1. the physical distance between the RPC server and the consumer;
  2. quantity of users/requests that are being served at the moment;
  3. size of the hardware.

In other words, no amount of CPU cores or memory can overcome the physics of networking transmission and the maximum theoretical speed of signals. Moreover a small server sitting “idle” could deliver responses more quickly than a huge cluster at a popular infra provider during a huge NFT mint.

Since distance is such a hard factor, it is very important that providers run nodes near population centers on each or most continents so that they can serve both “types” RPC consumers:

  • globally distributed end-users like wallets;
  • analytics apps like Dune etc. which generally ingest data into their servers located in one or a few data centers.

Our recommendation is to interpret the results in the following way: if you were to add your usage to these public endpoints and send requests similar to requests that we sent from nearby locations, then you too could expect to experience a similar performance. With a caveat that external factors might have changes since we typed this sentence and providers could have made changes to their infrastructure or other users could have changed their consumption patterns. So make sure to check yourself again.

As far as the efforts to cover the whole globe, we have also split results for 6 continents.

Best Optimism Mainnet Public Endpoints for North America

(5 AWS regions on January 19, 2024)

NoProviderAvg (ms)Failed429SuccessDuration (ms)
1Tenderly20.20001503,030
2LlamaNodes40.53001506,080
3thirdweb48.91001507,337
4Nodies57.22001508,583
5BlockPI Network63.69001509,554
6Blast API65.81001509,872
7Allnodes88.530015013,279
8Ankr97.550015014,632
91RPC103.330015015,500
10Gateway.fm130.450015019,567
11Optimism Foundation151.270015022,691
12OMNIA Protocol152.270015022,841
13BlockEden.xyz238.890015035,834
14Etherspot427.490015064,123

Best Optimism Mainnet Public Endpoints for South America

(1 AWS region on January 19, 2024)

NoProviderAvg (ms)Failed429SuccessDuration (ms)
1thirdweb96.5000302,895
2Ankr113.6700303,410
3Tenderly121.5300303,646
4Nodies129.7300303,892
5LlamaNodes137.3000304,119
6Allnodes143.2000304,296
7Blast API144.1300304,324
8BlockPI Network201.0000306,030
9Gateway.fm201.2000306,036
101RPC227.3700306,821
11OMNIA Protocol243.8700307,316
12Optimism Foundation251.2700307,538
13BlockEden.xyz412.17003012,365
14Etherspot604.53003018,136

Best Optimism Mainnet Public Endpoints for Europe

(8 AWS regions on January 19, 2024)

NoProviderAvg (ms)Failed429SuccessDuration (ms)
1Tenderly21.18002405,082
2Gateway.fm28.24002406,778
3Nodies40.98002409,834
4Optimism Foundation42.680024010,244
5thirdweb52.530024012,607
6Allnodes55.670024013,360
7BlockPI Network74.320024017,837
8Blast API75.050024018,013
9Ankr89.860024021,566
10LlamaNodes112.770024027,065
111RPC141.660024033,998
12Etherspot155.230024037,255
13BlockEden.xyz354.380024085,050
14OMNIA Protocol920.9200240221,020

Best Optimism Mainnet Public Endpoints for the Middle East and Africa

(3 AWS regions on January 19, 2024)

NoProviderAvg (ms)Failed429SuccessDuration (ms)
1Gateway.fm126.77009011,409
2thirdweb129.90009011,691
3Nodies143.44009012,910
4Tenderly147.41009013,267
5Optimism Foundation162.78009014,650
6Ankr168.80009015,192
7Blast API174.76009015,728
8Allnodes175.23009015,771
9BlockPI Network177.48009015,973
10LlamaNodes215.51009019,396
11Etherspot265.26009023,873
121RPC310.03009027,903
13BlockEden.xyz457.06009041,135
14OMNIA Protocol1087.47108996,785

Best Optimism Mainnet Public Endpoints for Asia

(8 AWS regions on January 19, 2024)

NoProviderAvg (ms)Failed429SuccessDuration (ms)
1Nodies72.330024017,360
2Ankr89.950024021,587
3thirdweb96.340024023,122
4BlockPI Network128.390024030,813
51RPC132.190024031,726
6Tenderly154.530024037,088
7LlamaNodes198.450024047,628
8Gateway.fm201.060024048,254
9Blast API201.900024048,455
10Allnodes263.680024063,284
11OMNIA Protocol273.350024065,605
12Optimism Foundation327.800024078,673
13BlockEden.xyz377.950024090,707
14Etherspot680.8700240163,408

Best Optimism Mainnet Public Endpoints for Australia

(2 AWS regions on January 19, 2024)

NoProviderAvg (ms)Failed429SuccessDuration (ms)
1Ankr84.4200605,065
2thirdweb102.3800606,143
3Nodies111.7300606,704
4Tenderly173.52006010,411
51RPC181.85006010,911
6BlockPI Network198.88006011,933
7LlamaNodes205.17006012,310
8Blast API217.75006013,065
9Allnodes290.27006017,416
10OMNIA Protocol294.15006017,649
11Gateway.fm302.8006018,168
12Optimism Foundation328.18006019,691
13BlockEden.xyz367.65006022,059
14Etherspot470.05006028,203

Overall Winner on January 19, 2024

Congratulations Nodies as the best public endpoint on Optimism mainnet (all endpoints).

Big shoutouts to continental leaders: Tenderly, thirdweb, Tenderly, Gateway.fm, Nodies, and Ankr.

Complete data for specific locations are in this sheet so additional kudos go out to:

  • LlamaNodes for their win in Ohio (note, they run directly from AWS Ohio);
  • 1RPC for their results from Hyderabad.

Yes, we realize that the population in South America is ten times greater than Australia yet we measure from both Sydney and Melbourne as opposed to Sao Paulo alone. Our goals are to improve by expanding locations in South America and adding continental multipliers proportional to their populations.

Indeed, it might appear that providers which also use AWS might have a significant advantage but we don’t think it had much impact. The IP data shows the following clouds & CDNs:

  • CLOUDFLARENET: Nodies, thirdweb, Ankr, Block PI Network, Blast API, Allnodes, BlockEden.xyz, Etherspot, OMNIA Protocol;
  • GOOGLE-CLOUD-PLATFORM: Tenderly and Optimism Foundation;
  • Cloudsigma Ag: Gateway.fm;
  • MICROSOFT-CORP-MSN-AS-BLOCK: 1RPC;
  • and only LlamaNodes is directly in AMAZON-02 with best result as No2 in North America; looks like they run from Ohio only, whereas we measure from 5 locations for that continent!

Raw Results

Follow us on:

John Doe
John Doe@username
Read More
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.
John Doe
John Doe@username
Read More
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.
John Doe
John Doe@username
Read More
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.
Previous
Next

Leave a Reply

Your email address will not be published. Required fields are marked *