Full Hive API Node Update - (12/05/2025)

nectarflower(51)
Published in
#hive
Words
738
Reading
4 min
1y
Listen to this post
~5 min

Full Hive API Node Update - (12/05/2025)

2025-05-12T11:00:05 (UTC)
Benchmarks are performed from a Digital Ocean Droplet in Frankfurt, Germany. Results may vary based on geographic location.

nectarflower@nectarflower provides daily updates about the state of all available full API node servers for Hive.
More information about nectarflower can be found in the github repository.

List of failing nodes

This table includes a list of all nodes which were not able to answer to a get_config API call within the specified timeout (default: 60 seconds).

nodeerror
https://api.hive.blueNumRetriesReached
https://rpc.ausbit.devNumRetriesReached
https://hived.emre.shNumRetriesReached
https://hive.roelandp.nlUnexpected response format: {'message': 'Internal Server Error'}
https://api.openhive.networkClient returned invalid format. Expected JSON!

List of working nodes (At least once)

This table includes all nodes which were able to answer a get_config call within the timeout (default: 60 seconds). The achieved mean duration values are shown. The returned version is also shown.

nodemean time [s]version
https://hive-api.3speak.tv0.011.27.5
https://api.deathwing.me0.021.27.5
https://rpc.mahdiyari.info0.031.27.10
https://hive-api.dlux.io0.051.27.8
https://hiveapi.actifit.io0.051.27.8
https://api.c0ff33a.uk0.051.27.5
https://hive-api.arcange.eu0.071.27.5
https://api.openhive.network0.081.27.8
https://api.hive.blog0.11.27.11
https://anyx.io0.11.27.4
https://api.syncad.com0.131.27.11
https://techcoderx.com0.191.27.11
https://hive.roelandp.nl0.551.27.4

Node Uptime Statistics (7-day period)

This table shows how reliable nodes have been over the past week.

nodeuptime %total checks
https://api.c0ff33a.uk100.0%168
https://api.deathwing.me100.0%168
https://api.hive.blog100.0%168
https://hive-api.arcange.eu100.0%168
https://hiveapi.actifit.io100.0%168
https://techcoderx.com100.0%168
https://hive-api.3speak.tv98.25%171
https://api.syncad.com91.8%183
https://anyx.io84.85%198
https://rpc.mahdiyari.info77.78%216
https://hive-api.dlux.io72.1%233
https://api.hive.blue50.0%336
https://api.openhive.network50.0%336
https://hive.roelandp.nl50.0%336
https://hived.emre.sh50.0%336
https://rpc.ausbit.dev50.0%336

Streaming blocks

This table shows how many blocks were streamed by the node within the default benchmark duration (30 seconds). The RPCs are ordered according to the number of blocks streamed.

nodeblocks streamedblocks per second
https://hive-api.3speak.tv37612.53
https://hive-api.dlux.io37612.52
https://api.deathwing.me2508.33
https://rpc.mahdiyari.info2498.28
https://hiveapi.actifit.io2327.72
https://api.c0ff33a.uk2177.23
https://hive-api.arcange.eu1755.81
https://anyx.io1003.33
https://api.hive.blog571.88
https://api.syncad.com481.59
https://techcoderx.com471.55

Streaming account history

This table shows how many account history operations were streamed by the node within the default benchmark duration (60 seconds). The RPCs are ordered according to the number of operations streamed.

nodeoperations streamedoperations per second
https://api.hive.blog2878197.39
https://hive-api.3speak.tv2877363.26
https://api.deathwing.me2877292.97
https://rpc.mahdiyari.info2877328.42
https://hive-api.dlux.io2877376.57
https://hiveapi.actifit.io2877297.52
https://api.c0ff33a.uk2877291.49
https://hive-api.arcange.eu2877252.81
https://api.openhive.network2877230.16
https://anyx.io2877176.83
https://techcoderx.com2877188.78
https://api.syncad.com280192.75

API call time

This table shows how long it took to call an API (single request, default timeout: 60 seconds). The RPCs are ordered according to the access time.

noderesponse time [s]
https://hive-api.3speak.tv0.04
https://api.deathwing.me0.1
https://hive-api.dlux.io0.1
https://rpc.mahdiyari.info0.12
https://hiveapi.actifit.io0.12
https://api.c0ff33a.uk0.17
https://hive-api.arcange.eu0.18
https://api.openhive.network0.2
https://api.hive.blog0.21
https://api.syncad.com0.27
https://techcoderx.com0.42

Block difference

This table shows the head blocks reported by each node. By comparing with the highest one, we can tell if a node has issues with block processing.

nodeblocks behindhead blocks behind irreversible
https://api.hive.blog00
https://techcoderx.com00
https://hive-api.3speak.tv20
https://api.c0ff33a.uk20
https://api.deathwing.me20
https://hive-api.dlux.io20
https://api.openhive.network20
https://hive-api.arcange.eu20
https://rpc.mahdiyari.info20
https://hiveapi.actifit.io20
https://api.syncad.com20
https://anyx.io20
https://hive.roelandp.nl30

Node Performance Trends (7-day period)

This table shows how node performance has changed over the past week.

nodeblock trendhistory trendAPI call trendconfig trendblock diff trend
https://anyx.io✓ stable✓ stable✗ failingn/an/a
https://api.c0ff33a.ukn/an/an/a✓ stable↗ improving
https://api.deathwing.me✓ stablen/an/a✓ stable✓ stable
https://api.hive.blogn/a✓ stablen/a✓ stable✓ stable
https://api.hive.bluen/an/a✗ failingn/a↗ improving
https://api.openhive.network✗ failingn/a✓ stablen/a↗ improving
https://api.syncad.com✓ stablen/an/a✓ stablen/a
https://hive-api.3speak.tvn/an/a✓ stable↗ improving✓ stable
https://hive-api.arcange.eun/an/an/a✓ stablen/a
https://hive-api.dlux.io↗ improving↗ improving↗ improvingn/an/a
https://hive.roelandp.nl✗ failing✗ failingn/an/an/a
https://hiveapi.actifit.io✓ stablen/an/a✓ stablen/a
https://hived.emre.sh✗ failing✗ failing✗ failing✗ failing✗ failing
https://rpc.ausbit.dev✗ failing✗ failing✗ failing✗ failing✗ failing
https://rpc.mahdiyari.info✓ stable↗ improvingn/a✓ stablen/a
https://techcoderx.comn/a✓ stable✓ stablen/a↗ improving

Node Consistency (7-day period)

This table shows how consistent node performance has been. Lower values indicate more consistent performance.

nodeblockhistoryAPI callconfigblock diff
https://hive-api.3speak.tv0.241.130.731.421.99
https://hive-api.dlux.io0.281.290.870.942.71
https://techcoderx.com0.740.910.770.633.09
https://rpc.mahdiyari.info0.950.990.871.51.94
https://hiveapi.actifit.io1.051.090.641.222.42
https://hive-api.arcange.eu0.761.430.870.972.42
https://api.c0ff33a.uk1.141.230.831.382.53
https://anyx.io0.770.820.01.023.25
https://api.hive.blog1.091.030.730.953.58
https://api.syncad.com1.241.560.591.083.09
https://api.deathwing.me1.250.870.941.712.94
https://hive.roelandp.nl0.00.00.970.683.86
https://api.hive.blue1.860.270.01.643.6
https://api.openhive.network0.01.521.192.282.65
https://rpc.ausbit.dev0.00.00.00.00.0
https://hived.emre.sh0.00.00.00.00.0

Overall Node Ranking

This table shows an overall ranking of nodes based on their performance across all tests.

nodescoreblock rankhistory rankAPI call rankconfig rankblock diff rank
https://hive-api.3speak.tv46.824113
https://hive-api.dlux.io42.012246
https://api.deathwing.me38.435325
https://rpc.mahdiyari.info32.443439
https://api.hive.blog25.291991
https://api.c0ff33a.uk21.6610664
https://hiveapi.actifit.io20.4585510
https://hive-api.arcange.eu16.877778
https://api.openhive.network13.75n/a6887
https://techcoderx.com10.011911122
https://anyx.io2.0811n/a1012
https://api.syncad.com0.01012101111
https://hive.roelandp.nl0.0n/an/an/a1313
https://api.hive.blue0.0n/an/an/an/an/a
https://rpc.ausbit.dev0.0n/an/an/an/an/a
https://hived.emre.sh0.0n/an/an/an/an/a

Conclusion

This report provides a snapshot of Hive 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 nectarflower@nectarflower account's json_metadata for automated processing.

Generated by the hive-bench tool.

hive
benchmark
nodes
performance
api
via hive-bench
This post was published via hive-bench. Ecency is not the originator or editor of this content and displays it for discovery purposes only.
10