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:27:18 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 77.60 250 0 5 30 2,328
N.America
B. POKT Network
nodies.app 55.07 250 0 0 150 8,260
S.America
A. OnFinality
onfinality.io 201.25 250 0 1 4 805
S.America
B. POKT Network
nodies.app 133.07 250 0 0 30 3,992
ME & Africa
A. OnFinality
onfinality.io 219.12 250 0 3 26 5,697
ME & Africa
B. POKT Network
nodies.app 148.84 250 0 0 90 13,396
Asia
A. OnFinality
onfinality.io 94.75 250 0 8 80 7,580
Asia
B. POKT Network
nodies.app 232.88 250 0 0 240 55,890
Australia
A. OnFinality
onfinality.io 129.50 250 0 2 20 2,590
Australia
B. POKT Network
nodies.app 277.17 250 0 0 60 16,630

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 100.71 0 1 87 81/no.4 180/no.7 7 705 142.215.53.42 250
N.America N. California
B. POKT Network
nodies.app 78.40 0 0 79 76/no.16 81/no.12 30 2,352 172.67.70.207 250
N.America Oregon
A. OnFinality
onfinality.io 116.40 0 1 98 94/no.4 193/no.3 5 582 142.215.53.42 250
N.America Oregon
B. POKT Network
nodies.app 82.80 0 0 82 78/no.5 93/no.19 30 2,484 104.26.5.88 250
N.America Ohio
A. OnFinality
onfinality.io 58.29 0 1 26 26/no.1 121/no.2 7 408 142.215.53.42 250
N.America Ohio
B. POKT Network
nodies.app 38.83 0 0 38 36/no.5 49/no.9 30 1,165 104.26.4.88 250
N.America Montreal
A. OnFinality
onfinality.io 57.17 0 1 32 32/no.1 125/no.5 6 343 142.215.53.42 250
N.America Montreal
B. POKT Network
nodies.app 55.70 0 0 56 54/no.3 59/no.8 30 1,671 104.26.5.88 250
N.America N. Virginia
A. OnFinality
onfinality.io 58.00 0 1 114 18/no.4 114/no.1 5 290 142.215.53.42 250
N.America N. Virginia
B. POKT Network
nodies.app 19.60 0 0 17 16/no.4 30/no.15 30 588 172.67.70.207 250
S.America São Paulo
A. OnFinality
onfinality.io 201.25 0 1 149 149/no.1 262/no.4 4 805 142.215.53.42 250
S.America São Paulo
B. POKT Network
nodies.app 133.07 0 0 132 130/no.16 141/no.28 30 3,992 172.67.70.207 250
Europe Ireland
A. OnFinality
onfinality.io 119.25 0 1 114 114/no.1 124/no.2 4 477 142.215.53.42 250
Europe Ireland
B. POKT Network
nodies.app 46.07 0 0 45 41/no.18 56/no.17 30 1,382 104.26.4.88 250
Europe London
A. OnFinality
onfinality.io 120.00 0 1 104 98/no.2 191/no.3 5 600 142.215.53.42 250
Europe London
B. POKT Network
nodies.app 43.00 0 0 41 36/no.21 63/no.14 30 1,290 104.26.4.88 250
Europe Spain
A. OnFinality
onfinality.io 139.50 0 1 220 120/no.4 220/no.1 6 837 142.215.53.42 250
Europe Spain
B. POKT Network
nodies.app 71.73 0 0 70 65/no.18 84/no.20 30 2,152 172.67.70.207 250
Europe Paris
A. OnFinality
onfinality.io 106.50 0 1 106 103/no.3 112/no.2 4 426 142.215.53.42 250
Europe Paris
B. POKT Network
nodies.app 34.03 0 0 36 27/no.11 57/no.17 30 1,021 172.67.70.207 250
Europe Frankfurt
A. OnFinality
onfinality.io 112.75 0 1 115 110/no.4 115/no.1 4 451 142.215.53.42 250
Europe Frankfurt
B. POKT Network
nodies.app 0.00 0 1 - - - 0 0 104.26.4.88 250
Europe Stockholm
A. OnFinality
onfinality.io 166.67 0 1 214 117/no.6 215/no.3 6 1,000 142.215.53.42 250
Europe Stockholm
B. POKT Network
nodies.app 51.87 0 0 48 46/no.18 114/no.13 30 1,556 104.26.4.88 250
Europe Zurich
A. OnFinality
onfinality.io 154.60 0 1 116 116/no.1 210/no.4 5 773 142.215.53.42 250
Europe Zurich
B. POKT Network
nodies.app 47.87 0 0 46 42/no.2 60/no.28 30 1,436 104.26.4.88 250
Europe Milan
A. OnFinality
onfinality.io 119.60 0 1 120 117/no.5 122/no.4 5 598 142.215.53.42 250
Europe Milan
B. POKT Network
nodies.app 52.17 0 0 44 43/no.16 79/no.9 30 1,565 172.67.70.207 250
ME & Africa Cape Town
A. OnFinality
onfinality.io 294.17 0 1 257 257/no.1 374/no.4 6 1,765 142.215.53.42 250
ME & Africa Cape Town
B. POKT Network
nodies.app 177.37 0 0 183 173/no.8 192/no.21 30 5,321 104.26.4.88 250
ME & Africa Bahrain
A. OnFinality
onfinality.io 179.70 0 1 181 177/no.5 183/no.2 10 1,797 8.219.75.68 250
ME & Africa Bahrain
B. POKT Network
nodies.app 127.87 0 0 121 117/no.9 161/no.5 30 3,836 104.26.4.88 250
ME & Africa UAE
A. OnFinality
onfinality.io 213.50 0 1 190 189/no.6 415/no.2 10 2,135 8.219.75.68 250
ME & Africa UAE
B. POKT Network
nodies.app 141.30 0 0 133 133/no.1 161/no.28 30 4,239 104.26.5.88 250
Asia Mumbai
A. OnFinality
onfinality.io 121.30 0 1 76 74/no.8 301/no.4 10 1,213 8.219.75.68 250
Asia Mumbai
B. POKT Network
nodies.app 245.97 0 0 263 234/no.3 263/no.1 30 7,379 104.26.5.88 250
Asia Hyderabad
A. OnFinality
onfinality.io 84.80 0 1 61 61/no.1 290/no.3 10 848 8.219.75.68 250
Asia Hyderabad
B. POKT Network
nodies.app 226.47 0 0 220 218/no.29 242/no.5 30 6,794 104.26.4.88 250
Asia Singapore
A. OnFinality
onfinality.io 65.00 0 1 20 19/no.2 248/no.6 10 650 8.219.75.68 250
Asia Singapore
B. POKT Network
nodies.app 179.00 0 0 168 167/no.23 196/no.18 30 5,370 104.26.4.88 250
Asia Jakarta
A. OnFinality
onfinality.io 54.60 0 1 31 30/no.3 262/no.2 10 546 8.219.75.68 250
Asia Jakarta
B. POKT Network
nodies.app 192.77 0 0 191 183/no.21 209/no.24 30 5,783 104.26.5.88 250
Asia Hong Kong
A. OnFinality
onfinality.io 51.40 0 1 53 50/no.5 54/no.8 10 514 8.219.75.68 250
Asia Hong Kong
B. POKT Network
nodies.app 215.60 0 0 217 202/no.25 233/no.3 30 6,468 104.26.5.88 250
Asia Seoul
A. OnFinality
onfinality.io 107.50 0 1 86 86/no.1 290/no.8 10 1,075 8.219.75.68 250
Asia Seoul
B. POKT Network
nodies.app 292.20 0 0 295 280/no.10 314/no.6 30 8,766 104.26.4.88 250
Asia Osaka
A. OnFinality
onfinality.io 144.20 0 1 96 95/no.2 337/no.9 10 1,442 8.219.75.68 250
Asia Osaka
B. POKT Network
nodies.app 261.17 0 0 273 251/no.2 278/no.3 30 7,835 172.67.70.207 250
Asia Tokyo
A. OnFinality
onfinality.io 129.20 0 1 258 88/no.6 313/no.8 10 1,292 8.219.75.68 250
Asia Tokyo
B. POKT Network
nodies.app 249.83 0 0 239 239/no.1 319/no.28 30 7,495 104.26.4.88 250
Australia Melbourne
A. OnFinality
onfinality.io 145.50 0 1 123 121/no.9 348/no.8 10 1,455 8.219.75.68 250
Australia Melbourne
B. POKT Network
nodies.app 282.93 0 0 283 271/no.3 300/no.16 30 8,488 104.26.4.88 250
Australia Sydney
A. OnFinality
onfinality.io 113.50 0 1 112 111/no.2 124/no.3 10 1,135 8.219.75.68 250
Australia Sydney
B. POKT Network
nodies.app 271.40 0 0 265 260/no.24 292/no.2 30 8,142 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:26:50.882 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}}
Oregon A. OnFinality 2/4/2024, 20:26:49.051 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:26:50.562 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}}
Montreal A. OnFinality 2/4/2024, 20:26:49.624 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}}
N. Virginia A. OnFinality 2/4/2024, 20:26:48.513 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}}
São Paulo A. OnFinality 2/4/2024, 20:26:48.583 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}}
Ireland A. OnFinality 2/4/2024, 20:26:48.104 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}}
London A. OnFinality 2/4/2024, 20:26:48.988 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}}
Spain A. OnFinality 2/4/2024, 20:26:50.357 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}}
Paris A. OnFinality 2/4/2024, 20:26:48.038 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}}
Frankfurt A. OnFinality 2/4/2024, 20:26:48.161 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}}
Frankfurt B. POKT Network 2/4/2024, 20:26:43.817 UTC Error (429) on request no.1: {"error":{}}
Stockholm A. OnFinality 2/4/2024, 20:26:50.184 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}}
Zurich A. OnFinality 2/4/2024, 20:26:49.100 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}}
Milan A. OnFinality 2/4/2024, 20:26:49.132 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:26:51.235 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}}
Bahrain A. OnFinality 2/4/2024, 20:26:54.669 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:26:54.908 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:26:54.697 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:26:54.541 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:26:54.417 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:26:54.511 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:26:54.395 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:26:54.498 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:26:54.607 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:26:54.342 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:26:54.813 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:26:54.547 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}}