OnFinality vs. POKT Network on Fantom Mainnet

GLOBAL NODE COMPARISON

Independent and transparent RPC performance comparison results

Data captured on (Sun, 04 Feb 2024 20:25:03 GMT UTC)

Better Overall Latency: Inconclusive Results

We could not collect sufficient data required to compute the global node comparison.
One of our conditions is that each provider must return more responses in every region than failed requests.
To learn more, please scroll and review the details below.

Results represent a comparison at a point in time using eth_blockNumber RPC method and WITH throttling — each regional probe sent its requests synchronously, after it received the previous response but not sooner than 1 second since the previous dispatch.

You can share a page link for these results. Note that the providers make frequent changes to their infrastructure. Therefore, we recommend additional similar comparisons which can be performed using our public Performance Inspector app for blockchain nodes .

Summary

Continent Provider Endpoint Avg (ms) ChainID Failed 429 Success Duration (ms)
N.America
A. OnFinality
onfinality.io 74.27 250 0 5 30 2,228
N.America
B. POKT Network
nodies.app 55.68 250 0 0 150 8,352
S.America
A. OnFinality
onfinality.io 187.43 250 0 1 7 1,312
S.America
B. POKT Network
nodies.app 125.63 250 0 0 30 3,769
ME & Africa
A. OnFinality
onfinality.io 241.39 250 0 3 28 6,759
ME & Africa
B. POKT Network
nodies.app 150.47 250 0 0 90 13,542
Asia
A. OnFinality
onfinality.io 92.76 250 0 8 80 7,421
Asia
B. POKT Network
nodies.app 231.87 250 0 0 240 55,649
Australia
A. OnFinality
onfinality.io 120.15 250 0 2 20 2,403
Australia
B. POKT Network
nodies.app 278.60 250 0 0 60 16,716

All 27 Regions: Details

Continent AWS Region Provider Endpoint Avg (ms) Failed 429 1st Best Worst Success Duration (ms) IP ChainID
N.America N. California
A. OnFinality
onfinality.io 115.17 0 1 85 84/no.6 178/no.2 6 691 142.215.53.42 250
N.America N. California
B. POKT Network
nodies.app 79.20 0 0 87 77/no.11 87/no.1 30 2,376 172.67.70.207 250
N.America Oregon
A. OnFinality
onfinality.io 105.80 0 1 103 102/no.4 116/no.2 5 529 142.215.53.42 250
N.America Oregon
B. POKT Network
nodies.app 78.40 0 0 77 74/no.26 87/no.2 30 2,352 172.67.70.207 250
N.America Ohio
A. OnFinality
onfinality.io 71.88 0 1 131 33/no.2 137/no.7 8 575 142.215.53.42 250
N.America Ohio
B. POKT Network
nodies.app 43.53 0 0 38 37/no.11 69/no.18 30 1,306 172.67.70.207 250
N.America Montreal
A. OnFinality
onfinality.io 47.50 0 1 78 35/no.4 78/no.1 4 190 142.215.53.42 250
N.America Montreal
B. POKT Network
nodies.app 58.10 0 0 58 55/no.3 62/no.26 30 1,743 104.26.4.88 250
N.America N. Virginia
A. OnFinality
onfinality.io 34.71 0 1 23 18/no.4 110/no.3 7 243 142.215.53.42 250
N.America N. Virginia
B. POKT Network
nodies.app 19.17 0 0 18 16/no.25 28/no.14 30 575 104.26.5.88 250
S.America São Paulo
A. OnFinality
onfinality.io 187.43 0 1 147 147/no.1 239/no.6 7 1,312 142.215.53.42 250
S.America São Paulo
B. POKT Network
nodies.app 125.63 0 0 134 122/no.3 138/no.23 30 3,769 104.26.5.88 250
Europe Ireland
A. OnFinality
onfinality.io 127.71 0 1 128 110/no.6 201/no.5 7 894 142.215.53.42 250
Europe Ireland
B. POKT Network
nodies.app 52.27 0 0 46 44/no.29 76/no.19 30 1,568 104.26.5.88 250
Europe London
A. OnFinality
onfinality.io 120.67 0 1 106 103/no.2 198/no.6 6 724 142.215.53.42 250
Europe London
B. POKT Network
nodies.app 43.17 0 0 103 35/no.21 103/no.1 30 1,295 104.26.4.88 250
Europe Spain
A. OnFinality
onfinality.io 118.86 0 1 119 115/no.5 125/no.6 7 832 142.215.53.42 250
Europe Spain
B. POKT Network
nodies.app 57.40 0 0 52 50/no.5 69/no.9 30 1,722 104.26.4.88 250
Europe Paris
A. OnFinality
onfinality.io 124.86 0 1 98 97/no.2 191/no.7 7 874 142.215.53.42 250
Europe Paris
B. POKT Network
nodies.app 39.20 0 0 34 33/no.13 53/no.17 30 1,176 104.26.5.88 250
Europe Frankfurt
A. OnFinality
onfinality.io 108.00 0 1 110 106/no.2 110/no.1 7 756 142.215.53.42 250
Europe Frankfurt
B. POKT Network
nodies.app 0.00 0 1 - - - 0 0 104.26.5.88 250
Europe Stockholm
A. OnFinality
onfinality.io 120.20 0 1 120 119/no.4 121/no.2 5 601 142.215.53.42 250
Europe Stockholm
B. POKT Network
nodies.app 49.57 0 0 50 46/no.18 58/no.17 30 1,487 104.26.5.88 250
Europe Zurich
A. OnFinality
onfinality.io 145.29 0 1 208 117/no.7 208/no.1 7 1,017 142.215.53.42 250
Europe Zurich
B. POKT Network
nodies.app 49.97 0 0 50 41/no.18 69/no.3 30 1,499 172.67.70.207 250
Europe Milan
A. OnFinality
onfinality.io 117.20 0 1 116 113/no.4 125/no.3 5 586 142.215.53.42 250
Europe Milan
B. POKT Network
nodies.app 42.83 0 0 41 36/no.13 68/no.4 30 1,285 104.26.5.88 250
ME & Africa Cape Town
A. OnFinality
onfinality.io 272.25 0 1 258 256/no.8 360/no.7 8 2,178 142.215.53.42 250
ME & Africa Cape Town
B. POKT Network
nodies.app 177.40 0 0 176 170/no.8 214/no.2 30 5,322 172.67.70.207 250
ME & Africa Bahrain
A. OnFinality
onfinality.io 218.60 0 1 185 185/no.1 349/no.2 10 2,186 8.219.75.68 250
ME & Africa Bahrain
B. POKT Network
nodies.app 125.27 0 0 142 119/no.3 142/no.1 30 3,758 172.67.70.207 250
ME & Africa UAE
A. OnFinality
onfinality.io 239.50 0 1 362 198/no.3 362/no.1 10 2,395 8.219.75.68 250
ME & Africa UAE
B. POKT Network
nodies.app 148.73 0 0 142 136/no.21 247/no.9 30 4,462 104.26.4.88 250
Asia Mumbai
A. OnFinality
onfinality.io 123.30 0 1 91 76/no.5 303/no.3 10 1,233 8.219.75.68 250
Asia Mumbai
B. POKT Network
nodies.app 239.00 0 0 249 228/no.15 258/no.5 30 7,170 104.26.4.88 250
Asia Hyderabad
A. OnFinality
onfinality.io 77.50 0 1 60 60/no.1 226/no.6 10 775 8.219.75.68 250
Asia Hyderabad
B. POKT Network
nodies.app 225.53 0 0 220 217/no.11 243/no.22 30 6,766 104.26.5.88 250
Asia Singapore
A. OnFinality
onfinality.io 42.60 0 1 21 18/no.3 244/no.10 10 426 8.219.75.68 250
Asia Singapore
B. POKT Network
nodies.app 180.13 0 0 192 167/no.19 236/no.11 30 5,404 104.26.5.88 250
Asia Jakarta
A. OnFinality
onfinality.io 57.00 0 1 33 32/no.3 260/no.9 10 570 8.219.75.68 250
Asia Jakarta
B. POKT Network
nodies.app 193.37 0 0 185 183/no.17 212/no.2 30 5,801 172.67.70.207 250
Asia Hong Kong
A. OnFinality
onfinality.io 95.80 0 1 50 49/no.3 277/no.6 10 958 8.219.75.68 250
Asia Hong Kong
B. POKT Network
nodies.app 211.37 0 0 206 201/no.10 226/no.4 30 6,341 104.26.5.88 250
Asia Seoul
A. OnFinality
onfinality.io 143.00 0 1 87 83/no.4 312/no.2 10 1,430 8.219.75.68 250
Asia Seoul
B. POKT Network
nodies.app 294.00 0 0 296 284/no.5 307/no.3 30 8,820 104.26.4.88 250
Asia Osaka
A. OnFinality
onfinality.io 97.50 0 1 97 95/no.4 111/no.10 10 975 8.219.75.68 250
Asia Osaka
B. POKT Network
nodies.app 262.57 0 0 257 252/no.4 278/no.24 30 7,877 104.26.5.88 250
Asia Tokyo
A. OnFinality
onfinality.io 105.40 0 1 89 88/no.3 252/no.10 10 1,054 8.219.75.68 250
Asia Tokyo
B. POKT Network
nodies.app 249.00 0 0 244 238/no.6 264/no.18 30 7,470 172.67.70.207 250
Australia Melbourne
A. OnFinality
onfinality.io 122.60 0 1 123 121/no.4 124/no.7 10 1,226 8.219.75.68 250
Australia Melbourne
B. POKT Network
nodies.app 282.93 0 0 277 273/no.25 301/no.28 30 8,488 104.26.5.88 250
Australia Sydney
A. OnFinality
onfinality.io 117.70 0 1 111 110/no.6 167/no.3 10 1,177 8.219.75.68 250
Australia Sydney
B. POKT Network
nodies.app 274.27 0 0 264 263/no.9 289/no.7 30 8,228 104.26.5.88 250

Total Logs: 28

AWS Region Provider UTC Timestamp Message (showing up to 4 logs for each provider in a region)
N. California A. OnFinality 2/4/2024, 20:24:31.902 UTC Error (429) on request no.7: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Oregon A. OnFinality 2/4/2024, 20:24:29.955 UTC Error (429) on request no.6: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Ohio A. OnFinality 2/4/2024, 20:24:32.551 UTC Error (429) on request no.9: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Montreal A. OnFinality 2/4/2024, 20:24:28.594 UTC Error (429) on request no.5: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
N. Virginia A. OnFinality 2/4/2024, 20:24:31.508 UTC Error (429) on request no.8: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
São Paulo A. OnFinality 2/4/2024, 20:24:32.251 UTC Error (429) on request no.8: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Ireland A. OnFinality 2/4/2024, 20:24:31.992 UTC Error (429) on request no.8: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
London A. OnFinality 2/4/2024, 20:24:30.994 UTC Error (429) on request no.7: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Spain A. OnFinality 2/4/2024, 20:24:32.182 UTC Error (429) on request no.8: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Paris A. OnFinality 2/4/2024, 20:24:32.035 UTC Error (429) on request no.8: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Frankfurt A. OnFinality 2/4/2024, 20:24:32.048 UTC Error (429) on request no.8: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Frankfurt B. POKT Network 2/4/2024, 20:24:24.824 UTC Error (429) on request no.1: {"error":{}}
Stockholm A. OnFinality 2/4/2024, 20:24:30.153 UTC Error (429) on request no.6: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Zurich A. OnFinality 2/4/2024, 20:24:32.176 UTC Error (429) on request no.8: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Milan A. OnFinality 2/4/2024, 20:24:30.146 UTC Error (429) on request no.6: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Cape Town A. OnFinality 2/4/2024, 20:24:34.160 UTC Error (429) on request no.9: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Bahrain A. OnFinality 2/4/2024, 20:24:35.725 UTC Error (429) on request no.11: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
UAE A. OnFinality 2/4/2024, 20:24:35.963 UTC Error (429) on request no.11: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Mumbai A. OnFinality 2/4/2024, 20:24:35.481 UTC Error (429) on request no.11: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Hyderabad A. OnFinality 2/4/2024, 20:24:35.531 UTC Error (429) on request no.11: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Singapore A. OnFinality 2/4/2024, 20:24:35.659 UTC Error (429) on request no.11: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Jakarta A. OnFinality 2/4/2024, 20:24:35.545 UTC Error (429) on request no.11: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Hong Kong A. OnFinality 2/4/2024, 20:24:35.336 UTC Error (429) on request no.11: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Seoul A. OnFinality 2/4/2024, 20:24:35.406 UTC Error (429) on request no.11: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Osaka A. OnFinality 2/4/2024, 20:24:35.469 UTC Error (429) on request no.11: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Tokyo A. OnFinality 2/4/2024, 20:24:35.526 UTC Error (429) on request no.11: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Melbourne A. OnFinality 2/4/2024, 20:24:35.568 UTC Error (429) on request no.11: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}
Sydney A. OnFinality 2/4/2024, 20:24:35.594 UTC Error (429) on request no.11: {"error":{"message":"Too Many Requests, Please apply an OnFinality API key or contact us to receive a higher rate limit","code":-32029}}