Hive-Engine Node Benchmark Report - 2025-04-18
hive-engine·@nectarflower·
0.000 HBDHive-Engine Node Benchmark Report - 2025-04-18
# Full Hive-Engine API Node Update - (18/04/2025) 2025-04-18T17:00:04 (UTC) **Note:** This post is published from the @nectarflower account, but the benchmark data and nodee metadata are from the @flowerengine account. @nectarflower provides daily updates about the state of all available full API node servers for Hive-Engine. More information about nectarflower can be found in the [github repository](https://github.com/thecrazygm/nectarflower-bench). ## List of failing nodes This table includes a list of all nodes which were not able to answer to a `getStatus` API call within the specified timeout. |node | error | | --- | --- | | <https://herpc.meb.asia> | Not a valid hive-engine node: HTTPSConnectionPool(host='herpc.meb.asia', port=443): Max retries e... | | <https://herpc.cupidchat.net> | Not a valid hive-engine node: HTTPSConnectionPool(host='herpc.cupidchat.net', port=443): Max retr... | | <https://herpc.mmshare.net> | Not a valid hive-engine node: HTTPSConnectionPool(host='herpc.mmshare.net', port=443): Max retrie... | | <https://herpc.asiaworld.net> | Not a valid hive-engine node: HTTPSConnectionPool(host='herpc.asiaworld.net', port=443): Max retr... | | <https://herpc.tarwateinthar.com> | Not a valid hive-engine node: HTTPSConnectionPool(host='herpc.tarwateinthar.com', port=443): Max ... | ## List of working nodes (At least once) This table includes all nodes which were able to answer a `getStatus` call within the timeout. The achieved mean duration values are shown. The returned SSCnodeVersion is also shown. |node | mean time [s] | SSCnodeVersion | | --- | --- | --- | | <https://light.primersion.com> | 0.0 | ivm-1.0.0 | | <https://herpc.dtools.dev> | 0.0 | ivm-1.0.0 | | <https://heapi.c0ff33a.uk> | 0.0 | ivm-1.0.0 | | <https://api2.hive-engine.com/rpc> | 0.0 | ivm-1.0.0 | | <https://herpc.filoz.info> | 0.0 | ivm-1.0.0 | | <https://herpc.liotes.com> | 0.0 | ivm-1.0.0 | | <https://he.c0ff33a.uk> | 0.0 | ivm-1.0.0 | | <https://enginerpc.com> | 0.0 | ivm-1.0.0 | | <https://he.sourov.dev> | 0.0 | ivm-1.0.0 | | <https://api.hive-engine.com/rpc> | 0.0 | ivm-1.0.0 | | <https://he.atexoras.com:2083> | 0.0 | ivm-1.0.0 | | <https://herpc.actifit.io> | 0.0 | ivm-1.0.0 | | <https://herpc.kanibot.com> | 0.0 | ivm-1.0.0 | | <https://he.eturnerx.com> | 0.0 | ivm-1.0.0 | | <https://api.primersion.com> | 0.0 | ivm-1.0.0 | | <https://engine.hive.pizza> | 0.0 | ivm-1.0.0 | # Full Hive-Engine API Node Update - (18/04/2025) 2025-04-18T17:00:04 (UTC) **Note:** This post is published from the @nectarflower account, but the benchmark data and node metadata are from the @flowerengine account. @nectarflower provides daily updates about the state of all available full API node servers for Hive-Engine. More information about nectarflower can be found in the [github repository](https://github.com/thecrazygm/benchmarks). ## List of failing nodes This table includes a list of all nodes which were not able to answer to a `getStatus` API call within the specified timeout. |node | error | | --- | --- | | <https://herpc.meb.asia> | Not a valid hive-engine node: HTTPSConnectionPool(host='herpc.meb.asia', port=443): Max retries e... | | <https://herpc.cupidchat.net> | Not a valid hive-engine node: HTTPSConnectionPool(host='herpc.cupidchat.net', port=443): Max retr... | | <https://herpc.mmshare.net> | Not a valid hive-engine node: HTTPSConnectionPool(host='herpc.mmshare.net', port=443): Max retrie... | | <https://herpc.asiaworld.net> | Not a valid hive-engine node: HTTPSConnectionPool(host='herpc.asiaworld.net', port=443): Max retr... | | <https://herpc.tarwateinthar.com> | Not a valid hive-engine node: HTTPSConnectionPool(host='herpc.tarwateinthar.com', port=443): Max ... | ## List of working nodes (At least once) This table includes all nodes which were able to answer a `getStatus` call within the timeout. The achieved mean duration values are shown. The returned SSCnodeVersion is also shown. |node | mean time [s] | SSCnodeVersion | | --- | --- | --- | | <https://light.primersion.com> | 0.0 | ivm-1.0.0 | | <https://herpc.dtools.dev> | 0.0 | ivm-1.0.0 | | <https://heapi.c0ff33a.uk> | 0.0 | ivm-1.0.0 | | <https://api2.hive-engine.com/rpc> | 0.0 | ivm-1.0.0 | | <https://herpc.filoz.info> | 0.0 | ivm-1.0.0 | | <https://herpc.liotes.com> | 0.0 | ivm-1.0.0 | | <https://he.c0ff33a.uk> | 0.0 | ivm-1.0.0 | | <https://enginerpc.com> | 0.0 | ivm-1.0.0 | | <https://he.sourov.dev> | 0.0 | ivm-1.0.0 | | <https://api.hive-engine.com/rpc> | 0.0 | ivm-1.0.0 | | <https://he.atexoras.com:2083> | 0.0 | ivm-1.0.0 | | <https://herpc.actifit.io> | 0.0 | ivm-1.0.0 | | <https://herpc.kanibot.com> | 0.0 | ivm-1.0.0 | | <https://he.eturnerx.com> | 0.0 | ivm-1.0.0 | | <https://api.primersion.com> | 0.0 | ivm-1.0.0 | | <https://engine.hive.pizza> | 0.0 | ivm-1.0.0 | ## Node Uptime Statistics (7-day period) This table shows how reliable nodes have been over the past week. | node | uptime % | total checks | | --- | --- | --- | | <https://api.hive-engine.com/rpc> | 100.0% | 1 | | <https://api.primersion.com> | 100.0% | 1 | | <https://api2.hive-engine.com/rpc> | 100.0% | 1 | | <https://engine.hive.pizza> | 100.0% | 1 | | <https://enginerpc.com> | 100.0% | 1 | | <https://he.atexoras.com:2083> | 100.0% | 1 | | <https://he.c0ff33a.uk> | 100.0% | 1 | | <https://he.eturnerx.com> | 100.0% | 1 | | <https://he.sourov.dev> | 100.0% | 1 | | <https://heapi.c0ff33a.uk> | 100.0% | 1 | | <https://herpc.actifit.io> | 100.0% | 1 | | <https://herpc.dtools.dev> | 100.0% | 1 | | <https://herpc.filoz.info> | 100.0% | 1 | | <https://herpc.kanibot.com> | 100.0% | 1 | | <https://herpc.liotes.com> | 100.0% | 1 | | <https://light.primersion.com> | 100.0% | 1 | | <https://herpc.asiaworld.net> | 50.0% | 2 | | <https://herpc.cupidchat.net> | 50.0% | 2 | | <https://herpc.meb.asia> | 50.0% | 2 | | <https://herpc.mmshare.net> | 50.0% | 2 | | <https://herpc.tarwateinthar.com> | 50.0% | 2 | ## Token retrieval This table shows how many token operations were processed by the node within the specified time. The nodes are ordered according to the number of operations processed. | node | operations processed | operations per second | | --- | --- | --- | | <https://herpc.filoz.info> | 3414 | 113.8 | | <https://herpc.actifit.io> | 935 | 31.15 | | <https://engine.hive.pizza> | 806 | 26.85 | | <https://heapi.c0ff33a.uk> | 647 | 21.54 | | <https://he.c0ff33a.uk> | 642 | 21.4 | | <https://herpc.liotes.com> | 617 | 20.55 | | <https://herpc.kanibot.com> | 433 | 14.39 | | <https://enginerpc.com> | 109 | 16.47 | | <https://api.primersion.com> | 88 | 56.73 | | <https://he.atexoras.com:2083> | 85 | 2.82 | | <https://light.primersion.com> | 59 | 23.14 | | <https://he.sourov.dev> | 52 | 29.65 | | <https://he.eturnerx.com> | 38 | 12.3 | | <https://api2.hive-engine.com/rpc> | 15 | 6.17 | | <https://api.hive-engine.com/rpc> | 14 | 6.47 | | <https://herpc.dtools.dev> | 13 | 31.97 | ## Contract operations This table shows how many contract operations were processed by the node within the specified time. The nodes are ordered according to the number of operations processed. | node | operations processed | operations per second | | --- | --- | --- | | <https://herpc.filoz.info> | 3163 | 105.41 | | <https://herpc.actifit.io> | 823 | 27.41 | | <https://engine.hive.pizza> | 757 | 25.21 | | <https://he.c0ff33a.uk> | 738 | 24.59 | | <https://heapi.c0ff33a.uk> | 733 | 24.4 | | <https://herpc.liotes.com> | 612 | 20.37 | | <https://herpc.kanibot.com> | 401 | 13.37 | | <https://enginerpc.com> | 97 | 18.14 | | <https://he.atexoras.com:2083> | 94 | 3.12 | | <https://he.sourov.dev> | 52 | 37.78 | | <https://he.eturnerx.com> | 27 | 15.67 | | <https://api.hive-engine.com/rpc> | 14 | 7.18 | | <https://api2.hive-engine.com/rpc> | 14 | 8.08 | | <https://herpc.dtools.dev> | 12 | 34.32 | ## Account history operations This table shows how many account history operations were processed by the node within the specified time. The nodes are ordered according to the number of operations processed. | node | operations processed | operations per second | | --- | --- | --- | | <https://herpc.kanibot.com> | 116 | 3.84 | | <https://herpc.filoz.info> | 19 | 1.77 | | <https://api.hive-engine.com/rpc> | 11 | 1.49 | | <https://engine.hive.pizza> | 3 | 0.75 | | <https://herpc.mmshare.net> | 2 | 0.71 | | <https://he.sourov.dev> | 2 | 0.81 | | <https://herpc.tarwateinthar.com> | 2 | 0.68 | | <https://enginerpc.com> | 2 | 1.01 | | <https://herpc.meb.asia> | 1 | 0.55 | | <https://api.primersion.com> | 1 | 0.51 | | <https://herpc.dtools.dev> | 1 | 0.55 | | <https://herpc.cupidchat.net> | 1 | 0.54 | | <https://herpc.asiaworld.net> | 1 | 0.55 | | <https://herpc.actifit.io> | 1 | 0.53 | | <https://api2.hive-engine.com/rpc> | 1 | 0.54 | | <https://he.c0ff33a.uk> | 1 | 0.5 | | <https://he.eturnerx.com> | 1 | 0.51 | | <https://heapi.c0ff33a.uk> | 1 | 0.55 | | <https://light.primersion.com> | 1 | 0.54 | | <https://herpc.liotes.com> | 1 | 0.55 | | <https://he.atexoras.com:2083> | 1 | 0.51 | ## Latency This table shows the latency measurements for each node. The nodes are ordered according to average latency (lowest first). | node | avg latency [s] | min latency [s] | max latency [s] | | --- | --- | --- | --- | | <https://herpc.filoz.info> | 0.03 | 0.01 | 0.05 | | <https://herpc.dtools.dev> | 0.04 | 0.01 | 0.07 | | <https://api.primersion.com> | 0.05 | 0.02 | 0.1 | | <https://light.primersion.com> | 0.06 | 0.04 | 0.09 | | <https://herpc.actifit.io> | 0.06 | 0.05 | 0.08 | | <https://he.sourov.dev> | 0.06 | 0.05 | 0.1 | | <https://engine.hive.pizza> | 0.1 | 0.05 | 0.13 | | <https://enginerpc.com> | 0.1 | 0.08 | 0.13 | | <https://herpc.kanibot.com> | 0.1 | 0.04 | 0.15 | | <https://api.hive-engine.com/rpc> | 0.11 | 0.04 | 0.15 | | <https://he.eturnerx.com> | 0.12 | 0.1 | 0.13 | | <https://api2.hive-engine.com/rpc> | 0.12 | 0.05 | 0.15 | | <https://he.c0ff33a.uk> | 0.12 | 0.04 | 0.17 | | <https://herpc.liotes.com> | 0.12 | 0.05 | 0.16 | | <https://heapi.c0ff33a.uk> | 0.13 | 0.05 | 0.16 | | <https://he.atexoras.com:2083> | 0.67 | 0.3 | 1.19 | ## Node Trends and Reliability The following data shows trends over the past 7 days: ### Node Uptime | Node | Uptime % | Total Runs | | --- | --- | --- | | <https://api.hive-engine.com/rpc> | 100.0% | 1 | | <https://api.primersion.com> | 100.0% | 1 | | <https://api2.hive-engine.com/rpc> | 100.0% | 1 | | <https://engine.hive.pizza> | 100.0% | 1 | | <https://enginerpc.com> | 100.0% | 1 | | <https://he.atexoras.com:2083> | 100.0% | 1 | | <https://he.c0ff33a.uk> | 100.0% | 1 | | <https://he.eturnerx.com> | 100.0% | 1 | | <https://he.sourov.dev> | 100.0% | 1 | | <https://heapi.c0ff33a.uk> | 100.0% | 1 | | <https://herpc.actifit.io> | 100.0% | 1 | | <https://herpc.dtools.dev> | 100.0% | 1 | | <https://herpc.filoz.info> | 100.0% | 1 | | <https://herpc.kanibot.com> | 100.0% | 1 | | <https://herpc.liotes.com> | 100.0% | 1 | ### Notable Trends No significant trends detected in the past 7 days. ## Node Consistency This section shows how consistent each node's performance has been. Lower standard deviation indicates more consistent performance. | Node | Consistency Score (lower is better) | | --- | --- | ## Conclusion This report provides a snapshot of Hive-Engine node performance. Users can use this information to select reliable nodes for their applications. The benchmark data is also available in JSON format in the @flowerengine account's `json_metadata` for automated processing. --- Generated by the engine-bench tool.
👍 sbi3, sbi-tokens, teamvn, noloafing, sneakyninja, thedailysneak, babysavage, ravensavage, sbi-booster, forykw, forkyishere, ecoinstant, fatman, voter002, tomiscurious, votehero, eturnerx-dbuzz, cryptoknight12, jozefkrichards, kernelillo, onewolfe, hivedrip, dpend.active, sketching, mxm0unite, thorlock, mighty-thor, splinterwhale, tipu, kryptogames, dappstats, sabajfa, mukadder, soyernesto, cryptogambit, longer, c0ff33a, blue.panda, whiterosecoffee, the.lazy.panda, teamuksupport, fazendadolobo, cryptosneeze, tommys.shop, leighscotford,